devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Steev Klimaszewski <steev@kali.org>
Subject: Re: [PATCH] arm64: dts: sdm850: Add OPP tables for 2.84 and 2.96GHz
Date: Tue, 12 Jan 2021 17:05:12 +0800	[thread overview]
Message-ID: <20210112090455.GA2479@dragon> (raw)
In-Reply-To: <20210112090140.19867-1-shawn.guo@linaro.org>

On Tue, Jan 12, 2021 at 05:01:40PM +0800, Shawn Guo wrote:
> From: Steev Klimaszewski <steev@kali.org>
> 
> Running cpufreq-hw driver on Lenovo Yoga C630 laptop, the following
> warning messages will be seen.
> 
> [    3.415340] cpu cpu4: Voltage update failed freq=2841600
> [    3.418755] cpu cpu4: failed to update OPP for freq=2841600
> [    3.422949] cpu cpu4: Voltage update failed freq=2956800
> [    3.427086] cpu cpu4: failed to update OPP for freq=2956800
> 
> This is because the cpufreq-hw lookup table of SDM850 provides these two
> set-points, but they are missing from OPP table in DT.  Let's create
> sdm850.dtsi to add the OPP for them, so that the warning will be gone.
> 
> Signed-off-by: Steev Klimaszewski <steev@kali.org>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>

Ignore this one.  Some needed changes got lost.

Shawn

      reply	other threads:[~2021-01-12  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  9:01 [PATCH] arm64: dts: sdm850: Add OPP tables for 2.84 and 2.96GHz Shawn Guo
2021-01-12  9:05 ` Shawn Guo [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=20210112090455.GA2479@dragon \
    --to=shawn.guo@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=steev@kali.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).