From: Phil Reid <preid@electromag.com.au>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
riku.voipio@iki.fi, rpurdie@rpsys.net, j.anaszewski@samsung.com,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org
Cc: Phil Reid <preid@electromag.com.au>
Subject: [Patch v5 0/1] leds: pca9532: Add device tree binding
Date: Tue, 14 Jun 2016 09:56:08 +0800 [thread overview]
Message-ID: <1465869369-13449-1-git-send-email-preid@electromag.com.au> (raw)
This patch adds very basic device tree binding support to the
pca9532 driver. Sufficent to load driver and enable LEDs.
Changes for v5:
- Address warning on 64bit builds. Change devid cast to unitptr_t.
- Make pca9532_of_populate_pdata static.
Changes for v4:
- Reference leds/common.txt in documentation.
- Check return value of of_match_device()
Changes for v3:
- Remove state from device tree binding.
This needs more thought on how to configure which PWM is used.
And is not essential for a first pass.
Changes for v2:
- Fixup device tree documentation
- Use label propert and fall back to node name,
- Call of_node_put when breaking loop iterating leds.
- Increment the loop counter.
- Add initial state and default-trigger.
Phil Reid (1):
leds: pca9532: Add device tree binding
.../devicetree/bindings/leds/leds-pca9532.txt | 39 +++++++++++
drivers/leds/leds-pca9532.c | 76 ++++++++++++++++++++--
include/dt-bindings/leds/leds-pca9532.h | 18 +++++
include/linux/leds-pca9532.h | 9 ++-
4 files changed, 133 insertions(+), 9 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/leds-pca9532.txt
create mode 100644 include/dt-bindings/leds/leds-pca9532.h
--
1.8.3.1
next reply other threads:[~2016-06-14 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 1:56 Phil Reid [this message]
[not found] ` <1465869369-13449-1-git-send-email-preid-qgqNFa1JUf/o2iN0hyhwsIdd74u8MsAO@public.gmane.org>
2016-06-14 1:56 ` [Patch v5 1/1] leds: pca9532: Add device tree binding Phil Reid
2016-06-14 7:30 ` Jacek Anaszewski
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=1465869369-13449-1-git-send-email-preid@electromag.com.au \
--to=preid@electromag.com.au \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=riku.voipio@iki.fi \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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).