From: Mark Brown <broonie@kernel.org>
To: David Collins <quic_collinsd@quicinc.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Cristian Marussi <cristian.marussi@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
Subject: Re: [RESEND PATCH 1/2] dt-bindings: firmware: arm,scmi: define support for name based regulators
Date: Thu, 3 Feb 2022 11:28:30 +0000 [thread overview]
Message-ID: <Yfu8XulvWQbpQoBR@sirena.org.uk> (raw)
In-Reply-To: <532aa931-2471-8fb3-0db4-7ab8a60333e8@quicinc.com>
[-- Attachment #1.1: Type: text/plain, Size: 812 bytes --]
On Wed, Feb 02, 2022 at 04:09:43PM -0800, David Collins wrote:
> On 2/2/22 9:38 AM, Mark Brown wrote:
> > This seems like a scenario where the DT should be being generated at
> > runtime along with the virtualisation of the platform? TBH a setup
> > where this is an issue feels like it's asking for trouble.
> I'm not familiar with runtime device tree generation. Could you please
> point to an example of it or documentation for it? How would this
> handle kernel devices on the VM side which need a phandle to an
> scmi-regulator DT subnode in order to get a pointer to the corresponding
> regulator device at runtime via devm_regulator_get()?
I believe qemu does this for the virt machine. I'm not sure what you're
seeing as particularly complex about generating regulator links in
particular though?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-03 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 0:27 [RESEND PATCH 0/2] regulator: scmi: add support for registering SCMI regulators by name David Collins
2022-01-25 0:27 ` [RESEND PATCH 1/2] dt-bindings: firmware: arm, scmi: define support for name based regulators David Collins
2022-01-28 19:32 ` [RESEND PATCH 1/2] dt-bindings: firmware: arm,scmi: " Mark Brown
2022-01-28 23:09 ` David Collins
2022-02-02 17:38 ` Mark Brown
2022-02-03 0:09 ` David Collins
2022-02-03 11:28 ` Mark Brown [this message]
2022-01-25 0:27 ` [RESEND PATCH 2/2] regulator: scmi: add support for registering SCMI regulators by name David Collins
-- strict thread matches above, loose matches on Subject: below --
2021-12-10 1:54 [PATCH 0/2] " David Collins
2021-12-10 1:54 ` [PATCH 1/2] dt-bindings: firmware: arm, scmi: define support for name based regulators David Collins
2022-01-24 23:20 ` [RESEND PATCH " David Collins
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=Yfu8XulvWQbpQoBR@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_collinsd@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).