From: "Arnd Bergmann" <arnd@arndb.de>
To: "Saravana Kannan" <saravanak@google.com>, "Marek Vasut" <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org, kernel@dh-electronics.com,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Jeff Johnson" <quic_jjohnson@quicinc.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] soc: imx8m: Probe the SoC driver as platform driver
Date: Fri, 27 Sep 2024 11:56:20 +0000 [thread overview]
Message-ID: <dbdb9141-a345-4a17-becb-29e69a494e59@app.fastmail.com> (raw)
In-Reply-To: <CAGETcx-q7+DGhPYd3QrsPh7O_0HU7T=NhaJYp0Fu7YW2zwbo7Q@mail.gmail.com>
On Thu, Sep 26, 2024, at 23:39, Saravana Kannan wrote:
>
> Also, you might want to check that your list of probed devices doesn't
> change without any async probing or this patch vs with async probing
> and this patch. Quick way to get list of successfully probed devices
> is:
> # find /sys/devices -name driver
>
> Arnd,
>
> Why is soc_device_match() doing a bus_for_each_dev(&soc_bus_type,...)?
> Are the real use cases where more than one soc device can be
> registered with soc_device_register()?
Anything can register a soc_device, and I think there is a case
where both the actual SoC and a firmware driver each register
one, see drivers/firmware/smccc/soc_id.c and
drivers/firmware/imx/imx-scu-soc.c.
Not sure how common this is, but this was something that people
asked for when we created the interface.
Arnd
next prev parent reply other threads:[~2024-09-27 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 21:36 [PATCH v3 1/2] soc: imx8m: Probe the SoC driver as platform driver Marek Vasut
2024-09-26 21:36 ` [PATCH v3 2/2] soc: imx8m: Remove global soc_uid Marek Vasut
2024-09-27 16:58 ` Frank Li
2024-09-27 20:05 ` Marek Vasut
2024-09-26 23:39 ` [PATCH v3 1/2] soc: imx8m: Probe the SoC driver as platform driver Saravana Kannan
2024-09-27 11:56 ` Arnd Bergmann [this message]
2024-09-27 21:42 ` Marek Vasut
2024-09-27 22:27 ` Saravana Kannan
2024-09-28 14:09 ` Arnd Bergmann
2024-09-29 18:47 ` Marek Vasut
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=dbdb9141-a345-4a17-becb-29e69a494e59@app.fastmail.com \
--to=arnd@arndb.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=quic_jjohnson@quicinc.com \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@kernel.org \
/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