From: Dave Gerlach <d-gerlach@ti.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Menon, Nishanth" <nm@ti.com>
Subject: Re: [PATCH 2/2] DTS: dra7: Add "opp_high" opp node to support 1.5 GHz SoC operation
Date: Mon, 6 Feb 2017 09:24:55 -0600 [thread overview]
Message-ID: <58989547.9030002@ti.com> (raw)
In-Reply-To: <20170206152450.3739af18@jawa>
Hi,
On 02/06/2017 08:24 AM, Lukasz Majewski wrote:
> Hi Dave,
>
>> On 02/03/2017 09:24 AM, Lukasz Majewski wrote:
>>> The "opp_high" property brings support for 1.5 GHz CPU frequency
>>> for TI's am57xx line of processors.
>>>
>>> Signed-off-by: Lukasz Majewski <lukma@denx.de>
>>> ---
>>> arch/arm/boot/dts/dra7.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>
>> This can't be blindly enabled for all am57xx SoCs, there is a
>> forthcoming ti-cpufreq [1] driver that is needed that will decided
>> which OPPs can and cannot be enabled for the specific variant in use.
>
> Do you know if there is ongoing work on using Avs0 voltage (encoded in
> efuse) to control the per SoC PMIC voltage value when switching to
> opp_high (1.5 GHz)?
Yes, Viresh Kumar introduced multi-regulator support in the OPP core recently
[1] which I wrote a test driver for here [2] which hooks into the OPP framework
to do both ABB regulator scaling and also programs the AVS0 voltages. The
current implementation I have cleaned up will depend on the ti-cpufreq driver so
once that is merged I will send the AVS0 and ABB support driver upstream as
well. If you are curious you can look at current internal implementation here [3].
Regards,
Dave
[1] http://www.spinics.net/lists/devicetree/msg153212.html
[2] https://www.spinics.net/lists/kernel/msg2384336.html
[3]
http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-lsk-linux-4.9.y/drivers/base/power/opp/ti-opp-supply.c
>
>
>>
>> Regards,
>> Dave
>>
>> [1] http://www.spinics.net/lists/devicetree/msg158967.html
>>
>>> diff --git a/arch/arm/boot/dts/dra7.dtsi
>>> b/arch/arm/boot/dts/dra7.dtsi index a860a56..5e678cd 100644
>>> --- a/arch/arm/boot/dts/dra7.dtsi
>>> +++ b/arch/arm/boot/dts/dra7.dtsi
>>> @@ -108,6 +108,11 @@
>>> opp-hz = /bits/ 64 <1176000000>;
>>> opp-microvolt = <1160000 885000 1160000>;
>>> };
>>> +
>>> + opp_high@1500000000 {
>>> + opp-hz = /bits/ 64 <1500000000>;
>>> + opp-microvolt = <1210000 950000 1250000>;
>>> + };
>>> };
>>>
>>> /*
>>>
>>
>
>
>
>
> Best regards,
>
> Lukasz Majewski
>
> --
>
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
>
next prev parent reply other threads:[~2017-02-06 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 15:24 [PATCH 1/2] DTS: dra7: Replace obsolete "operating-points" property with "operating-points-v2" Lukasz Majewski
2017-02-03 15:24 ` [PATCH 2/2] DTS: dra7: Add "opp_high" opp node to support 1.5 GHz SoC operation Lukasz Majewski
2017-02-03 16:48 ` Nishanth Menon
2017-02-03 23:06 ` Lukasz Majewski
2017-02-03 23:14 ` Nishanth Menon
2017-02-03 16:56 ` Dave Gerlach
2017-02-03 23:21 ` Lukasz Majewski
2017-02-04 0:21 ` Nishanth Menon
2017-02-04 5:30 ` Lukasz Majewski
2017-02-06 14:24 ` Lukasz Majewski
2017-02-06 15:24 ` Dave Gerlach [this message]
2017-02-07 4:27 ` Lukasz Majewski
2017-02-03 16:54 ` [PATCH 1/2] DTS: dra7: Replace obsolete "operating-points" property with "operating-points-v2" Dave Gerlach
2017-02-06 3:43 ` Viresh Kumar
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=58989547.9030002@ti.com \
--to=d-gerlach@ti.com \
--cc=bcousson@baylibre.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lukma@denx.de \
--cc=nm@ti.com \
/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).