From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org,
ilia.lin@kernel.org, rafael@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/5] qcom-cpufreq-nvmem: Add msm8939 with some fixups
Date: Wed, 25 May 2022 13:51:33 +0100 [thread overview]
Message-ID: <ef871d78-12d2-e19e-9a12-6288256116a7@linaro.org> (raw)
In-Reply-To: <20220418162226.2983117-1-bryan.odonoghue@linaro.org>
On 18/04/2022 17:22, Bryan O'Donoghue wrote:
> Fix up some missing compat strings for the qcom-cpufreq-nvmem yaml.
> Add in msm8939 as a compatible qcom-cpufreq-nvmem.
>
> Bryan O'Donoghue (5):
> dt-bindings: opp: Add missing compat devices
> dt-bindings: opp: Add msm8939 to the compatible list
> cpufreq: blocklist Qualcomm msm8939 in cpufreq-dt-platdev
> cpufreq: qcom-cpufreq-nvmem: Rename qcs404 data to cpr_genpd
> cpufreq: qcom-cpufreq-nvmem: Add msm8939 as cpr_genpd
>
> .../devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml | 8 ++++++++
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> drivers/cpufreq/qcom-cpufreq-nvmem.c | 9 +++++----
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
ping
prev parent reply other threads:[~2022-05-25 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 16:22 [PATCH 0/5] qcom-cpufreq-nvmem: Add msm8939 with some fixups Bryan O'Donoghue
2022-04-18 16:22 ` [PATCH 1/5] dt-bindings: opp: Add missing compat devices Bryan O'Donoghue
2022-04-26 20:09 ` Rob Herring
2022-04-18 16:22 ` [PATCH 2/5] dt-bindings: opp: Add msm8939 to the compatible list Bryan O'Donoghue
2022-04-26 20:10 ` Rob Herring
2022-04-18 16:22 ` [PATCH 3/5] cpufreq: blocklist Qualcomm msm8939 in cpufreq-dt-platdev Bryan O'Donoghue
2022-04-18 16:22 ` [PATCH 4/5] cpufreq: qcom-cpufreq-nvmem: Rename qcs404 data to cpr_genpd Bryan O'Donoghue
2022-04-18 16:22 ` [PATCH 5/5] cpufreq: qcom-cpufreq-nvmem: Add msm8939 as cpr_genpd Bryan O'Donoghue
2022-05-25 12:51 ` Bryan O'Donoghue [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=ef871d78-12d2-e19e-9a12-6288256116a7@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=ilia.lin@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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