From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: [PATCH 0/5] MFD: fixup tc3589x for device tree
Date: Tue, 15 Oct 2013 23:10:48 +0200 [thread overview]
Message-ID: <1381871448-21492-1-git-send-email-linus.walleij@linaro.org> (raw)
This series of patches defines the device tree bindings for the
Toshiba TC3589x multi-purpose expander. This has been half-useable
with devicetree using the "device tree node named like the I2C
device ID" approach, but this adds proper bindings and put them
to use.
It is partly documenting how it is already working, but since
there never was a proper binding document I do not regard the
old bindings "deployed".
The patches are orthogonal so once these are cleared, patches
1-3 can be applied to the MFD tree, patch 4 to the input tree,
and I will pick patch 5 to the ux500 device tree branch.
Linus Walleij (5):
mfd: tc3589x: add device tree bindings
mfd: tc3589x: detect the precise version
mfd: tc3589x: reform device tree probing
input: tc3589x-keypad: support probing from device tree
ARM: ux500: adjust the TC3589x devices to the binding
Documentation/devicetree/bindings/mfd/tc3589x.txt | 61 ++++++++++
arch/arm/boot/dts/ste-href-tvk1281618.dtsi | 39 ++++++-
arch/arm/boot/dts/ste-hrefprev60.dtsi | 8 +-
drivers/input/keyboard/tc3589x-keypad.c | 63 ++++++++++-
drivers/mfd/tc3589x.c | 129 ++++++++++++++++++----
5 files changed, 264 insertions(+), 36 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/tc3589x.txt
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2013-10-15 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1381871448-21492-1-git-send-email-linus.walleij@linaro.org \
--to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).