From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1] leds: Clarify supported chips by LM355x driver
Date: Fri, 26 Jan 2018 09:38:28 +0200 [thread overview]
Message-ID: <20180126073828.70597-1-andriy.shevchenko@linux.intel.com> (raw)
LM3555 is supported by AS3645A.
Clarify this in Kconfig by referencing to AS3645A.
No functional change.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/leds/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 3e763d2a0cb3..0961882fa57f 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -601,6 +601,8 @@ config LEDS_LM355x
This option enables support for LEDs connected to LM355x.
LM355x includes Torch, Flash and Indicator functions.
+ Note, LM3555 is driven by AS3645A.
+
config LEDS_OT200
tristate "LED support for the Bachmann OT200"
depends on LEDS_CLASS && HAS_IOMEM && (X86_32 || COMPILE_TEST)
--
2.15.1
next reply other threads:[~2018-01-26 7:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:38 Andy Shevchenko [this message]
2018-01-26 10:25 ` [PATCH v1] leds: Clarify supported chips by LM355x driver 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 ` [PATCH v2] " Pavel Machek
2018-02-01 21:33 ` 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=20180126073828.70597-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.