From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Peng Fan <peng.fan@oss.nxp.com>,
saravanak@google.com, cristian.marussi@arm.com,
krzk+dt@kernel.org, conor+dt@kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [RFC] dt-bindings: firmware: scmi: Introduce compatible string
Date: Fri, 28 Feb 2025 14:04:21 +0000 [thread overview]
Message-ID: <Z8HCZQQLofaiGtpG@bogus> (raw)
In-Reply-To: <CAL_JsqJOqKeDRuASWxCT=EA5LJbONpCX=Re8=XxKUbPToWy2Dg@mail.gmail.com>
On Fri, Feb 28, 2025 at 07:34:09AM -0600, Rob Herring wrote:
>
> - The parent driver creates child devices. The child devices can
> either reuse the parent DT node (i.e. set dev.of_node) or just get it
> from the parent device if needed.
>
This is exactly what I was thinking to deal with the issue since this
discussion started. I will give this a go. I believe this must solve
the issue, but I didn't want to spit it out loud until I tried to hack
and check.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-02-28 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:44 [RFC] dt-bindings: firmware: scmi: Introduce compatible string Peng Fan (OSS)
2025-02-26 16:09 ` Rob Herring
2025-02-26 17:19 ` Sudeep Holla
2025-02-27 3:15 ` Peng Fan
2025-02-27 9:12 ` Sudeep Holla
2025-02-27 3:09 ` Peng Fan
2025-02-28 13:34 ` Rob Herring
2025-02-28 14:04 ` Sudeep Holla [this message]
2025-02-28 14:17 ` Rob Herring
2025-03-03 4:35 ` Peng Fan
2025-02-27 11:48 ` Cristian Marussi
2025-03-03 4:27 ` Peng Fan
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=Z8HCZQQLofaiGtpG@bogus \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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).