From: Rob Herring <robh@kernel.org>
Cc: robh+dt@kernel.org, jacek.anaszewski@gmail.com, pavel@ucw.cz,
lee.jones@linaro.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: LMU: Add ti,brightness-resolution
Date: Mon, 29 Apr 2019 12:33:38 -0500 [thread overview]
Message-ID: <20190429173338.GA32250@bogus> (raw)
In-Reply-To: <20190405142855.3969-2-dmurphy@ti.com>
On Fri, 5 Apr 2019 09:28:51 -0500, Dan Murphy wrote:
> Add ti,brightness-resolution to the TI LMU binding to define
> whether the device uses 8-bit brightness or 11-bit brightness.
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v2 - New patch. Add brightness resolution to ti-lmu.txt. See patch comments
> for context. - https://lore.kernel.org/patchwork/patch/1054501/
>
> Documentation/devicetree/bindings/mfd/ti-lmu.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-04-29 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 14:28 [PATCH v2 1/6] dt-bindings: mfd: LMU: Add the ramp up/down property Dan Murphy
2019-04-05 14:28 ` [PATCH v2 2/6] dt-bindings: mfd: LMU: Add ti,brightness-resolution Dan Murphy
2019-04-29 17:33 ` Rob Herring [this message]
2019-04-05 14:28 ` [PATCH v2 3/6] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-04-05 14:28 ` [PATCH v2 4/6] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-04-11 19:48 ` Jacek Anaszewski
2019-04-12 19:34 ` Jacek Anaszewski
2019-04-24 19:24 ` Dan Murphy
2019-04-29 17:34 ` Rob Herring
2019-04-05 14:28 ` [PATCH v2 5/6] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-04-05 14:28 ` [PATCH v2 6/6] leds: lm3697: Introduce the lm3697 driver Dan Murphy
2019-04-29 17:32 ` [PATCH v2 1/6] dt-bindings: mfd: LMU: Add the ramp up/down property Rob Herring
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=20190429173338.GA32250@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--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).