From: sudeep.holla@arm.com (Sudeep Holla)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] clk: scpi: RfC - Allow to ignore invalid SCPI DVFS clock rates
Date: Wed, 8 Feb 2017 11:23:47 +0000 [thread overview]
Message-ID: <209248b8-2a1c-e00f-d8a8-b82759772b5d@arm.com> (raw)
In-Reply-To: <d7b8f9db-7512-646c-bb96-ef74e7266661@gmail.com>
On 04/02/17 21:03, Heiner Kallweit wrote:
> Introduce an optional property "clock-max-frequency" for SCPI DVFS
> clocks. All frequencies for the respective clock exceeding this
> threshold will be ignored.
>
> This is useful on systems where the firmware offers too optimistic
> clock rates causing instabilities and crashes.
>
It clearly means the firmware/hardware(IOW platform) was not tested
correctly before firmware advertised the OPPs. It needs to fixed in the
firmware. The approach should be advertise the known minimal set working
rather than the set for which hardware was designed.
That's the whole reason while these are kept in firmware so the OS need
not worry about such details.
So NACK, go fix the firmware or disable it completely and be happy with
the boot frequency.
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-02-08 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b60654a-88b6-6262-396e-a058ade1c586@gmail.com>
2017-02-04 21:03 ` Heiner Kallweit
2017-02-08 11:23 ` Sudeep Holla [this message]
2017-02-08 19:45 ` Kevin Hilman
2017-02-09 10:52 ` Sudeep Holla
2017-02-09 12:19 ` Michał Zegan
2017-02-09 12:25 ` Sudeep Holla
2017-02-09 12:51 ` Michał Zegan
2017-02-09 13:31 ` Neil Armstrong
2017-02-09 14:29 ` Sudeep Holla
2017-02-04 21:04 ` [PATCH 2/2] cpufreq: " Heiner Kallweit
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=209248b8-2a1c-e00f-d8a8-b82759772b5d@arm.com \
--to=sudeep.holla@arm.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®