From: Gene Chen <gene.chen.richtek@gmail.com>
To: jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org,
matthias.bgg@gmail.com
Cc: dmurphy@ti.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
gene_chen@richtek.com, Wilma.Wu@mediatek.com,
shufan_lee@richtek.com, cy_huang@richtek.com,
benjamin.chao@mediatek.com
Subject: [PATCH resend v13 0/5] leds: mt6360: Add LED driver for MT6360
Date: Thu, 24 Dec 2020 09:47:15 +0800 [thread overview]
Message-ID: <1608774440-21655-1-git-send-email-gene.chen.richtek@gmail.com> (raw)
This patch series add MT6360 LED support contains driver and binding document
Gene Chen (5)
leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH
leds: flash: Fix multicolor no-ops registration by return 0
dt-bindings: leds: Add LED_COLOR_ID_MOONLIGHT definitions
dt-bindings: leds: Add bindings for MT6360 LED
leds: mt6360: Add LED driver for MT6360
Documentation/devicetree/bindings/leds/leds-mt6360.yaml | 159 +++
drivers/leds/Kconfig | 13
drivers/leds/Makefile | 1
drivers/leds/leds-mt6360.c | 827 ++++++++++++++++
include/dt-bindings/leds/common.h | 1
include/linux/led-class-flash.h | 42
include/linux/led-class-multicolor.h | 42
7 files changed, 1049 insertions(+), 36 deletions(-)
changelogs between v1 & v2
- add led driver with mfd
changelogs between v2 & v3
- independent add led driver
- add dt-binding document
- refactor macros definition for easy to debug
- parse device tree by fwnode
- use devm*ext to register led class device
changelogs between v3 & v4
- fix binding document description
- use GENMASK and add unit postfix to definition
- isink register led class device
changelogs between v4 & v5
- change rgb isink to multicolor control
- add binding reference to mfd yaml
changelogs between v5 & v6
- Use DT to decide RGB LED is multicolor device or indicator device only
changelogs between v6 & v7
- Add binding multicolor device sample code
- Add flash ops mutex lock
- Remove V4L2 init with indicator device
changelogs between v7 & v8
- Add mutex for led fault get ops
- Fix flash and multicolor no-ops return 0
- Add LED_FUNCTION_MOONLIGHT
changelogs between v8 & v9
- reuse api in flash and multicolor header
changelogs between v9 & v10
- add comment for reuse registration functions in flash and multicolor
changelogs between v10 & v11
- match dt-binding reg property comment to the functionality name
- remove exist patch in linux-next
- dicide multicolor channel by color definitiion
changelogs between v11 & v12
- Fix print size_t by %zu
- Fix dt-binding name regular experssion
changelogs between v12 & v13
- Fix kbuild test rebot build error
WARNING: multiple messages have this Message-ID (diff)
From: Gene Chen <gene.chen.richtek@gmail.com>
To: jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org,
matthias.bgg@gmail.com
Cc: gene_chen@richtek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cy_huang@richtek.com,
benjamin.chao@mediatek.com, linux-mediatek@lists.infradead.org,
dmurphy@ti.com, linux-leds@vger.kernel.org,
Wilma.Wu@mediatek.com, linux-arm-kernel@lists.infradead.org,
shufan_lee@richtek.com
Subject: [PATCH resend v13 0/5] leds: mt6360: Add LED driver for MT6360
Date: Thu, 24 Dec 2020 09:47:15 +0800 [thread overview]
Message-ID: <1608774440-21655-1-git-send-email-gene.chen.richtek@gmail.com> (raw)
This patch series add MT6360 LED support contains driver and binding document
Gene Chen (5)
leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH
leds: flash: Fix multicolor no-ops registration by return 0
dt-bindings: leds: Add LED_COLOR_ID_MOONLIGHT definitions
dt-bindings: leds: Add bindings for MT6360 LED
leds: mt6360: Add LED driver for MT6360
Documentation/devicetree/bindings/leds/leds-mt6360.yaml | 159 +++
drivers/leds/Kconfig | 13
drivers/leds/Makefile | 1
drivers/leds/leds-mt6360.c | 827 ++++++++++++++++
include/dt-bindings/leds/common.h | 1
include/linux/led-class-flash.h | 42
include/linux/led-class-multicolor.h | 42
7 files changed, 1049 insertions(+), 36 deletions(-)
changelogs between v1 & v2
- add led driver with mfd
changelogs between v2 & v3
- independent add led driver
- add dt-binding document
- refactor macros definition for easy to debug
- parse device tree by fwnode
- use devm*ext to register led class device
changelogs between v3 & v4
- fix binding document description
- use GENMASK and add unit postfix to definition
- isink register led class device
changelogs between v4 & v5
- change rgb isink to multicolor control
- add binding reference to mfd yaml
changelogs between v5 & v6
- Use DT to decide RGB LED is multicolor device or indicator device only
changelogs between v6 & v7
- Add binding multicolor device sample code
- Add flash ops mutex lock
- Remove V4L2 init with indicator device
changelogs between v7 & v8
- Add mutex for led fault get ops
- Fix flash and multicolor no-ops return 0
- Add LED_FUNCTION_MOONLIGHT
changelogs between v8 & v9
- reuse api in flash and multicolor header
changelogs between v9 & v10
- add comment for reuse registration functions in flash and multicolor
changelogs between v10 & v11
- match dt-binding reg property comment to the functionality name
- remove exist patch in linux-next
- dicide multicolor channel by color definitiion
changelogs between v11 & v12
- Fix print size_t by %zu
- Fix dt-binding name regular experssion
changelogs between v12 & v13
- Fix kbuild test rebot build error
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Gene Chen <gene.chen.richtek@gmail.com>
To: jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org,
matthias.bgg@gmail.com
Cc: gene_chen@richtek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cy_huang@richtek.com,
benjamin.chao@mediatek.com, linux-mediatek@lists.infradead.org,
dmurphy@ti.com, linux-leds@vger.kernel.org,
Wilma.Wu@mediatek.com, linux-arm-kernel@lists.infradead.org,
shufan_lee@richtek.com
Subject: [PATCH resend v13 0/5] leds: mt6360: Add LED driver for MT6360
Date: Thu, 24 Dec 2020 09:47:15 +0800 [thread overview]
Message-ID: <1608774440-21655-1-git-send-email-gene.chen.richtek@gmail.com> (raw)
This patch series add MT6360 LED support contains driver and binding document
Gene Chen (5)
leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH
leds: flash: Fix multicolor no-ops registration by return 0
dt-bindings: leds: Add LED_COLOR_ID_MOONLIGHT definitions
dt-bindings: leds: Add bindings for MT6360 LED
leds: mt6360: Add LED driver for MT6360
Documentation/devicetree/bindings/leds/leds-mt6360.yaml | 159 +++
drivers/leds/Kconfig | 13
drivers/leds/Makefile | 1
drivers/leds/leds-mt6360.c | 827 ++++++++++++++++
include/dt-bindings/leds/common.h | 1
include/linux/led-class-flash.h | 42
include/linux/led-class-multicolor.h | 42
7 files changed, 1049 insertions(+), 36 deletions(-)
changelogs between v1 & v2
- add led driver with mfd
changelogs between v2 & v3
- independent add led driver
- add dt-binding document
- refactor macros definition for easy to debug
- parse device tree by fwnode
- use devm*ext to register led class device
changelogs between v3 & v4
- fix binding document description
- use GENMASK and add unit postfix to definition
- isink register led class device
changelogs between v4 & v5
- change rgb isink to multicolor control
- add binding reference to mfd yaml
changelogs between v5 & v6
- Use DT to decide RGB LED is multicolor device or indicator device only
changelogs between v6 & v7
- Add binding multicolor device sample code
- Add flash ops mutex lock
- Remove V4L2 init with indicator device
changelogs between v7 & v8
- Add mutex for led fault get ops
- Fix flash and multicolor no-ops return 0
- Add LED_FUNCTION_MOONLIGHT
changelogs between v8 & v9
- reuse api in flash and multicolor header
changelogs between v9 & v10
- add comment for reuse registration functions in flash and multicolor
changelogs between v10 & v11
- match dt-binding reg property comment to the functionality name
- remove exist patch in linux-next
- dicide multicolor channel by color definitiion
changelogs between v11 & v12
- Fix print size_t by %zu
- Fix dt-binding name regular experssion
changelogs between v12 & v13
- Fix kbuild test rebot build error
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-24 1:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 1:47 Gene Chen [this message]
2020-12-24 1:47 ` [PATCH resend v13 0/5] leds: mt6360: Add LED driver for MT6360 Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` [PATCH resend v13 1/5] leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` [PATCH resend v13 2/5] leds: flash: Fix multicolor no-ops registration by return 0 Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` [PATCH resend v13 3/5] dt-bindings: leds: Add LED_FUNCTION_MOONLIGHT definitions Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` [PATCH resend v13 4/5] dt-bindings: leds: Add bindings for MT6360 LED Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` [PATCH resend v13 5/5] leds: mt6360: Add LED driver for MT6360 Gene Chen
2020-12-24 1:47 ` Gene Chen
2020-12-24 1:47 ` Gene Chen
2021-01-10 19:03 ` Jacek Anaszewski
2021-01-10 19:03 ` Jacek Anaszewski
2021-01-10 19:03 ` 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=1608774440-21655-1-git-send-email-gene.chen.richtek@gmail.com \
--to=gene.chen.richtek@gmail.com \
--cc=Wilma.Wu@mediatek.com \
--cc=benjamin.chao@mediatek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=gene_chen@richtek.com \
--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=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=shufan_lee@richtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.