From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <vireshk@kernel.org>,
Stephen Boyd <sboyd@kernel.org>, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>,
David Heidelberg <david@ixit.cz>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v1] dt-bindings: opp: Allow multi-worded node names
Date: Wed, 20 Oct 2021 02:19:05 +0300 [thread overview]
Message-ID: <20211019231905.2974-1-digetx@gmail.com> (raw)
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]+)*$'
opp-shared:
description:
@@ -33,7 +33,7 @@ properties:
type: boolean
patternProperties:
- '^opp-?[0-9]+$':
+ '^opp(-[0-9]+)*$':
type: object
description:
One or more OPP nodes describing voltage-current-frequency combinations.
--
2.32.0
next reply other threads:[~2021-10-19 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 23:19 Dmitry Osipenko [this message]
2021-10-20 14:46 ` [PATCH v1] dt-bindings: opp: Allow multi-worded node names 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
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=20211019231905.2974-1-digetx@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+dt@kernel.org \
--cc=sboyd@kernel.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