From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Olof Johansson <olof@lixom.net>,
Simon Horman <horms@verge.net.au>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/2] base: soc: soc_device_match() improvements
Date: Wed, 29 Mar 2017 21:38:52 +0200 [thread overview]
Message-ID: <1490816334-14568-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Arnd, Greg, Kevin, Magnus, Olof, Simon,
This patch series contains two improvements for the SoC bus and
soc_device_match(). The second one is a dependency for handling
different SoC revisions in the Renesas R-Car SYSC driver, which manages
PM Domains and thus needs to be initialized from an early_initcall[*].
Changes compared to v1:
- Drop RFC state,
- Add more explanation,
- Add Acked-by.
Due to the dependency, and as changes for the Renesas R-Car SYSC driver
typically go in through the renesas and arm-soc trees, and if you agree,
I would like to send a pull request for these changes, to be pulled by
all of the driver core, renesas, and arm-soc trees. This is similar to
how soc_device_match() was integrated earlier.
Then the Renesas R-Car SYSC driver changes can easily be queued on top
in the renesas tree afterwards.
Do you agree?
Thanks for your answer!
P.S. If you think it's already too late in the cycle to queue Renesas
R-Car SYSC driver changes for v4.12 on top, please say so. Then the
dependency is relaxed, and this series can just go in through the
driver core tree, with the Renesas part to follow for v4.13.
[*] "[PATCH 0/3] soc: renesas: rcar-sysc: Add support for R-Car H3
ES2.0" (https://lkml.org/lkml/2017/3/13/833), will send v2 with
patch description changes only soon.
Geert Uytterhoeven (2):
base: soc: Let soc_device_match() return no match when called too
early
base: soc: Allow early registration of a single SoC device
drivers/base/soc.c | 52 ++++++++++++++++++++++++++++++++++------------------
1 file changed, 34 insertions(+), 18 deletions(-)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2017-03-29 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 19:38 Geert Uytterhoeven [this message]
2017-03-29 19:38 ` [PATCH v2 1/2] base: soc: Let soc_device_match() return no match when called too early Geert Uytterhoeven
2017-03-29 19:38 ` [PATCH v2 2/2] base: soc: Allow early registration of a single SoC device Geert Uytterhoeven
2017-03-29 19:48 ` [PATCH v2 0/2] base: soc: soc_device_match() improvements Arnd Bergmann
2017-03-31 8:39 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490816334-14568-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®