From: Mark Brown <broonie@kernel.org>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
mturquette@baylibre.com, sboyd@codeaurora.org,
lee.jones@linaro.org, lgirdwood@gmail.com, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, dianders@chromium.org,
zyw@rock-chips.com
Subject: Re: [PATCH v2 4/7] regulator: rk808: Add regulator driver for RK818
Date: Thu, 21 Apr 2016 17:02:32 +0100 [thread overview]
Message-ID: <20160421160232.GU3217@sirena.org.uk> (raw)
In-Reply-To: <1461244361-45686-5-git-send-email-w.egorov@phytec.de>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
On Thu, Apr 21, 2016 at 03:12:38PM +0200, Wadim Egorov wrote:
> Add support for the rk818 regulator. The regulator module consists
> of 4 DCDCs, 9 LDOs, 1 switch and 1 BOOST converter which is used to
> power OTG and HDMI5V.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-21 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 13:12 [PATCH v2 0/5] Add support for rk818 Wadim Egorov
2016-04-21 13:12 ` [PATCH v2 1/7] drivers: mfd: rk808: rename rk808 struct to rk8xx Wadim Egorov
2016-04-21 14:20 ` Alexandre Belloni
2016-04-21 13:12 ` [PATCH v2 2/7] mfd: RK808: Add RK818 support Wadim Egorov
2016-04-21 13:12 ` [PATCH v2 5/7] mfd: dt-bindings: Add RK818 device tree bindings document Wadim Egorov
2016-04-22 20:25 ` Rob Herring
2016-04-21 13:12 ` [PATCH v2 6/7] clk: Kconfig: Name RK818 in Kconfig for COMMON_CLK_RK808 Wadim Egorov
[not found] ` <1461244361-45686-7-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-04-22 21:37 ` Stephen Boyd
[not found] ` <1461244361-45686-1-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-04-21 13:12 ` [PATCH v2 3/7] regulator: rk808: Migrate to regulator core's simplified DT parsing code Wadim Egorov
[not found] ` <1461244361-45686-4-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-04-21 16:01 ` Mark Brown
2016-04-22 9:03 ` Wadim Egorov
[not found] ` <5719E8CD.1070304-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-04-22 9:41 ` Mark Brown
2016-04-21 13:12 ` [PATCH v2 4/7] regulator: rk808: Add regulator driver for RK818 Wadim Egorov
2016-04-21 16:02 ` Mark Brown [this message]
2016-04-21 13:12 ` [PATCH v2 7/7] rtc: Kconfig: Name RK818 in Kconfig for RTC_DRV_RK808 Wadim Egorov
[not found] ` <1461244361-45686-8-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-04-21 14:35 ` Alexandre Belloni
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=20160421160232.GU3217@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sboyd@codeaurora.org \
--cc=w.egorov@phytec.de \
--cc=zyw@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).