public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Carl Philipp Klemm <philipp@uvos.xyz>
Cc: tony@atomide.com, bcousson@baylibre.com, robh+dt@kernel.org,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: dts: omap443x: Correct sgx clock to 307.2MHz as used on motorola vendor kernel
Date: Wed, 30 Dec 2020 16:30:39 +0200	[thread overview]
Message-ID: <8f782d10-4c55-ffe6-aa1c-1960ca0e20c9@gmail.com> (raw)
In-Reply-To: <20201230145115.239b4e1d50db37fce3560007@uvos.xyz>



On 30.12.20 г. 15:51 ч., Carl Philipp Klemm wrote:
> The Android vendor kernel uses 307.2MHz or a devider ratio of /5 while active
> 153600000 or /10 is only used when the sgx core is inactive.
> 
> Signed-off-by: Carl Philipp Klemm <philipp@uvos.xyz>
> ---
>   arch/arm/boot/dts/omap443x.dtsi | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/omap443x.dtsi b/arch/arm/boot/dts/omap443x.dtsi
> index dd8ef58cbaed..8466161197ae 100644
> --- a/arch/arm/boot/dts/omap443x.dtsi
> +++ b/arch/arm/boot/dts/omap443x.dtsi
> @@ -78,11 +78,11 @@ &cpu_thermal {
>   /include/ "omap443x-clocks.dtsi"
>   
>   /*
> - * Use dpll_per for sgx at 153.6MHz like droid4 stock v3.0.8 Android kernel
> + * Use dpll_per for sgx at   like droid4 stock v3.0.8 Android kernel

Is is missing the value here (I guess this should be 307.2MHz)

Regards,
Ivo

>    */
>   &sgx_module {
>   	assigned-clocks = <&l3_gfx_clkctrl OMAP4_GPU_CLKCTRL 24>,
>   			  <&dpll_per_m7x2_ck>;
> -	assigned-clock-rates = <0>, <153600000>;
> +	assigned-clock-rates = <0>, <307200000>;
>   	assigned-clock-parents = <&dpll_per_m7x2_ck>;
>   };
> 

      reply	other threads:[~2020-12-30 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 13:51 [PATCH 1/1] ARM: dts: omap443x: Correct sgx clock to 307.2MHz as used on motorola vendor kernel Carl Philipp Klemm
2020-12-30 14:30 ` Ivaylo Dimitrov [this message]

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=8f782d10-4c55-ffe6-aa1c-1960ca0e20c9@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=philipp@uvos.xyz \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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