From: Linus Walleij <linus.walleij@linaro.org>
To: "Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v3 0/4] leds: bcm63138: Add some new bindings and code
Date: Fri, 04 Oct 2024 09:59:21 +0200 [thread overview]
Message-ID: <20241004-bcm63138-leds-v3-0-ba99a8e464b9@linaro.org> (raw)
This brings over the few know-how items and little things
I found about the BCMBCA LEDs in my previous duplicate driver.
This was tested on the BCM6846-based Genexis XG6846B.
The main addition is the ability to define the number shifting
bits in the serial shift register which is necessary if the
previous boot stages have not set up the hardware properly
before.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v3:
- Mention in the DT binding that hardware defaults will be used if the
property is missing.
- Link to v2: https://lore.kernel.org/r/20240928-bcm63138-leds-v2-0-f6aa4d4d6ef2@linaro.org
Changes in v2:
- Drop the u32 $ref in the schema, -bits is a standard suffix.
- Fix algorithm for shift register configuration.
- Fix spelling errors and numbering errors.
- Link to v1: https://lore.kernel.org/r/20240920-bcm63138-leds-v1-0-c150871324a0@linaro.org
---
Linus Walleij (4):
dt-bindings: leds: bcm63138: Add shift register bits
leds: bcm63138: Use scopes and guards
leds: bcm63138: Handle shift register config
leds: bcm63138: Add some register defines
.../devicetree/bindings/leds/leds-bcm63138.yaml | 11 +++++++++
drivers/leds/blink/leds-bcm63138.c | 28 ++++++++++++----------
2 files changed, 27 insertions(+), 12 deletions(-)
---
base-commit: 5724faee6be4109d7a3168625357e4127f42b5d2
change-id: 20240920-bcm63138-leds-1bc5f41c47cd
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2024-10-04 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 7:59 Linus Walleij [this message]
2024-10-04 7:59 ` [PATCH v3 1/4] dt-bindings: leds: bcm63138: Add shift register bits Linus Walleij
2024-10-04 16:15 ` Florian Fainelli
2024-10-05 18:08 ` Rob Herring (Arm)
2024-10-04 7:59 ` [PATCH v3 2/4] leds: bcm63138: Use scopes and guards Linus Walleij
2024-10-04 7:59 ` [PATCH v3 3/4] leds: bcm63138: Handle shift register config Linus Walleij
2024-10-04 16:15 ` Florian Fainelli
2024-10-04 7:59 ` [PATCH v3 4/4] leds: bcm63138: Add some register defines Linus Walleij
2024-10-04 16:24 ` Florian Fainelli
2024-10-10 13:41 ` Lee Jones
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=20241004-bcm63138-leds-v3-0-ba99a8e464b9@linaro.org \
--to=linus.walleij@linaro.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=william.zhang@broadcom.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;
as well as URLs for NNTP newsgroup(s).