From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-leds@vger.kernel.org
Cc: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
jacek.anaszewski@gmail.com, mika.westerberg@intel.com,
rafael@kernel.org
Subject: [PATCH 0/2] ACPI LED and LED flash support, ACPI support for AS3645A LED flash controller
Date: Fri, 15 Sep 2017 17:40:50 +0300 [thread overview]
Message-ID: <20170915144052.25903-1-sakari.ailus@linux.intel.com> (raw)
Hello everyone,
This small patchset defines how to use LEDs and refer to LEDs on ACPI as
well as make use of this with the AS3645A driver.
These patches depend on the AS3645A set here:
<URL:http://www.spinics.net/lists/linux-media/msg121423.html>
as well as the V4L2 fwnode / async improvement patchset here:
<URL:https://www.mail-archive.com/linux-media@vger.kernel.org/msg119015.html>
The two patches in this set used to be part of the above set (v9):
<URL:https://www.mail-archive.com/linux-media@vger.kernel.org/msg118522.html>
Comments would be welcome.
Regards,
Sakari
Sakari Ailus (2):
ACPI: Document how to refer to LEDs from remote nodes
as3645a: Switch to fwnode property API
Documentation/acpi/dsd/leds.txt | 94 +++++++++++++++++++++++++++++++++++++++++
drivers/leds/leds-as3645a.c | 81 ++++++++++++++++++++---------------
2 files changed, 140 insertions(+), 35 deletions(-)
create mode 100644 Documentation/acpi/dsd/leds.txt
--
2.11.0
next reply other threads:[~2017-09-15 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 14:40 Sakari Ailus [this message]
2017-09-15 14:40 ` [PATCH 1/2] ACPI: Document how to refer to LEDs from remote nodes Sakari Ailus
2017-09-17 16:57 ` Jacek Anaszewski
2017-09-18 10:34 ` Sakari Ailus
2017-09-18 18:14 ` Jacek Anaszewski
2017-09-15 14:40 ` [PATCH 2/2] as3645a: Switch to fwnode property API Sakari Ailus
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=20170915144052.25903-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=rafael@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