From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: firmware: arm,scmi: Update examples for protocol@13
Date: Wed, 10 Apr 2024 13:35:48 +0100 [thread overview]
Message-ID: <ZhaHpKLlPhr-eAvl@bogus> (raw)
In-Reply-To: <20240410115637.GA4042282-robh@kernel.org>
On Wed, Apr 10, 2024 at 06:56:37AM -0500, Rob Herring wrote:
> On Thu, Apr 04, 2024 at 12:52:08PM +0200, Ulf Hansson wrote:
> > On Wed, 3 Apr 2024 at 15:53, Sudeep Holla <sudeep.holla@arm.com> wrote:
> > >
> > > On Wed, Apr 03, 2024 at 01:11:06PM +0200, Ulf Hansson wrote:
> > > > Recently we extended the binding for protocol@13 to allow it to be modelled
> > > > as a generic performance domain. In a way to promote using the new binding,
> > > > let's update the examples.
> > > >
> > >
> > > Does it make sense to keep one DVFS example with #clock-cells until we
> > > mark it as deprecated ? Otherwise it may be confusing as the binding still
> > > lists. Or leave some comment in the example or something, I am open for
> > > suggestions.
> >
> > I am certainly fine with either way!
> >
> > However, if we intend to make #clock-cells deprecated down the road,
> > maybe it's better to start avoiding the use of it already now. That
> > said, what do you think of following up $subject patch with an update
> > to Juno's dts(i) to move to #power-domains-cells too? That would mean
> > we get a nice reference for how to use this too.
> >
> > >
> > > Other than that,
> > >
> > > Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> >
> > Are you picking this via your scmi tree, or which route is this going?
>
Sorry Ulf, this slipped through the cracks, will queue it.
> Please take via SCMI tree.
>
Sure
> Acked-by: Rob Herring <robh@kernel.org>
Thanks
--
Regards,
Sudeep
_______________________________________________
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:[~2024-04-10 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 11:11 [PATCH] dt-bindings: firmware: arm,scmi: Update examples for protocol@13 Ulf Hansson
2024-04-03 13:53 ` Sudeep Holla
2024-04-04 10:52 ` Ulf Hansson
2024-04-10 11:56 ` Rob Herring
2024-04-10 12:35 ` Sudeep Holla [this message]
2024-04-18 10:04 ` Sudeep Holla
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=ZhaHpKLlPhr-eAvl@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).