From: Viresh Kumar <viresh.kumar@linaro.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Yangtao Li <tiny.windzz@gmail.com>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Brandon Cheo Fusi <fusibrandon13@gmail.com>,
Martin Botka <martin.botka@somainline.org>,
Martin Botka <martin.botka1@gmail.com>,
Chris Morgan <macroalpha82@gmail.com>,
Ryan Walklin <ryan@testtoast.com>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v5 0/8] cpufreq: sun50i: Add Allwinner H616 support
Date: Fri, 19 Apr 2024 12:44:50 +0530 [thread overview]
Message-ID: <20240419071450.7aiheeoyq35yjoo7@vireshk-i7> (raw)
In-Reply-To: <20240418154408.1740047-1-andre.przywara@arm.com>
On 18-04-24, 16:44, Andre Przywara wrote:
> This series adds cpufreq support to the Allwinner H616 SoC.
> v5 just removes the explicit H700 speedbin support, as this proved to be
> problematic/unstable in testing. The rest is the same as v4.
> This is based on Martin's original series from about half a year ago[1].
> Thanks for the comments on the list!
> See below for a changelog.
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2024-04-19 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:44 [PATCH v5 0/8] cpufreq: sun50i: Add Allwinner H616 support Andre Przywara
2024-04-18 15:44 ` [PATCH v5 1/8] firmware: smccc: Export revision soc_id function Andre Przywara
2024-04-18 15:44 ` [PATCH v5 2/8] cpufreq: dt-platdev: Blocklist Allwinner H616/618 SoCs Andre Przywara
2024-04-18 15:44 ` [PATCH v5 3/8] dt-bindings: opp: Describe H616 OPPs and opp-supported-hw Andre Przywara
2024-04-18 15:44 ` [PATCH v5 4/8] cpufreq: sun50i: Refactor speed bin decoding Andre Przywara
2024-04-18 15:44 ` [PATCH v5 5/8] cpufreq: sun50i: Add support for opp_supported_hw Andre Przywara
2024-04-18 15:44 ` [PATCH v5 6/8] cpufreq: sun50i: Add H616 support Andre Przywara
2024-04-18 15:44 ` [PATCH v5 7/8] arm64: dts: allwinner: h616: Add CPU OPPs table Andre Przywara
2024-04-18 15:44 ` [PATCH v5 8/8] arm64: dts: allwinner: h616: enable DVFS for all boards Andre Przywara
2024-04-19 7:14 ` Viresh Kumar [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=20240419071450.7aiheeoyq35yjoo7@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fusibrandon13@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=macroalpha82@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.botka1@gmail.com \
--cc=martin.botka@somainline.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tiny.windzz@gmail.com \
--cc=vireshk@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).