From: Lee Jones <lee@kernel.org>
To: linux-leds@vger.kernel.org, Eddie James <eajames@linux.ibm.com>
Cc: andy.shevchenko@gmail.com, lee@kernel.org, pavel@kernel.org
Subject: Re: [PATCH v8 0/4] leds: pca955x: Add HW blink support
Date: Thu, 20 Feb 2025 14:32:09 +0000 [thread overview]
Message-ID: <174006192944.772603.7002544080664872535.b4-ty@kernel.org> (raw)
In-Reply-To: <20250212143038.1416501-1-eajames@linux.ibm.com>
On Wed, 12 Feb 2025 08:30:34 -0600, Eddie James wrote:
> This series adds support for blinking using the PCA955x chip, falling
> back to software blinking if another LED on the chip is already blinking
> at a different rate, or if the requested rate isn't representable with
> the PCA955x.
> Also included are some minor clean up and optimization changes that make
> the HW blinking a bit easier.
>
> [...]
Applied, thanks!
[1/4] leds: pca955x: Refactor with helper functions and renaming
commit: ca3362a841b67a23d23c22ac16d18acec6cc75ec
[2/4] leds: pca955x: Use pointers to driver data rather than I2C client
commit: 1ddab1e2de10a37b66b235cff30e5b0a0beb8809
[3/4] leds: pca955x: Optimize probe led selection
commit: 14ef0738a31dcecfbba38626884b7d9a60b75cd0
[4/4] leds: pca955x: Add HW blink support
commit: 575f10dc64a251fc69a3187f4058f272eab94bfe
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-02-20 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 14:30 [PATCH v8 0/4] leds: pca955x: Add HW blink support Eddie James
2025-02-12 14:30 ` [PATCH v8 1/4] leds: pca955x: Refactor with helper functions and renaming Eddie James
2025-02-12 14:30 ` [PATCH v8 2/4] leds: pca955x: Use pointers to driver data rather than I2C client Eddie James
2025-02-12 14:30 ` [PATCH v8 3/4] leds: pca955x: Optimize probe led selection Eddie James
2025-02-12 14:30 ` [PATCH v8 4/4] leds: pca955x: Add HW blink support Eddie James
2025-02-20 14:32 ` Lee Jones [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=174006192944.772603.7002544080664872535.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@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