[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170227104445.GE6795@leverpostej>
Date: Mon, 27 Feb 2017 10:44:45 +0000
From: Mark Rutland <mark.rutland@....com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Viresh Kumar <viresh.kumar@...aro.org>,
Rob Herring <robh+dt@...nel.org>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, masahiroy@...nel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Recommended notation for OPP to avoid DTC warnings
On Sun, Feb 26, 2017 at 02:18:03PM +0900, Masahiro Yamada wrote:
> Hi.
>
>
> Decumentation/devicetree/bindings/opp/opp.txt
> takes examples like this:
>
> opp@...0000000 {
> opp-hz = /bits/ 64 <1000000000>;
> opp-microvolt = <970000 975000 985000>;
> opp-microamp = <70000>;
> clock-latency-ns = <300000>;
> opp-suspend;
> };
> If we follow this notation and the device-tree is built with W=1,
> DTC warns like follows:
>
> Warning (unit_address_vs_reg): Node /opp_table0/opp@...0000000 has a
> unit name, but no reg property
>
> Is there a recommended notation to avoid it?
>
> Maybe, simply omit the "@" ?
I think just s/@/-/ should be fine, e.g. call the above opp-1000000000.
Thanks,
Mark.
Powered by blists - more mailing lists