From: David Heidelberg <david@ixit.cz>
To: Rob Herring <robh@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] [v2] dt-bindings: arm/msm/qcom,idle-state convert to YAML
Date: Sat, 11 Sep 2021 18:51:58 +0200 [thread overview]
Message-ID: <M64AZQ.XHLJ2TTJASSV1@ixit.cz> (raw)
In-Reply-To: <YTvWaRCswQs9Mt6L@robh.at.kernel.org>
Thank you for the input, for now I applied option 1 to my another
tegra-ehci binding (instead of having own file) and it lead to success,
so I'll choose option 1 for this case too.
Best regards
David Heidelberg
On Fri, Sep 10 2021 at 17:04:25 -0500, Rob Herring <robh@kernel.org>
wrote:
> On Wed, Sep 08, 2021 at 07:14:53PM +0200, David Heidelberg wrote:
>> Switched maintainer from Lina to Bjorn.
>>
>> Doesn't fix:
>> ```
>> idle-states: 'spc' does not match any of the regexes:
>> '^(cpu|cluster)-', 'pinctrl-[0-9]+'
>> ```
>> from colliding arm/idle-states.yaml .
>
> Your options are:
>
> - Drop this and add your node names and compatible strings to
> idle-states.yaml. A variation of this is change the QCom node names
> in dts files to match. Those look like the only real differences.
>
> - Extract the common idle state node properties to a common schema to
> reference from both schemas.
>
> I'd lean towards option 1 unless there are other variations of
> idle-state nodes that also need option 2.
>
> Rob
prev parent reply other threads:[~2021-09-11 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 17:14 [RFC PATCH] [v2] dt-bindings: arm/msm/qcom,idle-state convert to YAML David Heidelberg
2021-09-09 12:32 ` Rob Herring
2021-09-10 22:04 ` Rob Herring
2021-09-11 16:51 ` David Heidelberg [this message]
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=M64AZQ.XHLJ2TTJASSV1@ixit.cz \
--to=david@ixit.cz \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox