From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: devicetree@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
"Rob Herring" <robh+dt@kernel.org>, "Pavel Machek" <pavel@ucw.cz>,
linux-leds@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>
Subject: Re: [PATCH V2 1/2] dt-bindings: leds: add Broadcom's BCM63138 controller
Date: Tue, 30 Nov 2021 16:40:42 -0600 [thread overview]
Message-ID: <Yaaoan2BnAh6ayak@robh.at.kernel.org> (raw)
In-Reply-To: <20211124111952.22419-1-zajec5@gmail.com>
On Wed, 24 Nov 2021 12:19:51 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Broadcom used 2 LEDs hardware blocks for their BCM63xx SoCs:
> 1. Older one (BCM6318, BCM6328, BCM6362, BCM63268, BCM6838)
> 2. Newer one (BCM6848, BCM6858, BCM63138, BCM63148, BCM63381, BCM68360)
>
> The newer one was also later also used on BCM4908 SoC.
>
> Old block is already documented in the leds-bcm6328.yaml. This binding
> documents the new one which uses different registers & programming. It's
> first used in BCM63138 thus the binding name.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Rename to bcm63138 & make "brcm,bcm63138-leds" the main compatible
> ---
> .../bindings/leds/leds-bcm63138.yaml | 95 +++++++++++++++++++
> 1 file changed, 95 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm63138.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-11-30 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 11:19 [PATCH V2 1/2] dt-bindings: leds: add Broadcom's BCM63138 controller Rafał Miłecki
2021-11-24 11:19 ` [PATCH V2 2/2] leds: bcm63xxx: add support for " Rafał Miłecki
2021-12-14 3:41 ` Florian Fainelli
2021-12-15 20:26 ` Pavel Machek
2021-12-15 20:36 ` Rafał Miłecki
2021-11-30 22:40 ` Rob Herring [this message]
2021-12-14 3:41 ` [PATCH V2 1/2] dt-bindings: leds: add Broadcom's " Florian Fainelli
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=Yaaoan2BnAh6ayak@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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).