From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"cristian.marussi@arm.com" <cristian.marussi@arm.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>
Subject: Re: [PATCH RESEND] dt-bindings: firmware: arm,scmi: support system power protocol
Date: Thu, 18 Jul 2024 15:52:32 +0100 [thread overview]
Message-ID: <ZpksMAYaAkemr9dd@bogus> (raw)
In-Reply-To: <PAXPR04MB8459EB8FC25AFF6D7C912F2A88AC2@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Thu, Jul 18, 2024 at 12:15:20PM +0000, Peng Fan wrote:
> Hi Sudeep,
>
> > Subject: RE: [PATCH RESEND] dt-bindings: firmware: arm,scmi: support
> > system power protocol
> >
> > > Subject: Re: [PATCH RESEND] dt-bindings: firmware: arm,scmi:
> > support
> > > system power protocol
> > >
> > > On Fri, Jun 28, 2024 at 11:03:09AM +0800, Peng Fan (OSS) wrote:
> > > > From: Peng Fan <peng.fan@nxp.com>
> > > >
> > > > Add SCMI System Power Protocol bindings, and the protocol id is
> > > 0x12.
> > > >
> > >
> > > I think we must have this node only if it has dedicated channel or any
> > > other required property.
> >
> > I posted a patchset to support nodes not in device tree. And Cristian
> > gave some comments:
> > https://lore.kernel.org/all/Znv1p3FDiPSUNmBM@pluto/
> >
>
> Please suggest what should I do to avoid the dtbs_check issue.
>
> Should I switch back to
> https://lore.kernel.org/all/Znv1p3FDiPSUNmBM@pluto/
> or else?
>
Sorry I need to discuss with Cristain and decide. I might have already
discussed but I can't recall the details or decision(if any) made after
that. He is away now, will get back once we discuss and see what is the
best approach.
--
Regards,
Sudeep
next prev parent reply other threads:[~2024-07-18 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 3:03 [PATCH RESEND] dt-bindings: firmware: arm,scmi: support system power protocol Peng Fan (OSS)
2024-07-01 17:04 ` Rob Herring (Arm)
2024-07-04 10:40 ` Sudeep Holla
2024-07-04 10:46 ` Peng Fan
2024-07-18 12:15 ` Peng Fan
2024-07-18 14:52 ` Sudeep Holla [this message]
2024-08-02 2:51 ` Peng Fan
2024-08-09 13:34 ` 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=ZpksMAYaAkemr9dd@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.