From: Rob Herring <robh@kernel.org>
Cc: robh+dt@kernel.org, jacek.anaszewski@gmail.com, pavel@ucw.cz,
lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, Dan Murphy <dmurphy@ti.com>
Subject: Re: [PATCH v2 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu
Date: Mon, 29 Apr 2019 13:00:25 -0500 [thread overview]
Message-ID: <20190429180025.GA15562@bogus> (raw)
In-Reply-To: <20190410133833.28859-2-dmurphy@ti.com>
On Wed, 10 Apr 2019 08:38:29 -0500, Dan Murphy wrote:
> Add the LM36274 backlight driver with regulator support.
> This is a multi-function device for backlight applications.
>
> Backlight properties will be documented in it's a supplemental
> bindings document.
>
> Regulator support is documented in the regulator/lm363x-regulator.txt
>
> http://www.ti.com/lit/ds/symlink/lm36274.pdf
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v2 - No changes - https://lore.kernel.org/patchwork/patch/1058776/
>
> .../devicetree/bindings/mfd/ti-lmu.txt | 54 +++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-04-29 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 13:38 [PATCH v2 1/6] regulator: lm363x: Make the gpio register enable flexible Dan Murphy
2019-04-10 13:38 ` [PATCH v2 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu Dan Murphy
2019-04-29 18:00 ` Rob Herring [this message]
2019-04-10 13:38 ` [PATCH v2 3/6] mfd: ti-lmu: Add LM36274 support to the ti-lmu Dan Murphy
2019-04-10 13:38 ` [PATCH v2 4/6] regulator: lm363x: Add support for LM36274 Dan Murphy
2019-04-10 13:38 ` [PATCH v2 5/6] dt-bindings: leds: Add LED bindings for the LM36274 Dan Murphy
2019-04-29 18:01 ` Rob Herring
2019-04-10 13:38 ` [PATCH v2 6/6] leds: lm36274: Introduce the TI LM36274 LED driver Dan Murphy
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=20190429180025.GA15562@bogus \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
/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).