From: Brandon Cheo Fusi <fusibrandon13@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Yangtao Li <tiny.windzz@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Brandon Cheo Fusi <fusibrandon13@gmail.com>
Subject: [RFC PATCH v2 0/3] Add support for reading D1 efuse speed bin
Date: Thu, 21 Dec 2023 11:10:10 +0100 [thread overview]
Message-ID: <20231221101013.67204-1-fusibrandon13@gmail.com> (raw)
Hi everyone,
This series is an attempt to get feedback on decoding D1 efuse speed bins
in the Sun50i H6 cpufreq driver, and turning the result into a meaningful
value that selects voltage ranges in an OPP table.
I want to make sure I get this right before sending in a v3 of the D1
cpufreq support series here
https://lore.kernel.org/linux-sunxi/20231218110543.64044-1-fusibrandon13@gmail.com/T/#t
which is currently stuck at
https://lore.kernel.org/linux-sunxi/aad8302d-a015-44ee-ad11-1a4c6e00074c@sholland.org/
Changes in v2:
- Make speed bin decoding generic in one patch and add D1 support in a
separate patch
- Fix OPP voltage ranges to avoid stability issues
Brandon Cheo Fusi (3):
cpufreq: sun50i: Refactor speed bin decoding
cpufreq: sun50i: Add support for D1's speed bin decoding
riscv: dts: allwinner: Fill in OPPs
arch/riscv/boot/dts/allwinner/sun20i-d1s.dtsi | 19 +++-
drivers/cpufreq/sun50i-cpufreq-nvmem.c | 89 +++++++++++++++----
2 files changed, 89 insertions(+), 19 deletions(-)
--
2.30.2
next reply other threads:[~2023-12-21 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 10:10 Brandon Cheo Fusi [this message]
2023-12-21 10:10 ` [RFC PATCH v2 1/3] cpufreq: sun50i: Refactor speed bin decoding Brandon Cheo Fusi
2023-12-21 10:10 ` [RFC PATCH v2 2/3] cpufreq: sun50i: Add support for D1's " Brandon Cheo Fusi
2023-12-21 12:49 ` Andre Przywara
2023-12-21 17:11 ` Brandon Cheo Fusi
2023-12-21 17:26 ` Andre Przywara
2023-12-21 10:10 ` [RFC PATCH v2 3/3] riscv: dts: allwinner: Fill in OPPs Brandon Cheo Fusi
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=20231221101013.67204-1-fusibrandon13@gmail.com \
--to=fusibrandon13@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=sfr@canb.auug.org.au \
--cc=tiny.windzz@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.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).