devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: linux-leds@vger.kernel.org
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	p.meerwald@bct-electronic.com
Subject: [PATCH 2/2] dt-bindings: leds: pca963x: Add support for PCA962x chips
Date: Mon, 22 Aug 2022 08:18:38 +0200	[thread overview]
Message-ID: <20220822061838.8212-2-mike.looijmans@topic.nl> (raw)
In-Reply-To: <20220822061838.8212-1-mike.looijmans@topic.nl>

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>

---

 Documentation/devicetree/bindings/leds/leds-pca9532.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/leds/leds-pca9532.txt b/Documentation/devicetree/bindings/leds/leds-pca9532.txt
index f769c52e3643..50a340cbbb49 100644
--- a/Documentation/devicetree/bindings/leds/leds-pca9532.txt
+++ b/Documentation/devicetree/bindings/leds/leds-pca9532.txt
@@ -5,6 +5,10 @@ The PWM support 256 steps.
 
 Required properties:
 	- compatible:
+		"nxp,pca9522"
+		"nxp,pca9523"
+		"nxp,pca9524"
+		"nxp,pca9526"
 		"nxp,pca9530"
 		"nxp,pca9531"
 		"nxp,pca9532"
-- 
2.17.1


       reply	other threads:[~2022-08-22  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220822061838.8212-1-mike.looijmans@topic.nl>
2022-08-22  6:18 ` Mike Looijmans [this message]
2022-08-22 21:37   ` [PATCH 2/2] dt-bindings: leds: pca963x: Add support for PCA962x chips Rob Herring

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-2-mike.looijmans@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=p.meerwald@bct-electronic.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).