From: "Guido Günther" <agx@sigxcpu.org>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/6] leds: lm3692x: Allow to configure brigthness mode
Date: Wed, 25 Dec 2019 12:07:17 +0100 [thread overview]
Message-ID: <f6dabbf17ee2d839e53d305de819acd8fab72fad.1577271823.git.agx@sigxcpu.org> (raw)
In-Reply-To: <cover.1577271823.git.agx@sigxcpu.org>
Brightness mode is currently hardcoded as linear in the driver. Make
exponential mode configurable via DT.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
---
drivers/leds/leds-lm3692x.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/leds/leds-lm3692x.c b/drivers/leds/leds-lm3692x.c
index 28973cc5a6cc..ff20560a8263 100644
--- a/drivers/leds/leds-lm3692x.c
+++ b/drivers/leds/leds-lm3692x.c
@@ -115,7 +115,7 @@ struct lm3692x_led {
int led_enable;
int model_id;
- u8 boost_ctrl;
+ u8 boost_ctrl, brightness_ctrl;
};
static const struct reg_default lm3692x_reg_defs[] = {
@@ -267,8 +267,7 @@ static int lm3692x_init(struct lm3692x_led *led)
if (ret)
goto out;
- ret = regmap_write(led->regmap, LM3692X_BRT_CTRL,
- LM3692X_BL_ADJ_POL | LM3692X_RAMP_EN);
+ ret = regmap_write(led->regmap, LM3692X_BRT_CTRL, led->brightness_ctrl);
if (ret)
goto out;
@@ -326,6 +325,7 @@ static int lm3692x_probe_dt(struct lm3692x_led *led)
struct fwnode_handle *child = NULL;
struct led_init_data init_data = {};
u32 ovp;
+ bool exp_mode;
int ret;
led->enable_gpio = devm_gpiod_get_optional(&led->client->dev,
@@ -376,6 +376,12 @@ static int lm3692x_probe_dt(struct lm3692x_led *led)
}
}
+ led->brightness_ctrl = LM3692X_BL_ADJ_POL | LM3692X_RAMP_EN;
+ exp_mode = device_property_read_bool(&led->client->dev,
+ "ti,brightness-mapping-exponential");
+ if (exp_mode)
+ led->brightness_ctrl |= LM3692X_MAP_MODE_EXP;
+
child = device_get_next_child_node(&led->client->dev, child);
if (!child) {
dev_err(&led->client->dev, "No LED Child node\n");
--
2.23.0
next prev parent reply other threads:[~2019-12-25 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 11:07 [PATCH v2 0/6] leds: lm3692x: Allow to set ovp and brigthness mode Guido Günther
2019-12-25 11:07 ` [PATCH v2 1/6] dt: bindings: lm3692x: Add ti,ovp-microvolt property Guido Günther
2019-12-26 10:06 ` Pavel Machek
2019-12-27 12:17 ` Guido Günther
2019-12-25 11:07 ` [PATCH v2 2/6] leds: lm3692x: Allow to configure over voltage protection Guido Günther
2019-12-26 10:07 ` Pavel Machek
2019-12-25 11:07 ` [PATCH v2 3/6] dt: bindings: lm3692x: Add ti,brightness-mapping-exponential property Guido Günther
2019-12-25 11:07 ` Guido Günther [this message]
2019-12-25 11:07 ` [PATCH v2 5/6] dt: bindings: lm3692x: Add led-max-microamp property Guido Günther
2019-12-26 10:08 ` Pavel Machek
2019-12-25 11:07 ` [PATCH v2 6/6] leds: lm3692x: Make sure we don't exceed the maximum led current Guido Günther
2019-12-26 10:13 ` Pavel Machek
2019-12-27 12:59 ` Guido Günther
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=f6dabbf17ee2d839e53d305de819acd8fab72fad.1577271823.git.agx@sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).