From: Dan Murphy <dmurphy@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v10 13/16] leds: lp5523: Update the lp5523 code to add intensity function
Date: Tue, 1 Oct 2019 09:56:17 -0500 [thread overview]
Message-ID: <20191001145620.11123-14-dmurphy@ti.com> (raw)
In-Reply-To: <20191001145620.11123-1-dmurphy@ti.com>
Add the intensity function call back to support the multicolor
framework. This function allows setting a specific brightness on
a specific channel.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
drivers/leds/leds-lp5523.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/leds/leds-lp5523.c b/drivers/leds/leds-lp5523.c
index d0b931a136b9..07484fc2f715 100644
--- a/drivers/leds/leds-lp5523.c
+++ b/drivers/leds/leds-lp5523.c
@@ -791,6 +791,19 @@ static ssize_t store_master_fader_leds(struct device *dev,
return ret;
}
+static int lp5523_led_intensity(struct lp55xx_led *led, int chan_num,
+ int brightness)
+{
+ struct lp55xx_chip *chip = led->chip;
+ int ret;
+
+ mutex_lock(&chip->lock);
+ ret = lp55xx_write(chip, LP5523_REG_LED_PWM_BASE + chan_num,
+ brightness);
+ mutex_unlock(&chip->lock);
+ return ret;
+}
+
static int lp5523_led_brightness(struct lp55xx_led *led)
{
struct lp55xx_chip *chip = led->chip;
@@ -857,6 +870,7 @@ static struct lp55xx_device_config lp5523_cfg = {
.max_channel = LP5523_MAX_LEDS,
.post_init_device = lp5523_post_init_device,
.brightness_fn = lp5523_led_brightness,
+ .color_intensity_fn = lp5523_led_intensity,
.set_led_current = lp5523_set_led_current,
.firmware_cb = lp5523_firmware_loaded,
.run_engine = lp5523_run_engine,
--
2.22.0.214.g8dca754b1e
next prev parent reply other threads:[~2019-10-01 14:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 14:56 [PATCH v10 00/16] Multicolor Framework Dan Murphy
2019-10-01 14:56 ` [PATCH v10 01/16] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2019-10-01 14:56 ` [PATCH v10 02/16] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy
2019-10-01 14:56 ` [PATCH v10 03/16] " Dan Murphy
2019-10-01 14:56 ` [PATCH v10 04/16] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2019-10-06 15:23 ` Jacek Anaszewski
2019-10-07 11:51 ` Dan Murphy
2019-10-01 14:56 ` [PATCH v10 05/16] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2019-10-01 14:56 ` [PATCH v10 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2019-10-02 0:16 ` kbuild test robot
2019-10-06 16:12 ` Jacek Anaszewski
2019-10-07 12:35 ` Dan Murphy
2019-10-01 14:56 ` [PATCH v10 07/16] dt: bindings: lp55xx: Be consistent in the document with LED acronym Dan Murphy
2019-10-01 14:56 ` [PATCH v10 08/16] dt: bindings: lp55xx: Update binding for Multicolor Framework Dan Murphy
2019-10-01 14:56 ` [PATCH v10 09/16] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2019-10-01 14:56 ` [PATCH v10 10/16] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2019-10-01 14:56 ` [PATCH v10 11/16] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes Dan Murphy
2019-10-04 21:50 ` Linus Walleij
2019-10-01 14:56 ` [PATCH v10 12/16] leds: lp55xx: Add multicolor framework support to lp55xx Dan Murphy
2019-10-02 0:31 ` kbuild test robot
2019-10-02 1:24 ` kbuild test robot
2019-10-06 19:52 ` Jacek Anaszewski
2019-10-07 17:08 ` Dan Murphy
2019-10-07 19:27 ` Jacek Anaszewski
2019-10-01 14:56 ` Dan Murphy [this message]
2019-10-01 14:56 ` [PATCH v10 14/16] leds: lp5521: Add multicolor framework intensity support Dan Murphy
2019-10-01 14:56 ` [PATCH v10 15/16] leds: lp55xx: Fix checkpatch file permissions issues Dan Murphy
2019-10-01 14:56 ` [PATCH v10 16/16] leds: lp5523: Fix checkpatch issues in the code Dan Murphy
2019-10-02 15:53 ` [PATCH v10 00/16] Multicolor Framework Dan Murphy
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=20191001145620.11123-14-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).