From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: sean.wang@mediatek.com
Cc: pavel@ucw.cz, matthias.bgg@gmail.com, linux-leds@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 0/3] leds-mt6323: Make driver flexible and cleanups
Date: Wed, 22 Jun 2022 15:53:07 +0200 [thread overview]
Message-ID: <b587116e-712e-07a5-cc83-457de768835b@collabora.com> (raw)
In-Reply-To: <20220516094222.30414-1-angelogioacchino.delregno@collabora.com>
Il 16/05/22 11:42, AngeloGioacchino Del Regno ha scritto:
> MT6323 is not the only PMIC that has a LEDs controller IP and it was
> found that the others do have a compatible register layout, except
> for some register offsets.
> The logic contained in this driver can be totally reused for other
> PMICs as well, so I can't see any reason to keep this specific to
> the MT6323 part.
>
> This series brings meaningful platform data to this driver, giving
> it flexibility and making it possible and straightforward to add
> support for other (older, or newer!) PMICs.
>
> AngeloGioacchino Del Regno (3):
> leds: leds-mt6323: Specify registers and specs in platform data
> leds: leds-mt6323: Open code and drop MT6323_CAL_HW_DUTY macro
> leds: leds-mt6323: Drop MT6323_ prefix from macros and defines
>
> drivers/leds/leds-mt6323.c | 258 ++++++++++++++++++++++++-------------
> 1 file changed, 166 insertions(+), 92 deletions(-)
>
Gentle ping on this series...
Thanks,
Angelo
prev parent reply other threads:[~2022-06-22 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 9:42 AngeloGioacchino Del Regno
2022-05-16 9:42 ` [PATCH 1/3] leds: leds-mt6323: Specify registers and specs in platform data AngeloGioacchino Del Regno
2022-05-16 9:42 ` [PATCH 2/3] leds: leds-mt6323: Open code and drop MT6323_CAL_HW_DUTY macro AngeloGioacchino Del Regno
2022-05-16 9:42 ` [PATCH 3/3] leds: leds-mt6323: Drop MT6323_ prefix from macros and defines AngeloGioacchino Del Regno
2022-06-22 13:53 ` AngeloGioacchino Del Regno [this message]
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=b587116e-712e-07a5-cc83-457de768835b@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.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=sean.wang@mediatek.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
all inboxes | Powered by JetHome®