From: Mike Looijmans <mike.looijmans@topic.nl>
To: linux-leds@vger.kernel.org
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, p.meerwald@bct-electronic.com
Subject: [PATCH 1/2] leds: pca963x: Add support for PCA962x chips
Date: Mon, 22 Aug 2022 08:18:37 +0200 [thread overview]
Message-ID: <20220822061838.8212-1-mike.looijmans@topic.nl> (raw)
The PCA962x family shares the same I2C register layout and functionality.
This adds support for the following chips:
PCA9623 4-channel
PCA9624 8-channel
PCA9622 16-channel
PCA9626 24-channel
Tested only the PCA9624. Other devices based on datasheet information.
Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
---
drivers/leds/Kconfig | 8 ++++----
drivers/leds/leds-pca963x.c | 36 ++++++++++++++++++++++++++++++++++++
2 files changed, 40 insertions(+), 4 deletions(-)
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 499d0f215a8b..9a99190c13af 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -497,13 +497,13 @@ config LEDS_PCA955X_GPIO
config LEDS_PCA963X
- tristate "LED support for PCA963x I2C chip"
+ tristate "LED support for PCA962x and PCA963x I2C chips"
depends on LEDS_CLASS
depends on I2C
help
- This option enables support for LEDs connected to the PCA963x
- LED driver chip accessed via the I2C bus. Supported
- devices include PCA9633 and PCA9634
+ This option enables support for LEDs connected to the PCA96xx
+ LED driver chip accessed via the I2C bus. Supported devices:
+ PCA9622, PCA9623, PCA9624, PCA9626, PCA9633, PCA9634, PCA9635.
config LEDS_WM831X_STATUS
tristate "LED support for status LEDs on WM831x PMICs"
diff --git a/drivers/leds/leds-pca963x.c b/drivers/leds/leds-pca963x.c
index 00aecd67e348..4d589624d192 100644
--- a/drivers/leds/leds-pca963x.c
+++ b/drivers/leds/leds-pca963x.c
@@ -48,6 +48,10 @@
#define PCA963X_PWM_BASE 0x02
enum pca963x_type {
+ pca9622,
+ pca9623,
+ pca9624,
+ pca9626,
pca9633,
pca9634,
pca9635,
@@ -62,6 +66,30 @@ struct pca963x_chipdef {
};
static struct pca963x_chipdef pca963x_chipdefs[] = {
+ [pca9622] = {
+ .grppwm = 0x12,
+ .grpfreq = 0x13,
+ .ledout_base = 0x14,
+ .n_leds = 16,
+ },
+ [pca9623] = {
+ .grppwm = 0x6,
+ .grpfreq = 0x7,
+ .ledout_base = 0x8,
+ .n_leds = 4,
+ },
+ [pca9624] = {
+ .grppwm = 0xa,
+ .grpfreq = 0xb,
+ .ledout_base = 0xc,
+ .n_leds = 8,
+ },
+ [pca9626] = {
+ .grppwm = 0x1a,
+ .grpfreq = 0x1b,
+ .ledout_base = 0x1d,
+ .n_leds = 24,
+ },
[pca9633] = {
.grppwm = 0x6,
.grpfreq = 0x7,
@@ -87,6 +115,10 @@ static struct pca963x_chipdef pca963x_chipdefs[] = {
#define PCA963X_BLINK_PERIOD_MAX 10667
static const struct i2c_device_id pca963x_id[] = {
+ { "pca9622", pca9622 },
+ { "pca9623", pca9623 },
+ { "pca9624", pca9624 },
+ { "pca9626", pca9626 },
{ "pca9632", pca9633 },
{ "pca9633", pca9633 },
{ "pca9634", pca9634 },
@@ -363,6 +395,10 @@ static int pca963x_register_leds(struct i2c_client *client,
}
static const struct of_device_id of_pca963x_match[] = {
+ { .compatible = "nxp,pca9622", },
+ { .compatible = "nxp,pca9623", },
+ { .compatible = "nxp,pca9624", },
+ { .compatible = "nxp,pca9626", },
{ .compatible = "nxp,pca9632", },
{ .compatible = "nxp,pca9633", },
{ .compatible = "nxp,pca9634", },
--
2.17.1
next reply other threads:[~2022-08-22 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 6:18 Mike Looijmans [this message]
2022-08-22 6:18 ` [PATCH 2/2] dt-bindings: leds: pca963x: Add support for PCA962x chips Mike Looijmans
2022-08-22 21:37 ` Rob Herring
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.eea759f5-b343-44ae-b225-1c6c559cf756.15e0f4b6-2201-4a5d-b92c-9ec71e7ae8fa@emailsignatures365.codetwo.com>
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.67ffd036-675b-48f2-93d0-58c455654605@emailsignatures365.codetwo.com>
2022-10-11 6:20 ` [PATCH 1/2] " Mike Looijmans
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=20220822061838.8212-1-mike.looijmans@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=p.meerwald@bct-electronic.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).