From: Heiko Stuebner <heiko@sntech.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko.stuebner@theobroma-systems.com>,
linux-kernel@vger.kernel.org, cmuellner@linux.com,
finley.xiao@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: synchronize rk3399 opps with vendor kernel
Date: Sun, 21 Mar 2021 21:14:31 +0100 [thread overview]
Message-ID: <161635763247.767241.15196995855292324141.b4-ty@sntech.de> (raw)
In-Reply-To: <20210225133322.3420724-1-heiko@sntech.de>
On Thu, 25 Feb 2021 14:33:20 +0100, Heiko Stuebner wrote:
> The vendor-kernel did increase the minimum voltage for some low frequency
> opps to 825mV citing stability reasons. So do that in mainline as well
> and also use the ranged notation the vendor-kernel switched to, to give
> a bit more flexibility for different regulator setups.
Applied, thanks!
[1/3] arm64: dts: rockchip: synchronize rk3399 opps with vendor kernel
commit: 6daae8ff20b8e9d67c282ba37c63e1a7ee3c2206
[2/3] arm64: dts: rockchip: used range'd gpu opps on rk3399
commit: 6d5989a36e60614e12949c6c2dac368b380bf2ca
[3/3] arm64: dts: rockchip: drop separate opp table on rk3399-puma
commit: b417764daa2d7e1325fe926144ffcb4b2bbd8d25
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2021-03-21 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 13:33 [PATCH 1/3] arm64: dts: rockchip: synchronize rk3399 opps with vendor kernel Heiko Stuebner
2021-02-25 13:33 ` [PATCH 2/3] arm64: dts: rockchip: used range'd gpu opps on rk3399 Heiko Stuebner
2021-02-25 13:33 ` [PATCH 3/3] arm64: dts: rockchip: drop separate opp table on rk3399-puma Heiko Stuebner
2021-03-21 20:14 ` Heiko Stuebner [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=161635763247.767241.15196995855292324141.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=cmuellner@linux.com \
--cc=finley.xiao@rock-chips.com \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).