devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support
Date: Tue, 24 Apr 2018 10:10:27 +0800	[thread overview]
Message-ID: <CAGb2v64zj=DHW2ta9d7=SGGbE2BZUeigJw=NqJMUfK0aV9+Aow@mail.gmail.com> (raw)
In-Reply-To: <CAGb2v67FaU3_su9XGaGj4zVSoAnpfN8cAhbBHEJu3Owt=Qicmg@mail.gmail.com>

On Mon, Apr 16, 2018 at 12:41 PM, Chen-Yu Tsai <wens@csie.org> wrote:
> Hi,
>
> On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
>> This patchset tries to add DVFS support for Allwinner H3 SoC,
>> considering two kinds of adjustable regulators used on H3 boards:
>> SY8106A I2C-controlled regulator and SY8113B regulator (controllable
>> by GPIO with some special designs on the board), and also taking the
>> uncontrollable boards into consider.
>>
>> PATCH 1 and PATCH 2 are for the SY8106A regulator, then PATCH 3 and
>> PATCH 4 are for the r_i2c bus, which is used by boards with SY8106A
>> to communicate with the regulator.
>>
>> PATCH 5 adds the operating points v2 table to the H3 SoC, but with
>> OPPs higher than 1008MHz temporarily dropped.
>>
>> Then there's patches for several tested boards: Orange Pi PC (with
>> SY8106A), Orange Pi One/Zero (with GPIO-adjustable SY8113B) and
>> ALL-H3-CC (unadjustable).
>>
>> Icenowy Zheng (5):
>>   ARM: sun8i: h3: add operating-points-v2 table for CPU
>>   ARM: sun8i: h2+: add SY8113B regulator used by Orange Pi Zero board
>>   ARM: sun8i: h3: add SY8113B regulator used by Orange Pi One board
>>   ARM: sun8i: h3: fix ALL-H3-CC H3 ver VDD-CPUX voltage
>>   ARM: sun8i: h3: set the cpu-supply to VDD-CPUX on ALL-H3-CC H3 ver
>>
>> Ondrej Jirman (5):
>>   dt-bindings: add binding for the SY8106A voltage regulator
>>   regulator: add support for SY8106A regulator
>>   ARM: sunxi: h3/h5: Add r_i2c pinmux node
>>   ARM: sunxi: h3/h5: Add r_i2c I2C controller
>>   ARM: sun8i: h3: Add SY8106A regulator to Orange Pi PC

Dropped this patch at your request. The rest will be in -next.

ChenYu

>
> I've applied all the device tree patches for 4.18, taking into account
> comments from Maxime. See
>
>     https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git/log/?h=sunxi/h3-h5-for-4.17
>
> Mostly it's just renaming the regulator node names and labels.
>
> Please resend the first two patches to Mark Brown, the regulator
> subsystem maintainer. And you might want to mention the branch
> above in case he needs a use case reference.
>
> Regards
> ChenYu

  parent reply	other threads:[~2018-04-24  2:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06  4:48 [PATCH v2 00/10] Allwinner H3 DVFS support Icenowy Zheng
2018-02-06  4:48 ` [PATCH v2 01/10] dt-bindings: add binding for the SY8106A voltage regulator Icenowy Zheng
     [not found] ` <20180206044905.30508-1-icenowy-h8G6r0blFSE@public.gmane.org>
2018-02-06  4:48   ` [PATCH v2 02/10] regulator: add support for SY8106A regulator Icenowy Zheng
     [not found]     ` <20180206044905.30508-3-icenowy-h8G6r0blFSE@public.gmane.org>
2018-03-30  8:03       ` Chen-Yu Tsai
2018-02-06  4:48   ` [PATCH v2 03/10] ARM: sunxi: h3/h5: Add r_i2c pinmux node Icenowy Zheng
2018-02-06  4:48   ` [PATCH v2 04/10] ARM: sunxi: h3/h5: Add r_i2c I2C controller Icenowy Zheng
2018-02-06  4:49   ` [PATCH v2 05/10] ARM: sun8i: h3: add operating-points-v2 table for CPU Icenowy Zheng
     [not found]     ` <20180206044905.30508-6-icenowy-h8G6r0blFSE@public.gmane.org>
2018-02-06  9:06       ` Maxime Ripard
2018-02-06  9:10         ` Icenowy Zheng
2018-02-06  4:49   ` [PATCH v2 06/10] ARM: sun8i: h2+: add SY8113B regulator used by Orange Pi Zero board Icenowy Zheng
     [not found]     ` <20180206044905.30508-7-icenowy-h8G6r0blFSE@public.gmane.org>
2018-03-30  7:49       ` Chen-Yu Tsai
2018-02-06  4:49   ` [PATCH v2 07/10] ARM: sun8i: h3: add SY8113B regulator used by Orange Pi One board Icenowy Zheng
2018-02-06  9:10     ` Maxime Ripard
2018-02-06  4:49   ` [PATCH v2 08/10] ARM: sun8i: h3: Add SY8106A regulator to Orange Pi PC Icenowy Zheng
     [not found]     ` <20180206044905.30508-9-icenowy-h8G6r0blFSE@public.gmane.org>
2018-03-30  8:16       ` Chen-Yu Tsai
2018-02-06  4:49   ` [PATCH v2 10/10] ARM: sun8i: h3: set the cpu-supply to VDD-CPUX on ALL-H3-CC H3 ver Icenowy Zheng
2018-04-16  4:41   ` [PATCH v2 00/10] Allwinner H3 DVFS support Chen-Yu Tsai
     [not found]     ` <CAGb2v67FaU3_su9XGaGj4zVSoAnpfN8cAhbBHEJu3Owt=Qicmg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-16  4:47       ` Chen-Yu Tsai
2018-04-24  2:10     ` Chen-Yu Tsai [this message]
2018-02-06  4:49 ` [PATCH v2 09/10] ARM: sun8i: h3: fix ALL-H3-CC H3 ver VDD-CPUX voltage Icenowy Zheng
     [not found]   ` <20180206044905.30508-10-icenowy-h8G6r0blFSE@public.gmane.org>
2018-03-30  7:43     ` 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='CAGb2v64zj=DHW2ta9d7=SGGbE2BZUeigJw=NqJMUfK0aV9+Aow@mail.gmail.com' \
    --to=wens@csie.org \
    --cc=devicetree@vger.kernel.org \
    --cc=icenowy@aosc.io \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@bootlin.com \
    /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).