[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGngYiWQixey6t_4evqPdS9Rw+VNf0M1nax8bEqaUt=nLDjEfw@mail.gmail.com>
Date: Mon, 18 Nov 2019 16:17:49 -0500
From: Sven Van Asbroeck <thesven73@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Grigoryev Denis <grigoryev@...twel.ru>,
Axel Lin <axel.lin@...ics.com>, Dan Murphy <dmurphy@...com>,
Mark Rutland <mark.rutland@....com>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v1 1/4] tps6105x: add optional devicetree support
On Mon, Nov 18, 2019 at 3:34 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Mon, Nov 18, 2019 at 01:13:24PM -0500, Sven Van Asbroeck wrote:
>
> Is the regulator bit of this perhaps a voltage regulator and a current
> regulator packaged together mainly for use powering LEDs? That's a
> hardware design I've seen before...
Yes, you nailed it :)
>
> Just point the regulator framework at the MFD's DT node - the children
> of the MFD can look at the parent device happily, there's several
> existing MFDs do this.
Ok, I think I get it now. Will prepare v2.
Powered by blists - more mailing lists