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>,
Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH v3] dt-bindings: opp: Allow multi-worded OPP entry names
Date: Mon, 25 Oct 2021 00:57:18 +0300 [thread overview]
Message-ID: <20211024215718.28969-1-digetx@gmail.com> (raw)
Not all OPP entries fit into a single word. In particular NVIDIA Tegra OPP
tables use multi-word names where first part is freq and second voltage
because different hardware versions use different voltages for the same
freqs. Allow OPP entry to have multi-worded name separated by hyphen.
This silences DT checker warnings about wrong naming scheme.
Reviewed-by: David Heidelberg <david@ixit.cz>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
Changelog:
v3: - Viresh Kumar suggested that we shouldn't support postfix variant.
I dropped variant with postfix naming scheme and multi-wording
support of table names.
v2: - In addition to a multi-wording support, support of the postfix
*-opp-table naming scheme is added to the updated pattern.
Documentation/devicetree/bindings/opp/opp-v2-base.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
index ae3ae4d39843..f79343960539 100644
--- a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
+++ b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
@@ -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.33.1
next reply other threads:[~2021-10-24 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 21:57 Dmitry Osipenko [this message]
2021-10-25 5:49 ` [PATCH v3] dt-bindings: opp: Allow multi-worded OPP entry names Viresh Kumar
2021-10-27 21:19 ` Rob Herring
2021-10-28 21:12 ` 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=20211024215718.28969-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).