LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Dan Murphy <dmurphy@ti.com>,
pavel@ucw.cz, broonie@kernel.org, lgirdwood@gmail.com
Cc: lee.jones@linaro.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] LM36274 Introduction
Date: Wed, 22 May 2019 21:37:00 +0200 [thread overview]
Message-ID: <6501a8b5-8068-4c9d-6b51-ef00fa72c6d5@gmail.com> (raw)
In-Reply-To: <20190522192733.13422-1-dmurphy@ti.com>
Hi Dan,
On 5/22/19 9:27 PM, Dan Murphy wrote:
> Hello
>
> This is patch set v4 for the LM36274. There were no changes made
> to this patch set except to rebase this on top of the latest TI LMU common code
> patchset.
Why the rebase was needed? leds-lm36274.c was already including
leds-ti-lmu-common.h.
> This patch set was rebased on the series at:
> https://lore.kernel.org/patchwork/project/lkml/list/?series=393071
>
> Dan
>
> Dan Murphy (6):
> regulator: lm363x: Make the gpio register enable flexible
> dt-bindings: mfd: Add lm36274 bindings to ti-lmu
> mfd: ti-lmu: Add LM36274 support to the ti-lmu
> regulator: lm363x: Add support for LM36274
> dt-bindings: leds: Add LED bindings for the LM36274
> leds: lm36274: Introduce the TI LM36274 LED driver
>
> .../devicetree/bindings/leds/leds-lm36274.txt | 82 +++++++++
> .../devicetree/bindings/mfd/ti-lmu.txt | 54 ++++++
> drivers/leds/Kconfig | 7 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-lm36274.c | 174 ++++++++++++++++++
> drivers/mfd/Kconfig | 5 +-
> drivers/mfd/ti-lmu.c | 14 ++
> drivers/regulator/Kconfig | 2 +-
> drivers/regulator/lm363x-regulator.c | 56 +++++-
> include/linux/mfd/ti-lmu-register.h | 23 +++
> include/linux/mfd/ti-lmu.h | 4 +
> 11 files changed, 416 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt
> create mode 100644 drivers/leds/leds-lm36274.c
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-05-22 19:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:27 Dan Murphy
2019-05-22 19:27 ` [RESEND PATCH v4 1/6] regulator: lm363x: Make the gpio register enable flexible Dan Murphy
2019-05-22 21:22 ` Pavel Machek
2019-05-23 13:03 ` Mark Brown
2019-05-23 13:50 ` Dan Murphy
2019-05-26 12:48 ` Mark Brown
2019-05-29 11:51 ` Dan Murphy
2019-05-29 15:10 ` Mark Brown
2019-05-29 20:47 ` Dan Murphy
2019-05-30 15:26 ` Mark Brown
2019-06-04 15:14 ` Dan Murphy
2019-06-04 15:33 ` Mark Brown
2019-05-22 19:27 ` [RESEND PATCH v4 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu Dan Murphy
2019-05-22 21:22 ` Pavel Machek
2019-05-22 19:27 ` [RESEND PATCH v4 3/6] mfd: ti-lmu: Add LM36274 support to the ti-lmu Dan Murphy
2019-05-23 8:09 ` Pavel Machek
2019-05-22 19:27 ` [RESEND PATCH v4 4/6] regulator: lm363x: Add support for LM36274 Dan Murphy
2019-05-23 8:12 ` Pavel Machek
2019-05-23 13:04 ` Mark Brown
2019-05-22 19:27 ` [RESEND PATCH v4 5/6] dt-bindings: leds: Add LED bindings for the LM36274 Dan Murphy
2019-05-23 12:43 ` Pavel Machek
2019-05-22 19:27 ` [RESEND PATCH v4 6/6] leds: lm36274: Introduce the TI LM36274 LED driver Dan Murphy
2019-05-23 12:50 ` Pavel Machek
2019-05-23 19:09 ` Dan Murphy
2019-05-24 20:51 ` Jacek Anaszewski
2019-05-29 13:58 ` Lee Jones
2019-05-29 20:50 ` Jacek Anaszewski
2019-05-30 7:38 ` Lee Jones
2019-05-30 19:58 ` Jacek Anaszewski
2019-05-31 6:23 ` Lee Jones
2019-05-31 19:44 ` Jacek Anaszewski
2019-05-31 21:07 ` Dan Murphy
2019-05-31 21:57 ` Jacek Anaszewski
2019-05-31 22:41 ` Dan Murphy
2019-06-01 13:55 ` Jacek Anaszewski
2019-05-22 19:37 ` Jacek Anaszewski [this message]
2019-05-22 19:39 ` [PATCH v4 0/6] LM36274 Introduction Dan Murphy
-- strict thread matches above, loose matches on Subject: below --
2019-05-07 20:11 Dan Murphy
2019-05-14 19:11 ` Jacek Anaszewski
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=6501a8b5-8068-4c9d-6b51-ef00fa72c6d5@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=broonie@kernel.org \
--cc=dmurphy@ti.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 \
--subject='Re: [PATCH v4 0/6] LM36274 Introduction' \
/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
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).