From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>
Subject: [PATCH v2] leds: Clarify supported chips by LM355x driver
Date: Thu, 1 Feb 2018 21:26:34 +0100 [thread overview]
Message-ID: <20180201202634.GA29617@amd> (raw)
In-Reply-To: <15971fbb-2c6d-5c15-d5d7-1718af904ebb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
Reported-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Clarify which controllers are supported by which driver.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 318a28f..9a538de 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -69,7 +69,7 @@ config LEDS_APU
module will be called leds-apu.
config LEDS_AS3645A
- tristate "AS3645A LED flash controller support"
+ tristate "AS3645A and LM3555 LED flash controllers support"
depends on I2C && LEDS_CLASS_FLASH
depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
help
@@ -587,12 +587,12 @@ config LEDS_MAX8997
MAXIM MAX8997 PMIC.
config LEDS_LM355x
- tristate "LED support for LM355x Chips, LM3554 and LM3556"
+ tristate "LED support for LM3554 and LM3556 chips"
depends on LEDS_CLASS && I2C
select REGMAP_I2C
help
- This option enables support for LEDs connected to LM355x.
- LM355x includes Torch, Flash and Indicator functions.
+ This option enables support for LEDs connected to LM3554
+ and LM3556. It includes Torch, Flash and Indicator functions.
config LEDS_OT200
tristate "LED support for the Bachmann OT200"
--
(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:[~2018-02-01 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:38 [PATCH v1] leds: Clarify supported chips by LM355x driver Andy Shevchenko
2018-01-26 10:25 ` Pavel Machek
2018-01-26 11:44 ` Andy Shevchenko
2018-01-26 21:05 ` Pavel Machek
2018-01-26 21:32 ` Pavel Machek
2018-01-26 22:07 ` Sakari Ailus
2018-01-28 14:18 ` Andy Shevchenko
2018-01-26 20:39 ` Jacek Anaszewski
2018-01-28 14:30 ` Andy Shevchenko
2018-01-29 20:46 ` Jacek Anaszewski
2018-01-30 11:08 ` Andy Shevchenko
2018-01-30 20:04 ` Jacek Anaszewski
2018-02-01 20:26 ` Pavel Machek [this message]
2018-02-01 21:33 ` [PATCH v2] " Jacek Anaszewski
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=20180201202634.GA29617@amd \
--to=pavel@ucw.cz \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
/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