linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brad <bjharper@gmail.com>
To: linux-amlogic@lists.infradead.org
Subject: Re: [RFC-next 0/1] Odroid C2: Enable DVFS for cpu
Date: Thu, 2 Jan 2020 11:16:55 +1100	[thread overview]
Message-ID: <6fa964be-7222-66d6-2118-90b6e618b7d1@gmail.com> (raw)
In-Reply-To: <83791a71-a45c-383d-0406-b0f4e0a0c215@baylibre.com>


On 14/12/2019 12:24 am, Neil Armstrong wrote:
>
> This is the point, the Odroid-C2 is *not* stable at 2GHz,
> a large amount of board doesn't support 2GHz, this is why Amlogic
> dropped the freq > 1.536 GHz for the GXBB family.
>
> But HardKernel still delivers the SCPI table with > 1.536 GHz which breaks
> on most of the boards, but doesn't on 3.14 since they have a hack disabling
> higher freqs with a cmdline set in boot.ini.

Hi Neil,

Hardkernel did update there firmware to restrict frequency to 1.536 back 
in 2017 back in this commit 
https://github.com/hardkernel/u-boot/commit/205c7b3259559283161703a1a200b787c2c445a5 
Versions prior to this would runaway on boot up to 2Ghz and crash.

They also added a hidden function to the SCPI_CMD_GET_DVFS_INFO call 
which works by changing the domain number in the call to pull back 
different OPP tables.  Domain set to 0 will limit frequency to 1.536.  
They set the highest bit in the domain number to 1 which opens SCPI 
table to 2.016GHz.  This is done in via BL301 so it might be possible 
for mainline kernel to check this bit and open up the table after boot 
using a special driver.  Joy posted some details here 
https://forum.odroid.com/viewtopic.php?f=141&t=23044&start=350#p181017

Of course it would still cause problems for boards running an old 
version of the firmware but newer versions of the bootloader boot fine 
in mainline with DVFS enabled as its limited to 1.536 by default.

> The various tests gave very little perf enhancement by going > 1,536 GHz, seriously
> it's not worth the pain.
>
> Neil

My tests showed my board (they may vary) was very stable up to 
1.680Ghz,  at 1.752Ghz could get it to crash if I tried to burn all 4 
cores with heavy NEON stress test. At 1.896GHz I would get random 
freezes even with only 1 core enabled at boot.  I must say I never 
tested with Mali enabled so it may influence things.

I do agree though it might cause more pain that it is worth especially 
when old firmware is used.

- Brad

>> -Anand
>>
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2020-01-02  0:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 14:31 [RFC-next 0/1] Odroid C2: Enable DVFS for cpu Anand Moon
2019-11-01 14:31 ` [RFC-next 1/1] arm64: dts: meson: odroid-c2: Enable SCPI " Anand Moon
2019-12-09 22:12 ` [RFC-next 0/1] Odroid C2: Enable " Kevin Hilman
2019-12-10  8:43   ` Neil Armstrong
2019-12-10 14:50     ` Anand Moon
2019-12-10 18:13       ` Kevin Hilman
2019-12-10 20:04         ` Martin Blumenstingl
2019-12-10 21:47           ` Kevin Hilman
2019-12-11  8:49             ` Neil Armstrong
2019-12-12 20:09               ` Martin Blumenstingl
2019-12-13 11:28                 ` Anand Moon
2019-12-13 13:24                   ` Neil Armstrong
2019-12-13 14:23                     ` Anand Moon
2020-01-02  0:16                     ` Brad [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=6fa964be-7222-66d6-2118-90b6e618b7d1@gmail.com \
    --to=bjharper@gmail.com \
    --cc=linux-amlogic@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).