From: Lukasz Luba <lukasz.luba@arm.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] cpufreq: Reintroduce ready() callback
Date: Fri, 28 Jan 2022 08:52:08 +0000 [thread overview]
Message-ID: <f539ca2b-22c4-5708-ddd6-4b638dc0655d@arm.com> (raw)
In-Reply-To: <20220128032554.155132-1-bjorn.andersson@linaro.org>
Hi Bjorn,
On 1/28/22 3:25 AM, Bjorn Andersson wrote:
> This effectively revert '4bf8e582119e ("cpufreq: Remove ready()
> callback")' (except the Chinese translation), in order to reintroduce
Is there something wrong with the Chinese translation that it has to be
dropped? Someone has put an effort to create it, I'd assume (and also
based on online translator) that it's correct.
> the ready callback.
>
> This is needed in order to be able to leave the thermal pressure
> interrupts in the Qualcomm CPUfreq driver disabled during
> initialization, so that it doesn't fire while related_cpus are still 0.
If you are going to push the 2nd patch into stable tree, then you would
also need this one.
Regards,
Lukasz
next prev parent reply other threads:[~2022-01-28 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 3:25 Bjorn Andersson
2022-01-28 3:25 ` [PATCH v2 2/2] cpufreq: qcom-hw: Delay enabling throttle_irq Bjorn Andersson
2022-01-28 10:39 ` Lukasz Luba
2022-01-28 18:30 ` Bjorn Andersson
2022-01-31 8:59 ` Lukasz Luba
2022-02-09 7:38 ` Viresh Kumar
2022-01-28 8:52 ` Lukasz Luba [this message]
2022-01-28 18:24 ` [PATCH v2 1/2] cpufreq: Reintroduce ready() callback Bjorn Andersson
2022-02-09 7:50 ` Viresh Kumar
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=f539ca2b-22c4-5708-ddd6-4b638dc0655d@arm.com \
--to=lukasz.luba@arm.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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®