From: Dan Murphy <dmurphy@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>, <robh@kernel.org>,
<marek.behun@nic.cz>
Cc: <devicetree@vger.kernel.org>, <linux-leds@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v32 0/6] Multicolor Framework v32
Date: Wed, 22 Jul 2020 10:31:40 -0500 [thread overview]
Message-ID: <20200722153146.8767-1-dmurphy@ti.com> (raw)
Hello
This is the remaining patches in the multicolor framework series. Only the
LP50xx driver has been updated per the review comment here
https://lore.kernel.org/patchwork/patch/1274070/
In addition to these fixes fixes for the enable/disable and reset functions have
also been updated.
Summary:
Converted links from http->https
Fixed comment style
Fixed enable/disable function
Refactored probe_dt code
Fixed checkpatch style issues
Fixed issues when building with W=1 C=1
Dan Murphy (6):
dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers
leds: lp50xx: Add the LP50XX family of the RGB LED driver
ARM: defconfig: u8500: Add LP55XX_COMMON config flag
ARM: dts: n900: Add reg property to the LP5523 channel node
ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 channel node
ARM: dts: ste-href: Add reg property to the LP5521 channel nodes
.../devicetree/bindings/leds/leds-lp50xx.yaml | 130 +++
arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 14 +-
arch/arm/boot/dts/omap3-n900.dts | 29 +-
arch/arm/boot/dts/ste-href.dtsi | 22 +-
arch/arm/configs/u8500_defconfig | 1 +
drivers/leds/Kconfig | 11 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-lp50xx.c | 791 ++++++++++++++++++
8 files changed, 980 insertions(+), 19 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.yaml
create mode 100644 drivers/leds/leds-lp50xx.c
--
2.27.0
next reply other threads:[~2020-07-22 15:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 15:31 Dan Murphy [this message]
2020-07-22 15:31 ` [PATCH v32 1/6] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2020-07-28 13:39 ` Dan Murphy
2020-08-04 19:55 ` Dan Murphy
2020-08-07 13:42 ` Dan Murphy
2020-08-11 10:32 ` Pavel Machek
2020-08-11 10:20 ` Pavel Machek
2020-08-11 17:07 ` Dan Murphy
2020-07-22 15:31 ` [PATCH v32 2/6] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2020-08-11 10:29 ` Pavel Machek
2020-08-11 10:31 ` Pavel Machek
2020-08-11 10:54 ` Pavel Machek
2020-08-11 17:27 ` Dan Murphy
2020-08-11 22:01 ` Pavel Machek
2020-08-11 22:16 ` Dan Murphy
2020-08-11 22:26 ` Pavel Machek
2020-08-12 16:00 ` Dan Murphy
2020-07-22 15:31 ` [PATCH v32 3/6] ARM: defconfig: u8500: Add LP55XX_COMMON config flag Dan Murphy
2020-07-28 13:38 ` Dan Murphy
2020-08-03 23:14 ` Linus Walleij
2020-07-22 15:31 ` [PATCH v32 4/6] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2020-07-22 15:31 ` [PATCH v32 5/6] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2020-07-22 15:31 ` [PATCH v32 6/6] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes 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=20200722153146.8767-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=pavel@ucw.cz \
--cc=robh@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).