[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191119154611.29625-1-TheSven73@gmail.com>
Date: Tue, 19 Nov 2019 10:46:07 -0500
From: Sven Van Asbroeck <thesven73@...il.com>
To: Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.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 v2 0/4] tps6105x add devicetree and leds support
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.
Interestingly, the main mfd driver had a dt 'compatible' binding, but
could not operate without platform data?
Sven Van Asbroeck (4):
tps6105x: add optional devicetree support
regulator: 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 | 42 ++++++++-
drivers/leds/Kconfig | 10 +++
drivers/leds/Makefile | 1 +
drivers/leds/leds-tps6105x.c | 87 +++++++++++++++++++
drivers/mfd/tps6105x.c | 34 +++++++-
drivers/regulator/tps6105x-regulator.c | 2 +
include/linux/mfd/tps6105x.h | 1 +
7 files changed, 173 insertions(+), 4 deletions(-)
create mode 100644 drivers/leds/leds-tps6105x.c
--
2.17.1
Powered by blists - more mailing lists