linux-kernel - Re: [PATCH v1] dt-bindings: opp: Allow multi-worded node names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 22 Oct 2021 13:15:51 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Dmitry Osipenko <digetx@...il.com>
Cc:     Rob Herring <robh@...nel.org>, Viresh Kumar <vireshk@...nel.org>,
        Stephen Boyd <sboyd@...nel.org>, Nishanth Menon <nm@...com>,
        David Heidelberg <david@...t.cz>, linux-kernel@...r.kernel.org,
        linux-pm@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v1] dt-bindings: opp: Allow multi-worded node names

On 22-10-21, 10:39, Dmitry Osipenko wrote:
> 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@...0 {
> 	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@...0 {
> 	operating-points-v2 = <&table>;
> 
> 	table: opp-table {
> 		opp: ...
> 	};
> };

I thought you would have already thought about that and I was surprised when you
saw the tables are big enough to be moved. I was wondering what does it really
mean :)

> Then there no need to change current naming scheme. Let me try to
> implement it and see how it goes.

That's good then.

-- 
viresh