From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Sven Van Asbroeck <thesven73@gmail.com>,
Lee Jones <lee.jones@linaro.org>, Pavel Machek <pavel@ucw.cz>,
Rob Herring <robh+dt@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Grigoryev Denis <grigoryev@fastwel.ru>,
Axel Lin <axel.lin@ingics.com>, Dan Murphy <dmurphy@ti.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 0/2] tps6105x add devicetree and leds support
Date: Thu, 21 Nov 2019 19:20:38 +0100 [thread overview]
Message-ID: <4b64bc1d-681d-8916-7247-a9536afc00c6@gmail.com> (raw)
In-Reply-To: <20191121142726.22856-1-TheSven73@gmail.com>
Hi Sven,
Thank you for the updated set.
For both patches:
Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Best regards,
Jacek Anaszewski
On 11/21/19 3:27 PM, Sven Van Asbroeck wrote:
> v3 -> v4:
> Removed tps6105 mfd patch - it was accepted (Mark Brown).
>
> Use the new LED registration API - suggested by Jacek Anaszewski.
>
> Updated led dt bindings to document function, color usage.
>
> v2 -> v3:
> Removed tps6105x regulator patch - it was accepted (Mark Brown).
>
> Removed devicetree/platdata bindings for tps6105x led naming.
> I can test only with a 4.19 vendor kernel, which does not have the
> latest led naming infrastructure (function/color). Drop devicetree/
> fwnode/pdata led naming in favour of hard-coding to "tps6105x::torch",
> so the patch can be tested by me, yet remains acceptable to upstream.
>
> v1 -> v2:
> Select chip operational mode by looking at subnode name, _not_ its
> compatible property. Suggested by Mark Brown.
>
> I needed led operation for this mfd chip, so I added a very simple
> driver for this.
>
> My platform (arm imx6q) is devicetree-based, so I added optional
> devicetree support for this chip and its sub-drivers.
>
> Sven Van Asbroeck (2):
> leds: tps6105x: add driver for mfd chip led mode
> dt-bindings: mfd: update TI tps6105x chip bindings
>
> .../devicetree/bindings/mfd/tps6105x.txt | 47 ++++++++++-
> drivers/leds/Kconfig | 10 +++
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-tps6105x.c | 83 +++++++++++++++++++
> 4 files changed, 140 insertions(+), 1 deletion(-)
> create mode 100644 drivers/leds/leds-tps6105x.c
>
next prev parent reply other threads:[~2019-11-21 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 14:27 [PATCH v4 0/2] tps6105x add devicetree and leds support Sven Van Asbroeck
2019-11-21 14:27 ` [PATCH v4 1/2] leds: tps6105x: add driver for mfd chip led mode Sven Van Asbroeck
2019-11-21 14:27 ` [PATCH v4 2/2] dt-bindings: mfd: update TI tps6105x chip bindings Sven Van Asbroeck
2019-11-23 0:02 ` Rob Herring
2019-12-09 12:32 ` Lee Jones
2019-12-09 13:44 ` Sven Van Asbroeck
2019-12-10 8:46 ` Lee Jones
2019-12-10 8:46 ` Lee Jones
2019-11-21 18:20 ` Jacek Anaszewski [this message]
2019-11-22 13:36 ` [PATCH v4 0/2] tps6105x add devicetree and leds support Sven Van Asbroeck
2019-11-22 21:04 ` Jacek Anaszewski
2019-11-27 13:15 ` 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=4b64bc1d-681d-8916-7247-a9536afc00c6@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=axel.lin@ingics.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=grigoryev@fastwel.ru \
--cc=lee.jones@linaro.org \
--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).