public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Cc: linux-rockchip@lists.infradead.org, arm@kernel.org,
	Thierry Reding <treding@nvidia.com>,
	Kevin Hilman <khilman@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-kernel@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Arnd Bergmann <arnd@arndb.de>, Lee Jones <lee.jones@linaro.org>,
	Olof Johansson <olof@lixom.net>, Ray Jui <rjui@broadcom.com>,
	Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH v2 2/5] ARM: multi_v7_defconfig: Enable common regulators for rockchip boards
Date: Fri, 25 Sep 2015 00:10:16 +0200	[thread overview]
Message-ID: <5471789.IH6TzhIBOd@diego> (raw)
In-Reply-To: <1443094759-28531-3-git-send-email-sjoerd.simons@collabora.co.uk>

Am Donnerstag, 24. September 2015, 13:39:16 schrieb Sjoerd Simons:
> Rockchip boards seem to have two common regulator setups. Various board
> used the Active Semi act8846 often in combination with Silergy syr82x

For people just skimming over these patches, the syr82x are siblings to the 
fan53555 - same register interface and all, thus that option gets enabled.


> regulators (e.g. Radxa Rock Pro/Rock 2, Firefly, and Netxeon R89 etc),
> while others use regulator part of the Rockchip RK808 chip (e.g. the
> various Veyron based chromebooks, Chipspark Popmetal etc)
> 
> Enable all these regulators.
> 
> Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
> 
> ---
> 
> Changes in v2:
> - Enable all common rockchip regulators, not just ACT8846
> 
>  arch/arm/configs/multi_v7_defconfig | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm/configs/multi_v7_defconfig
> b/arch/arm/configs/multi_v7_defconfig index 170f18e..3938f54 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -394,6 +394,7 @@ CONFIG_MFD_MAX14577=y
>  CONFIG_MFD_MAX77686=y
>  CONFIG_MFD_MAX77693=y
>  CONFIG_MFD_MAX8907=y
> +CONFIG_MFD_RK808=y
>  CONFIG_MFD_SEC_CORE=y
>  CONFIG_MFD_STMPE=y
>  CONFIG_MFD_PALMAS=y
> @@ -401,11 +402,14 @@ CONFIG_MFD_TPS65090=y
>  CONFIG_MFD_TPS6586X=y
>  CONFIG_MFD_TPS65910=y
>  CONFIG_REGULATOR_AB8500=y
> +CONFIG_REGULATOR_ACT8865=y
>  CONFIG_REGULATOR_AS3711=y
>  CONFIG_REGULATOR_AS3722=y
>  CONFIG_REGULATOR_AXP20X=y
>  CONFIG_REGULATOR_BCM590XX=y
>  CONFIG_REGULATOR_DA9210=y
> +CONFIG_REGULATOR_FAN53555=y
> +CONFIG_REGULATOR_RK808=y
>  CONFIG_REGULATOR_GPIO=y
>  CONFIG_MFD_SYSCON=y
>  CONFIG_POWER_RESET_SYSCON=y


  reply	other threads:[~2015-09-24 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:39 [PATCH v2 0/5] ARM: multi_v7_defconfig: Improve rockchip support Sjoerd Simons
2015-09-24 11:39 ` [PATCH v2 1/5] ARM: multi_v7_defconfig: Enable common Rockchip devices/busses Sjoerd Simons
2015-09-24 11:39 ` [PATCH v2 2/5] ARM: multi_v7_defconfig: Enable common regulators for rockchip boards Sjoerd Simons
2015-09-24 22:10   ` Heiko Stübner [this message]
2015-09-24 11:39 ` [PATCH v2 3/5] ARM: multi_v7_defconfig: Enable Rockchip display support Sjoerd Simons
2015-09-24 11:39 ` [PATCH v2 4/5] ARM: multi_v7_defconfig: Enable the Rockchip USB 2.0 phy Sjoerd Simons
2015-09-24 11:39 ` [PATCH v2 5/5] ARM: multi_v7_defconfig: Support RTC devices commonly used on Rockchip boards Sjoerd Simons
2015-09-24 22:13 ` [PATCH v2 0/5] ARM: multi_v7_defconfig: Improve rockchip support Heiko Stübner
2015-10-06 14:14   ` Arnd Bergmann

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=5471789.IH6TzhIBOd@diego \
    --to=heiko@sntech.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=javier@osg.samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=rjui@broadcom.com \
    --cc=sjoerd.simons@collabora.co.uk \
    --cc=swarren@nvidia.com \
    --cc=treding@nvidia.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