From: Pavel Machek <pavel@ucw.cz>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Dan Murphy <dmurphy@ti.com>,
linux-leds@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>,
newbytee@protonmail.com, Stephan Gerhold <stephan@gerhold.net>,
linux-media@vger.kernel.org, phone-devel@vger.kernel.org,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH 2/2 v9] leds: rt8515: Add Richtek RT8515 LED driver
Date: Wed, 27 Jan 2021 23:16:29 +0100 [thread overview]
Message-ID: <20210127221628.GC24799@amd> (raw)
In-Reply-To: <20210102231510.2068851-2-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Hi!
> This adds a driver for the Richtek RT8515 dual channel
> torch/flash white LED driver.
>
> This LED driver is found in some mobile phones from
> Samsung such as the GT-S7710 and GT-I8190.
>
> A V4L interface is added.
>
> We do not have a proper datasheet for the RT8515 but
> it turns out that RT9387A has a public datasheet and
> is essentially the same chip. We designed the driver
> in accordance with this datasheet. The day someone
> needs to drive a RT9387A this driver can probably
> easily be augmented to handle that chip too.
>
> Sakari Ailus, Pavel Machek and Andy Shevchenko helped
> significantly in getting this driver right.
Thanks, applied... And sorry for the delay.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2021-01-27 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 23:15 [PATCH 1/2 v9] dt-bindings: leds: Add DT binding for Richtek RT8515 Linus Walleij
2021-01-02 23:15 ` [PATCH 2/2 v9] leds: rt8515: Add Richtek RT8515 LED driver Linus Walleij
2021-01-22 21:40 ` Linus Walleij
2021-01-27 22:16 ` Pavel Machek [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=20210127221628.GC24799@amd \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=newbytee@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=stephan@gerhold.net \
/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).