From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jean-Jacques Hiblot <jjhiblot@traphandler.com>
Cc: Pavel Machek <pavel@ucw.cz>,
krzk+dt@kernel.org, Rob Herring <robh+dt@kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] Add support for the TLC5925
Date: Tue, 14 Jun 2022 16:53:13 +0200 [thread overview]
Message-ID: <CAHp75Vd29e55B7MFfg5A4RLkCzhKbE3FxcnESV2hNxYLA+OWGw@mail.gmail.com> (raw)
In-Reply-To: <20220614142704.155496-1-jjhiblot@traphandler.com>
On Tue, Jun 14, 2022 at 4:27 PM Jean-Jacques Hiblot
<jjhiblot@traphandler.com> wrote:
>
> This series add the support for the TLC5925 LED controller.
adds
> This LED controller is driven though SPI. There is little internal logic
through
> and it can be thought of as a deserializer + latches.
> The TLC5925 itself drives up to 16 LEDs, but multiple TLC5925s can be
> chained to drive more.
>
> The first patch describes the dt bindings.
> The second patch implements most of the driver and supports only
> synchronous brightness setting (brightness_set_blocking).
> The last patch implements the non-blocking version (brightness_set).
Much better, I have a few comments and I believe next version will be final.
> changes v3->v4:
> * add missing MODULE_DEVICE_TABLE(of, ...)
> * use dev_err_probe() to avoid spaming the log in case of deferred probe
spamming
> * use bitmap ops instead of direct mem access + lock
memory
> * sort headers and a few other cosmetic changes.
>
> changes v2->v3:
> * fixed the yaml description of the bindings (now passes dt_binding_check)
> * renamed shit-register-length into ti,shift-register-length and specify its
> type
>
> changes v1->v2:
> * renamed property shift_register_length into shift-register-length
> * add a SPI MODULE_DEVICE_TABLE structure
> * fixed the yaml description of the bindings (now passes dt_binding_check)
>
> Jean-Jacques Hiblot (3):
> dt-bindings: leds: Add bindings for the TLC5925 controller
> leds: Add driver for the TLC5925 LED controller
> leds: tlc5925: Add support for non blocking operations
>
> .../devicetree/bindings/leds/ti,tlc5925.yaml | 107 ++++++++++
> drivers/leds/Kconfig | 6 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-tlc5925.c | 191 ++++++++++++++++++
> 4 files changed, 305 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/ti,tlc5925.yaml
> create mode 100644 drivers/leds/leds-tlc5925.c
>
> --
> 2.25.1
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-06-14 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:27 [PATCH v4 0/3] Add support for the TLC5925 Jean-Jacques Hiblot
2022-06-14 14:27 ` [PATCH v4 1/3] dt-bindings: leds: Add bindings for the TLC5925 controller Jean-Jacques Hiblot
2022-06-14 14:27 ` [PATCH v4 2/3] leds: Add driver for the TLC5925 LED controller Jean-Jacques Hiblot
2022-06-14 14:49 ` Andy Shevchenko
2022-06-14 14:27 ` [PATCH v4 3/3] leds: tlc5925: Add support for non blocking operations Jean-Jacques Hiblot
2022-06-14 14:51 ` Andy Shevchenko
2022-06-14 14:53 ` Andy Shevchenko [this message]
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=CAHp75Vd29e55B7MFfg5A4RLkCzhKbE3FxcnESV2hNxYLA+OWGw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jjhiblot@traphandler.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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).