From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rob Herring <robh@kernel.org>, Viresh Kumar <vireshk@kernel.org>,
Stephen Boyd <sboyd@kernel.org>, Nishanth Menon <nm@ti.com>,
David Heidelberg <david@ixit.cz>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: opp: Allow multi-worded node names
Date: Fri, 22 Oct 2021 10:39:22 +0300 [thread overview]
Message-ID: <9798d34b-4886-9d4a-9fb7-634aa323af02@gmail.com> (raw)
In-Reply-To: <20211022065029.x5a5oh7mh2sjofey@vireshk-i7>
22.10.2021 09:50, Viresh Kumar пишет:
> On 22-10-21, 09:40, Dmitry Osipenko wrote:
>> 22.10.2021 07:43, Viresh Kumar пишет:
>>> On 20-10-21, 09:46, Rob Herring wrote:
>>>> On Wed, Oct 20, 2021 at 02:19:05AM +0300, Dmitry Osipenko wrote:
>>>>> Not all OPP table names and OPP entries consist of a single word. In
>>>>> particular NVIDIA Tegra OPP tables use multi-word names. Allow OPP node
>>>>> and OPP entry name to have multi-worded names to silence DT checker
>>>>> warnings about the multi-word names separated by hyphen.
>>>>>
>>>>> Reviewed-by: David Heidelberg <david@ixit.cz>
>>>>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>>>>> ---
>>>>> Documentation/devicetree/bindings/opp/opp-v2-base.yaml | 4 ++--
>>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
>>>>> index ae3ae4d39843..298cf24af270 100644
>>>>> --- a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
>>>>> +++ b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
>>>>> @@ -22,7 +22,7 @@ select: false
>>>>>
>>>>> properties:
>>>>> $nodename:
>>>>> - pattern: '^opp-table(-[a-z0-9]+)?$'
>>>>> + pattern: '^opp-table(-[a-z0-9]+)*$'
>>>>
>>>> I don't see how this helps you. What I see needed upstream is a prefix:
>>>>
>>>> '-?opp-table(-[0-9]+)?$'
>>>
>>> I wonder if we should disallow that to keep naming more
>>
>> I also think that postfix variant should be disallowed for consistency.
>> I sent out patches for both variants.
>>
>> V2 uses pattern that supports both naming schemes. If V2 is less
>> appropriate, then please take this V1.
>
> I didn't like V2, we can mandate to keep it like opp-* and opp-table-*.
>
> This patch looked okay to me, lets see what Rob has to say.
>
What we currently have for Tegra is a tegra-opps.dtsi and tegra.dtsi
which includes the OPP's dtsi.
the tegra-opps.dtsi has this structure:
table: devname-opp-table {
opp: ...
};
and tegra.dtsi:
#include "tegra-opps.dtsi"
device@0000 {
operating-points-v2 = <&table>;
};
It just occurred to me that there is no need to move all tables to
tegra.dtsi, but change structure of tegra-opps.dtsi to:
device@0000 {
operating-points-v2 = <&table>;
table: opp-table {
opp: ...
};
};
Then there no need to change current naming scheme. Let me try to
implement it and see how it goes.
next prev parent reply other threads:[~2021-10-22 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 23:19 [PATCH v1] dt-bindings: opp: Allow multi-worded node names Dmitry Osipenko
2021-10-20 14:46 ` Rob Herring
2021-10-20 14:59 ` Dmitry Osipenko
2021-10-21 5:59 ` Dmitry Osipenko
2021-10-22 4:43 ` Viresh Kumar
2021-10-22 5:58 ` Dmitry Osipenko
2021-10-22 6:40 ` Dmitry Osipenko
2021-10-22 6:50 ` Viresh Kumar
2021-10-22 7:39 ` Dmitry Osipenko [this message]
2021-10-22 7:45 ` Viresh Kumar
2021-10-23 13:00 ` Dmitry Osipenko
2021-10-23 13:46 ` Dmitry Osipenko
2021-10-23 19:01 ` Dmitry Osipenko
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=9798d34b-4886-9d4a-9fb7-634aa323af02@gmail.com \
--to=digetx@gmail.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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