From: Pierre-Hugues Husson <phh-8tEavu1zA38@public.gmane.org>
To: lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/2] mfd: add Ricoh RC5T619 PMIC support
Date: Sat, 5 Nov 2016 17:19:23 +0100 [thread overview]
Message-ID: <20161105161925.14910-1-phh@phh.me> (raw)
This patchset adds RC5T619 support. This PMIC is used on many
rockchip-based devices, for instance the GPD XD, or the Archos 101 Oxygen
---
Documentation/devicetree/bindings/mfd/rn5t618.txt | 16 +++--
drivers/mfd/Kconfig | 3 -
drivers/mfd/rn5t618.c | 1
drivers/regulator/Kconfig | 4 -
drivers/regulator/rn5t618-regulator.c | 35 ++++++++++--
include/linux/mfd/rn5t618.h | 15 +++++
6 files changed, 61 insertions(+), 13 deletions(-)
--
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
next reply other threads:[~2016-11-05 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 16:19 Pierre-Hugues Husson [this message]
[not found] ` <20161105161925.14910-1-phh-8tEavu1zA38@public.gmane.org>
2016-11-05 16:19 ` [PATCH 1/2] mfd: rn5t618: Add Ricoh RC5T619 PMIC support Pierre-Hugues Husson
[not found] ` <20161105161925.14910-2-phh-8tEavu1zA38@public.gmane.org>
2016-11-14 16:02 ` Rob Herring
2016-11-18 19:05 ` Lee Jones
2016-11-05 16:19 ` [PATCH 2/2] regulator: rn5t618: add " Pierre-Hugues Husson
[not found] ` <20161105161925.14910-3-phh-8tEavu1zA38@public.gmane.org>
2016-11-09 14:02 ` Mark Brown
2016-12-19 20:06 ` Pierre-Hugues Husson
2017-08-27 14:30 ` Applied "regulator: rn5t618: add RC5T619 PMIC support" to the regulator tree Mark Brown
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=20161105161925.14910-1-phh@phh.me \
--to=phh-8teavu1za38@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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).