[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191122073124.GA3296@dell>
Date: Fri, 22 Nov 2019 07:31:24 +0000
From: Lee Jones <lee.jones@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Sven Van Asbroeck <thesven73@...il.com>,
Axel Lin <axel.lin@...ics.com>, Dan Murphy <dmurphy@...com>,
devicetree@...r.kernel.org, Grigoryev Denis <grigoryev@...twel.ru>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>
Subject: Re: Applied "tps6105x: add optional devicetree support" to the
regulator tree
On Wed, 20 Nov 2019, Mark Brown wrote:
> The patch
>
> tps6105x: add optional devicetree support
>
> has been applied to the regulator tree at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.5
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
>
> From 62f7f3eca4c30064ab37b42d97cef4292d75fdd0 Mon Sep 17 00:00:00 2001
> From: Sven Van Asbroeck <thesven73@...il.com>
> Date: Tue, 19 Nov 2019 10:46:08 -0500
> Subject: [PATCH] tps6105x: add optional devicetree support
>
> This driver currently requires platform data to specify the
> operational mode and regulator init data (in case of regulator
> mode).
>
> Optionally specify the operational mode by looking at the name
> of the devicetree child node.
>
> Example: put chip in regulator mode:
>
> i2c0 {
> tps61052@33 {
> compatible = "ti,tps61052";
> reg = <0x33>;
>
> regulator {
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
> regulator-always-on;
> };
> };
> };
>
> Tree: linux-next
> Signed-off-by: Sven Van Asbroeck <TheSven73@...il.com>
> Link: https://lore.kernel.org/r/20191119154611.29625-2-TheSven73@gmail.com
> Signed-off-by: Mark Brown <broonie@...nel.org>
> ---
> drivers/mfd/tps6105x.c | 34 +++++++++++++++++++++++++++++++---
> 1 file changed, 31 insertions(+), 3 deletions(-)
?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists