From: Brian Masney <masneyb@onstation.org>
To: lee.jones@linaro.org, daniel.thompson@linaro.org,
jingoohan1@gmail.com, robh+dt@kernel.org
Cc: jacek.anaszewski@gmail.com, pavel@ucw.cz, mark.rutland@arm.com,
b.zolnierkie@samsung.com, dri-devel@lists.freedesktop.org,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dmurphy@ti.com, jonathan@marek.ca
Subject: [PATCH v5 0/3] backlight: lm3630a: bug fix and fwnode support
Date: Thu, 18 Apr 2019 11:11:40 -0400 [thread overview]
Message-ID: <20190418151143.26068-1-masneyb@onstation.org> (raw)
Here is a patch series that fixes a single bug and adds fwnode support
to the lm3630a driver. This work was tested on a LG Nexus 5 (hammerhead)
phone. My status page at https://masneyb.github.io/nexus-5-upstream/
describes what is working so far with the upstream kernel.
See the individual patches for the changelog.
Brian Masney (3):
backlight: lm3630a: return 0 on success in update_status functions
dt-bindings: backlight: add lm3630a bindings
backlight: lm3630a: add firmware node support
.../leds/backlight/lm3630a-backlight.yaml | 129 +++++++++++++++
drivers/video/backlight/lm3630a_bl.c | 153 +++++++++++++++++-
include/linux/platform_data/lm3630a_bl.h | 4 +
3 files changed, 279 insertions(+), 7 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml
--
2.20.1
next reply other threads:[~2019-04-18 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 15:11 Brian Masney [this message]
2019-04-18 15:11 ` [PATCH v5 1/3] backlight: lm3630a: return 0 on success in update_status functions Brian Masney
2019-04-18 15:11 ` [PATCH v5 2/3] dt-bindings: backlight: add lm3630a bindings Brian Masney
2019-04-24 1:52 ` Rob Herring
2019-04-18 15:11 ` [PATCH v5 3/3] backlight: lm3630a: add firmware node support Brian Masney
2019-04-23 13:49 ` Dan Murphy
2019-04-23 14:01 ` Brian Masney
2019-04-23 15:31 ` Dan Murphy
2019-04-23 16:00 ` Brian Masney
2019-04-23 19:02 ` 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=20190418151143.26068-1-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=jonathan@marek.ca \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--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