[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <F72772FC-088A-43B6-B486-7AD172885796@goldelico.com>
Date: Tue, 3 Sep 2019 07:58:43 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Benoît Cousson <bcousson@...libre.com>,
Tony Lindgren <tony@...mide.com>,
Rob Herring <robh+dt@...nel.org>,
Adam Ford <aford173@...il.com>,
André Roth <neolynx@...il.com>,
Mark Rutland <mark.rutland@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
letux-kernel@...nphoenux.org, kernel@...a-handheld.com
Subject: Re: [RFC 2/5] ARM: dts: add support for opp-v2 for omap34xx and omap36xx
> Am 03.09.2019 um 04:38 schrieb Viresh Kumar <viresh.kumar@...aro.org>:
>
> On 02-09-19, 12:55, H. Nikolaus Schaller wrote:
>> + opp1-125000000 {
>> + opp-hz = /bits/ 64 <125000000>;
>> + // we currently only select the max voltage from table Table 3-3 of the omap3530 Data sheet (SPRS507F)
>> + // <target min max> could also be single <target>
>> + opp-microvolt = <975000 975000 975000>;
>> + // first value is silicon revision, second one 720MHz Device Identification
>
>> + opp-supported-hw = <0xffffffff 3>;
>
> I don't see the driver changes using this field, am I missing
> something ?
This is parsed by _opp_is_supported() which is called
indirectly by ti_cpufreq_probe().
BR,
Nikolaus
Powered by blists - more mailing lists