public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <lee.jones@linaro.org>, <rdunlap@infradead.org>,
	<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v4 0/7] LMU Rework
Date: Mon, 6 May 2019 14:16:07 -0500	[thread overview]
Message-ID: <20190506191614.25051-1-dmurphy@ti.com> (raw)

Hello

With this series there was an offline discussion that the filename of the LED
portion of the driver did not adhere to the directory file naming convention so
the file name has been changed

ti-lmu-led-common.c->leds-ti-lmu-common.c
ti-lmu-led-common.h->leds-ti-lmu-common.h

Dan

Dan Murphy (7):
  dt-bindings: mfd: LMU: Fix lm3632 dt binding example
  dt-bindings: mfd: LMU: Add the ramp up/down property
  dt-bindings: mfd: LMU: Add ti,brightness-resolution
  leds: TI LMU: Add common code for TI LMU devices
  dt-bindings: ti-lmu: Modify dt bindings for the LM3697
  mfd: ti-lmu: Remove support for LM3697
  leds: lm3697: Introduce the lm3697 driver

 .../devicetree/bindings/leds/leds-lm3697.txt  |  73 ++++
 .../devicetree/bindings/mfd/ti-lmu.txt        |  58 ++-
 drivers/leds/Kconfig                          |  15 +
 drivers/leds/Makefile                         |   2 +
 drivers/leds/leds-lm3697.c                    | 395 ++++++++++++++++++
 drivers/leds/leds-ti-lmu-common.c             | 156 +++++++
 drivers/mfd/Kconfig                           |   2 +-
 drivers/mfd/ti-lmu.c                          |  17 -
 include/linux/leds-ti-lmu-common.h            |  47 +++
 include/linux/mfd/ti-lmu-register.h           |  44 --
 include/linux/mfd/ti-lmu.h                    |   1 -
 11 files changed, 714 insertions(+), 96 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3697.txt
 create mode 100644 drivers/leds/leds-lm3697.c
 create mode 100644 drivers/leds/leds-ti-lmu-common.c
 create mode 100644 include/linux/leds-ti-lmu-common.h

-- 
2.21.0.5.gaeb582a983


             reply	other threads:[~2019-05-06 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 19:16 Dan Murphy [this message]
2019-05-06 19:16 ` [PATCH v4 1/7] dt-bindings: mfd: LMU: Fix lm3632 dt binding example Dan Murphy
2019-05-08 11:35   ` Lee Jones
2019-05-06 19:16 ` [PATCH v4 2/7] dt-bindings: mfd: LMU: Add the ramp up/down property Dan Murphy
2019-05-08 11:35   ` Lee Jones
2019-05-06 19:16 ` [PATCH v4 3/7] dt-bindings: mfd: LMU: Add ti,brightness-resolution Dan Murphy
2019-05-08 11:36   ` Lee Jones
2019-05-06 19:16 ` [PATCH v4 4/7] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-05-06 19:16 ` [PATCH v4 5/7] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-05-08 11:36   ` Lee Jones
2019-05-06 19:16 ` [PATCH v4 6/7] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-05-06 19:16 ` [PATCH v4 7/7] leds: lm3697: Introduce the lm3697 driver 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=20190506191614.25051-1-dmurphy@ti.com \
    --to=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rdunlap@infradead.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