From: "Rafał Miłecki" <zajec5@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH V3 1/2] dt-bindings: leds: add Broadcom's BCM63138 controller
Date: Sun, 27 Mar 2022 11:28:43 +0200 [thread overview]
Message-ID: <223aabc8-7ec3-2719-866a-8f35ab97a11f@gmail.com> (raw)
In-Reply-To: <1ca1d83d-9803-77a3-e5bb-2380a2dc03b0@gmail.com>
Hi Pavel,
On 7.03.2022 07:27, Rafał Miłecki wrote:
> On 27.12.2021 15:59, 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>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
>
> Pavel: can I get this patchset finally accepted, please?
It has been 3 months now. I kindly pinged you in January, February and
March. Please let me know how can I get those patches accepted.
next prev parent reply other threads:[~2022-03-27 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 14:59 [PATCH V3 1/2] dt-bindings: leds: add Broadcom's BCM63138 controller Rafał Miłecki
2021-12-27 14:59 ` [PATCH V3 2/2] leds: bcm63138: add support for " Rafał Miłecki
2022-07-17 11:41 ` Pavel Machek
2022-03-07 6:27 ` [PATCH V3 1/2] dt-bindings: leds: add Broadcom's " Rafał Miłecki
2022-03-27 9:28 ` Rafał Miłecki [this message]
2022-04-27 20:47 ` Rafał Miłecki
2022-07-06 12:54 ` Rafał Miłecki
2022-07-17 11:37 ` Pavel Machek
2022-07-17 11:42 ` Pavel Machek
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=223aabc8-7ec3-2719-866a-8f35ab97a11f@gmail.com \
--to=zajec5@gmail.com \
--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=robh@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).