linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: Cristian Marussi <cristian.marussi@arm.com>,
	"Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: "sudeep.holla@arm.com" <sudeep.holla@arm.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.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>
Subject: RE: [PATCH] dt-bindings: firmware: arm,scmi: support system power protocol
Date: Tue, 27 Feb 2024 01:01:41 +0000	[thread overview]
Message-ID: <DU0PR04MB941710FB1400D0A17F99B6ED88592@DU0PR04MB9417.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <ZdyoAsYGXK9GjHVx@pluto>

> Subject: Re: [PATCH] dt-bindings: firmware: arm,scmi: support system power
> protocol
>
> On Mon, Feb 26, 2024 at 01:28:31PM +0000, Cristian Marussi wrote:
> > On Mon, Feb 26, 2024 at 09:02:43PM +0800, Peng Fan (OSS) wrote:
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > Add SCMI System Power Protocol bindings, and the protocol id is 0x12.
> > >
> > Hi,
> >
> > yes this is something I spotted in the past it was missing and I
> > posted a similar patch but I was told that a protocol node without any
> > specific additional properties is already being described by the
> > general protocol node described above.

Without this patch, there is dtbs_check warning.

scmi: 'protocol@12' does not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/firmware/arm,scmi.yaml#

Regards,
Peng.

> >
>
>
> I was referring to this old thread...
>
> https://lore.ke/
> rnel.org%2Fall%2F20230124222023.316089-1-
> robh%40kernel.org%2F&data=05%7C02%7Cpeng.fan%40nxp.com%7C73d2d
> 867857f409cfd2608dc36dbf475%7C686ea1d3bc2b4c6fa92cd99c5c301635%
> 7C0%7C0%7C638445565544388755%7CUnknown%7CTWFpbGZsb3d8eyJWI
> joiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> 0%7C%7C%7C&sdata=SDKSIbYQq5YS4M7SJXyWwaPLVvQK6wIPtjUYi%2FW3
> p6k%3D&reserved=0
>
> Thanks,
> Cristian

  reply	other threads:[~2024-02-27  1:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 13:02 [PATCH] dt-bindings: firmware: arm,scmi: support system power protocol Peng Fan (OSS)
2024-02-26 13:28 ` Cristian Marussi
2024-02-26 15:02   ` Cristian Marussi
2024-02-27  1:01     ` Peng Fan [this message]
2024-02-29 13:59       ` Sudeep Holla
2024-03-01  0:41         ` Peng Fan
2024-03-01  7:52           ` Cristian Marussi
2024-03-01  9:22             ` Peng Fan
2024-03-01  9:31               ` Sudeep Holla
2024-03-01 10:37               ` Cristian Marussi
2024-03-01 10:46                 ` Cristian Marussi
2024-03-04  2:18                   ` Peng Fan
2024-03-04  8:29                     ` Cristian Marussi

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=DU0PR04MB941710FB1400D0A17F99B6ED88592@DU0PR04MB9417.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@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).