From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Sven Van Asbroeck <thesven73@gmail.com>,
Axel Lin <axel.lin@ingics.com>, Dan Murphy <dmurphy@ti.com>,
devicetree@vger.kernel.org,
Grigoryev Denis <grigoryev@fastwel.ru>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>, Pavel Machek <pavel@ucw.cz>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: Applied "tps6105x: add optional devicetree support" to the regulator tree
Date: Fri, 22 Nov 2019 14:42:35 +0000 [thread overview]
Message-ID: <20191122144235.GD3296@dell> (raw)
In-Reply-To: <20191122133230.GD6849@sirena.org.uk>
On Fri, 22 Nov 2019, Mark Brown wrote:
> On Fri, Nov 22, 2019 at 07:31:24AM +0000, Lee Jones wrote:
> > On Wed, 20 Nov 2019, Mark Brown wrote:
>
> > > 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;
> > > };
> > > };
> > > };
>
> > ?
>
> Sorry, I completely missed that this was adding a MFD file - the binding
> only mentioned regulator stuff and I clearly didn't look at the
> filename. Do you want me to drop it?
It's okay. Probably won't cause too much chaos. Keep it applied.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-11-22 14:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:46 [PATCH v2 0/4] tps6105x add devicetree and leds support Sven Van Asbroeck
2019-11-19 15:46 ` [PATCH v2 1/4] tps6105x: add optional devicetree support Sven Van Asbroeck
2019-11-20 17:18 ` Applied "tps6105x: add optional devicetree support" to the regulator tree Mark Brown
2019-11-22 7:31 ` Lee Jones
2019-11-22 13:32 ` Mark Brown
2019-11-22 13:39 ` Sven Van Asbroeck
2019-11-22 14:42 ` Lee Jones [this message]
2019-11-19 15:46 ` [PATCH v2 2/4] regulator: tps6105x: add optional devicetree support Sven Van Asbroeck
2019-11-19 18:14 ` Mark Brown
2019-11-19 18:21 ` Sven Van Asbroeck
2019-11-20 17:18 ` Applied "regulator: tps6105x: add optional devicetree support" to the regulator tree Mark Brown
2019-11-19 15:46 ` [PATCH v2 3/4] leds: tps6105x: add driver for mfd chip led mode Sven Van Asbroeck
2019-11-19 18:32 ` Dan Murphy
2019-11-19 18:59 ` Sven Van Asbroeck
2019-11-19 21:52 ` Sven Van Asbroeck
2019-11-19 15:46 ` [PATCH v2 4/4] dt-bindings: mfd: update TI tps6105x chip bindings Sven Van Asbroeck
2019-11-19 18:36 ` Dan Murphy
2019-11-19 19:03 ` Sven Van Asbroeck
2019-11-19 19:38 ` Jacek Anaszewski
2019-11-19 20:22 ` Sven Van Asbroeck
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=20191122144235.GD3296@dell \
--to=lee.jones@linaro.org \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=grigoryev@fastwel.ru \
--cc=jacek.anaszewski@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=thesven73@gmail.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).