[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211024215718.28969-1-digetx@gmail.com>
Date: Mon, 25 Oct 2021 00:57:18 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Viresh Kumar <vireshk@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
Nishanth Menon <nm@...com>, Rob Herring <robh+dt@...nel.org>,
David Heidelberg <david@...t.cz>,
Thierry Reding <treding@...dia.com>,
Jonathan Hunter <jonathanh@...dia.com>
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: [PATCH v3] dt-bindings: opp: Allow multi-worded OPP entry names
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@...t.cz>
Signed-off-by: Dmitry Osipenko <digetx@...il.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
Powered by blists - more mailing lists