From: Pavel Machek <pavel@ucw.cz>
To: Martin Botka <martin.botka1@gmail.com>
Cc: "Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"Dan Murphy" <dmurphy@ti.com>, "Rob Herring" <robh+dt@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee.jones@linaro.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH RFC 0/6] Add QCOM pwm-lpg and tri-led drivers
Date: Sat, 25 Jul 2020 00:05:16 +0200 [thread overview]
Message-ID: <20200724220516.GA21965@amd> (raw)
In-Reply-To: <20200724213659.273599-1-martin.botka1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
Hi!
Dalsi cech co hackuje LEDky?
> This series brings QCOM pwm-lpg and tri-led drivers from 4.14 that is required to support pmic-connected notification LED.
> This comes straight from downstream and I'm ready for your comments.
Yeah, so...
Bindings should go first, they may need to be converted to yml
(devicetree people will know).
Can generic pwm driver be used here?
This is for RGB modules, right? It will need to use multicolor
framework.
"Breathing" will need to be figured out. It should become a trigger.
Is this for phone, btw? If so, which one?
Best regards,
Pavel
> .../bindings/leds/leds-qti-tri-led.txt | 72 +
> .../devicetree/bindings/pwm/pwm-qti-lpg.txt | 163 +++
> drivers/leds/Kconfig | 9 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-qti-tri-led.c | 640 ++++++++
> drivers/pwm/Kconfig | 10 +
> drivers/pwm/Makefile | 1 +
> drivers/pwm/core.c | 56 +-
> drivers/pwm/pwm-qti-lpg.c | 1284 +++++++++++++++++
> drivers/pwm/sysfs.c | 56 +-
> include/linux/pwm.h | 144 +-
> 11 files changed, 2418 insertions(+), 18 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-qti-tri-led.txt
> create mode 100644 Documentation/devicetree/bindings/pwm/pwm-qti-lpg.txt
> create mode 100644 drivers/leds/leds-qti-tri-led.c
> create mode 100644 drivers/pwm/pwm-qti-lpg.c
>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-07-24 22:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 21:36 [PATCH RFC 0/6] Add QCOM pwm-lpg and tri-led drivers Martin Botka
2020-07-24 21:36 ` [PATCH RCC 1/6] pwm: Add different PWM output types support Martin Botka
2020-07-27 20:10 ` Uwe Kleine-König
2020-07-27 20:56 ` Martin Botka
2020-07-28 7:52 ` Uwe Kleine-König
2020-07-27 21:46 ` Guru Das Srinagesh
2020-07-24 21:36 ` [PATCH RFC 2/6] pwm: core: Add option to config PWM duty/period with u64 data length Martin Botka
2020-07-25 14:55 ` Martin Botka
2020-07-25 15:24 ` Pavel Machek
2020-07-25 15:30 ` Martin Botka
2020-07-26 9:04 ` Andy Shevchenko
2020-07-26 9:12 ` Martin Botka
2020-07-27 7:29 ` Martin Botka
2020-07-27 7:32 ` Martin Botka
2020-07-27 7:52 ` Uwe Kleine-König
2020-07-27 7:58 ` Martin Botka
2020-07-27 8:34 ` Uwe Kleine-König
2020-07-24 21:36 ` [PATCH RFC 3/6] pwm: pwm-qti-lpg: Add PWM driver for QTI LPG module Martin Botka
2020-07-27 20:09 ` Uwe Kleine-König
2020-07-27 21:16 ` Martin Botka
2020-07-28 7:08 ` Uwe Kleine-König
2020-07-24 21:36 ` [PATCH RFC 4/6] leds: leds-qti-tri-led: Add LED driver for QTI TRI_LED module Martin Botka
2020-07-26 17:25 ` Martin Botka
2020-07-24 21:36 ` [PATCH RFC 5/6] Documentation: Add binding for qti-tri-led Martin Botka
2020-07-24 21:36 ` [PATCH RFC 6/6] Documentation: Add binding for pwm-qti-lpg Martin Botka
2020-07-24 22:05 ` Pavel Machek [this message]
2020-07-24 22:26 ` [PATCH RFC 0/6] Add QCOM pwm-lpg and tri-led drivers Martin Botka
2020-07-24 22:32 ` Pavel Machek
2020-07-24 22:48 ` Martin Botka
[not found] ` <CADQ2G_HbysJbiQKSRmA6HDRfjPYPiDjbZfeuUjM1mNV-BBBC-A@mail.gmail.com>
2020-07-24 22:31 ` Pavel Machek
2020-07-24 22:46 ` Martin Botka
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=20200724220516.GA21965@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.botka1@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).