[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191120144401.30452-1-TheSven73@gmail.com>
Date: Wed, 20 Nov 2019 09:43:58 -0500
From: Sven Van Asbroeck <thesven73@...il.com>
To: Lee Jones <lee.jones@...aro.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Grigoryev Denis <grigoryev@...twel.ru>,
Axel Lin <axel.lin@...ics.com>, Dan Murphy <dmurphy@...com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org
Subject: [PATCH v3 0/3] tps6105x add devicetree and leds support
v2 -> v3:
Removed tps6105x regulator patch - it was accepted (Mark Brown).
Removed devicetree/platdata bindings for tps6105x led naming.
I can test only with a 4.19 vendor kernel, which does not have the
latest led naming infrastructure (function/color). Drop devicetree/
fwnode/pdata led naming in favour of hard-coding to "tps6105x::torch",
so the patch can be tested by me, yet remains acceptable to upstream.
v1 -> v2:
Select chip operational mode by looking at subnode name, _not_ its
compatible property. Suggested by Mark Brown.
I needed led operation for this mfd chip, so I added a very simple
driver for this.
My platform (arm imx6q) is devicetree-based, so I added optional
devicetree support for this chip and its sub-drivers.
Sven Van Asbroeck (3):
tps6105x: add optional devicetree support
leds: tps6105x: add driver for mfd chip led mode
dt-bindings: mfd: update TI tps6105x chip bindings
.../devicetree/bindings/mfd/tps6105x.txt | 39 ++++++++++-
drivers/leds/Kconfig | 10 +++
drivers/leds/Makefile | 1 +
drivers/leds/leds-tps6105x.c | 67 +++++++++++++++++++
drivers/mfd/tps6105x.c | 34 +++++++++-
5 files changed, 147 insertions(+), 4 deletions(-)
create mode 100644 drivers/leds/leds-tps6105x.c
--
2.17.1
Powered by blists - more mailing lists