From: cy_huang <u0084500@gmail.com>
To: pavel@ucw.cz, matthias.bgg@gmail.com
Cc: cy_huang@richtek.com, jacek.anaszewski@gmail.com,
gene_chen@richtek.com, linux-leds@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] leds: flash: mt6360: Apply the fixes and hardware features
Date: Thu, 28 Apr 2022 17:32:41 +0800 [thread overview]
Message-ID: <1651138365-17362-1-git-send-email-u0084500@gmail.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
This patch series includes some fixes and add supproted ISNK hardware features.
From MT6360, ISNK can support three modes (CC, PWM, and Breath). The previous
one can only support CC mode.
ChiYuan Huang (4):
leds: flash: mt6360: Fix the wrong enable_reg in multicolor brightness
set
leds: flash: mt6360: Remove unused dependency in Kconfig
leds: flash: mt6360: Add mt6360 isnk channel hardware timer dimming
mode support
leds: flash: mt6360: Add mt6360 isnk channel hardwre breath mode
support
drivers/leds/flash/Kconfig | 4 +-
drivers/leds/flash/leds-mt6360.c | 413 ++++++++++++++++++++++++++++++++++++++-
2 files changed, 410 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2022-04-28 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 9:32 cy_huang [this message]
2022-04-28 9:32 ` [PATCH 1/4] leds: flash: mt6360: Fix the wrong enable_reg in multicolor brightness set cy_huang
2022-04-28 9:32 ` [PATCH 2/4] leds: flash: mt6360: Remove unused dependency in Kconfig cy_huang
2022-04-28 9:32 ` [PATCH 3/4] leds: flash: mt6360: Add mt6360 isnk channel hardware timer dimming mode support cy_huang
2022-04-28 9:32 ` [PATCH 4/4] leds: flash: mt6360: Add mt6360 isnk channel hardwre breath " cy_huang
2022-04-28 11:50 ` Matti Vaittinen
2022-04-28 14:57 ` ChiYuan Huang
2022-06-14 7:36 ` [PATCH 0/4] leds: flash: mt6360: Apply the fixes and hardware features ChiYuan Huang
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=1651138365-17362-1-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=cy_huang@richtek.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 \
/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).