mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: hkallweit1@gmail.com (Heiner Kallweit)
To: linus-amlogic@lists.infradead.org
Subject: Follow-up: How to deal with weird SCPI firmware and invalid DVFS frequencies
Date: Thu, 5 Oct 2017 22:32:01 +0200	[thread overview]
Message-ID: <a96ffcce-7399-97c6-10be-88869c77ccef@gmail.com> (raw)

Few months ago we discussed how to deal with the Amlogic Meson SCPI
DVFS cpu frequencies. To recap:
SCPI DVFS provides some high frequencies which are usable only if
just one CPU core is used. Else the system will just crash
(even w/o being thermally loaded).

See also:
https://patchwork.kernel.org/patch/9557349/
https://patchwork.kernel.org/patch/9555761/

One idea was to introduce a DT param for the CPU nodes to configure
a max frequency, and all DVFS freq's above this threashold would be
ignored. However we didn't come to an agreement.

Now, when dealing with SCPI again, another idea came to my mind:
Still it would be about introducing such a DT parameter, however
we would not completely ignore higher frequencies but just set
the "turbo" flag of the opp.
This way cpufreq would ignore these frequencies, however we still
had the option to manually enable these frequencies via sysfs and
use them on systems where just one CPU core is used.
(or more general: manually enable the boost frequencies if system
macthes certain criteria)

Does this sound better or would you still consider this to be too
hacky?

Rgds, Heiner

             reply	other threads:[~2017-10-05 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 20:32 Heiner Kallweit [this message]
2017-10-06 15:33 ` Sudeep Holla

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=a96ffcce-7399-97c6-10be-88869c77ccef@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=linus-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

all inboxes | Powered by JetHome®