devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Tony Xie <tony.xie@rock-chips.com>
Cc: heiko@sntech.de, broonie@kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, a.zummo@towertech.it,
	alexandre.belloni@bootlin.com, sboyd@kernel.org,
	linux-clk@vger.kernel.org, linux-rtc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, chenjh@rock-chips.com,
	xsf@rock-chips.com, zhangqing@rock-chips.com,
	huangtao@rock-chips.com
Subject: Re: [PATCH v10 0/6] support a new type of PMIC,including two chips(rk817 and rk809)
Date: Wed, 26 Jun 2019 12:52:51 +0100	[thread overview]
Message-ID: <20190626115251.GR21119@dell> (raw)
In-Reply-To: <20190621103258.8154-1-tony.xie@rock-chips.com>

On Fri, 21 Jun 2019, Tony Xie wrote:

> Most of functions and registers of the rk817 and rk808 are the same,
> so they can share allmost all codes.
> 
> Their specifications are as follows:
>   1) The RK809 and RK809 consist of 5 DCDCs, 9 LDOs and have the same
> registers
>      for these components except dcdc5.
>   2) The dcdc5 is a boost dcdc for RK817 and is a buck for RK809.
>   3) The RK817 has one switch but The Rk809 has two.

Just tried to apply this set to a v5.2-rc1 base, but it doesn't seem
to do so cleanly.  Would you be able to rebase and resend please?

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2019-06-26 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 10:32 [PATCH v10 0/6] support a new type of PMIC,including two chips(rk817 and rk809) Tony Xie
2019-06-21 10:32 ` [PATCH v10 1/6] mfd: rk808: remove the id_table Tony Xie
2019-06-26 11:53   ` Lee Jones
2019-06-21 10:32 ` [PATCH v10 2/6] mfd: rk808: Add RK817 and RK809 support Tony Xie
2019-06-21 10:32 ` [PATCH v10 3/6] regulator: rk808: add RK809 and RK817 support Tony Xie
2019-06-26 12:29   ` [PATCH v10.1 " Heiko Stuebner
2019-06-21 10:32 ` [PATCH v10 4/6] dt-bindings: mfd: rk808: Add binding information for RK809 and RK817 Tony Xie
2019-06-21 10:34 ` [PATCH v10 5/6] rtc: rk808: add RK809 and RK817 support Tony Xie
2019-06-21 10:34 ` [PATCH v10 6/6] clk: RK808: " Tony Xie
2019-06-26 11:52 ` Lee Jones [this message]
2019-06-27  8:18   ` [PATCH v10 0/6] support a new type of PMIC,including two chips(rk817 and rk809) Heiko Stuebner
2019-06-27 13:59 ` [GIT PULL] Immutable branch between MFD, Clk, Regulator and RTC due for the v5.3 merge window Lee Jones

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=20190626115251.GR21119@dell \
    --to=lee.jones@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=chenjh@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tony.xie@rock-chips.com \
    --cc=xsf@rock-chips.com \
    --cc=zhangqing@rock-chips.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).