linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Chen <gene.chen.richtek@gmail.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Dan Murphy <dmurphy@ti.com>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support" 
	<linux-mediatek@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Gene Chen <gene_chen@richtek.com>,
	Wilma.Wu@mediatek.com, shufan_lee@richtek.com,
	ChiYuan Huang <cy_huang@richtek.com>,
	benjamin.chao@mediatek.com
Subject: Re: [PATCH v14 0/2] leds: mt6360: Add LED driver for MT6360
Date: Mon, 12 Jul 2021 16:33:19 +0800	[thread overview]
Message-ID: <CAE+NS37kf1JAJ2Zt7UGsfsubp6O=xBNtnJgVEnz8-mm2rxFa+g@mail.gmail.com> (raw)
In-Reply-To: <20210524152427.123856-1-gene.chen.richtek@gmail.com>

Gene Chen <gene.chen.richtek@gmail.com> 於 2021年5月24日 週一 下午11:24寫道:
>
> This patch series add MT6360 LED support contains driver and binding document
>
> Gene Chen (2)
>  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/flash/Kconfig                              |   13
>  drivers/leds/flash/Makefile                             |    1
>  drivers/leds/flash/leds-mt6360.c                        |  910 ++++++++++++++++
>  4 files changed, 1083 insertions(+)
>
> 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
>
> changelogs between v13 & v14
>  - Move driver to flash folder
>  - Remove LED FUNCTION MOONLIGHT
>  - Keep 80 char per line
>
>

Dear Reviewers,

Please let me know if any update.

  parent reply	other threads:[~2021-07-12  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 15:24 [PATCH v14 0/2] leds: mt6360: Add LED driver for MT6360 Gene Chen
2021-05-24 15:24 ` [PATCH v14 1/2] dt-bindings: leds: Add bindings for MT6360 LED Gene Chen
2021-05-24 15:24 ` [PATCH v14 2/2] leds: mt6360: Add LED driver for MT6360 Gene Chen
2021-07-12  8:33 ` Gene Chen [this message]
2021-07-12 20:24   ` [PATCH v14 0/2] " Jacek Anaszewski
2021-07-16  6:27     ` Gene Chen

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='CAE+NS37kf1JAJ2Zt7UGsfsubp6O=xBNtnJgVEnz8-mm2rxFa+g@mail.gmail.com' \
    --to=gene.chen.richtek@gmail.com \
    --cc=Wilma.Wu@mediatek.com \
    --cc=benjamin.chao@mediatek.com \
    --cc=cy_huang@richtek.com \
    --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=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 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).