Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: "Lukasz Majewski" <lukma@denx.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Viresh Kumar" <viresh.kumar@linaro.org>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH 2/2] DTS: dra7: Add "opp_high" opp node to support 1.5 GHz SoC operation
Date: Fri, 3 Feb 2017 10:56:57 -0600	[thread overview]
Message-ID: <e398ff96-dca7-7934-70b1-9a95c01d3b27@ti.com> (raw)
In-Reply-To: <1486135491-14223-2-git-send-email-lukma@denx.de>

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.

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>;
> +		};
>  	};
>
>  	/*
>

  parent reply	other threads:[~2017-02-03 16:56 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
     [not found]     ` <f17ceda2-45e0-9c67-7c8a-5a35132a2d0a-l0cyMroinI0@public.gmane.org>
2017-02-03 23:06       ` Lukasz Majewski
2017-02-03 23:14         ` Nishanth Menon
2017-02-03 16:56   ` Dave Gerlach [this message]
     [not found]     ` <e398ff96-dca7-7934-70b1-9a95c01d3b27-l0cyMroinI0@public.gmane.org>
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
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
     [not found] ` <1486135491-14223-1-git-send-email-lukma-ynQEQJNshbs@public.gmane.org>
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=e398ff96-dca7-7934-70b1-9a95c01d3b27@ti.com \
    --to=d-gerlach@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukma@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.org \
    /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