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 0/6] leds: lm3692x: Allow to set ovp and brigthness mode
Date: Wed, 25 Dec 2019 12:07:13 +0100 [thread overview]
Message-ID: <cover.1577271823.git.agx@sigxcpu.org> (raw)
Overvoltage protection and brightness mode are currently hardcoded
as 29V and disabled in the driver. Make these configurable via DT.
Besides addressing review comments v2 also allows to limit the maximum led
current.
Changes from v1
- As per review comments by Dan Murphy
https://lore.kernel.org/linux-leds/3d66b07d-b4c5-43e6-4378-d63cc84b8d43@ti.com/
- Split commits per propoerty
- Add new properties to DT example too
- Drop dev_dbg() statements
- ovp: fix 21V value parsing
- ovp: Set correct default value if DT parsing fails
- As per review comments by Pavel Machek
https://lore.kernel.org/linux-leds/20191221191515.GF32732@amd/
- Fix defaults (which is 29V)
- Use uV as Unit for ovp property
- Change property name to 'ti,ovp-microvolt' to make it shorter
- Honor led-max-microamp to not exceed the maximum led current
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
Guido Günther (6):
dt: bindings: lm3692x: Add ti,ovp-microvolt property
leds: lm3692x: Allow to configure over voltage protection
dt: bindings: lm3692x: Add ti,brightness-mapping-exponential property
leds: lm3692x: Allow to configure brigthness mode
dt: bindings: lm3692x: Add led-max-microamp property
leds: lm3692x: Make sure we don't exceed the maximum led current
.../devicetree/bindings/leds/leds-lm3692x.txt | 11 +++
drivers/leds/leds-lm3692x.c | 67 +++++++++++++++++--
2 files changed, 72 insertions(+), 6 deletions(-)
--
2.23.0
next 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 Guido Günther [this message]
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 ` [PATCH v2 4/6] leds: lm3692x: Allow to configure brigthness mode Guido Günther
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=cover.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).