From: Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH] ARM: dts: sun8i: a83t: Add CPU regulator supplies for A83T boards
Date: Wed, 27 Jun 2018 19:04:03 +0200 [thread overview]
Message-ID: <20180627170403.y7ptuiyrhklh7foj@flea> (raw)
In-Reply-To: <20180627022709.27434-1-wens-jdAy2FN1RRM@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Wed, Jun 27, 2018 at 10:27:09AM +0800, Chen-Yu Tsai wrote:
> The OPPs for the A83T CPU cores were added in v4.17 in commit 2db639d8c166
> ("ARM: dts: sun8i: a83t: add stable OPP tables and CPUfreq"), but board
> level regulator supplies for the CPU clusters were only added for the
> TBS-A711 tablet. This means the other A83T boards do not benefit from
> voltage scaling, or worse, if the implementation does not scale the
> frequency when the voltage is fixed, no benefit at all.
>
> Add board level CPU cluster power supplies to all the A83T development
> boards, so they can have proper dynamic CPU voltage and frequency scaling.
>
> Signed-off-by: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-27 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 2:27 [PATCH] ARM: dts: sun8i: a83t: Add CPU regulator supplies for A83T boards Chen-Yu Tsai
[not found] ` <20180627022709.27434-1-wens-jdAy2FN1RRM@public.gmane.org>
2018-06-27 17:04 ` Maxime Ripard [this message]
2018-06-27 18:45 ` [linux-sunxi] " Ondřej Jirman
2018-06-28 3:10 ` Chen-Yu Tsai
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=20180627170403.y7ptuiyrhklh7foj@flea \
--to=maxime.ripard-ldxbnhwyfcjbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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