From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
sameo@linux.intel.com, lee.jones@linaro.org,
a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
Subject: [PATCH 0/4] Add Device tree support for 88PM800 mfd and rtc driver
Date: Sat, 30 May 2015 03:49:18 +0530 [thread overview]
Message-ID: <1432937962-4537-1-git-send-email-vaibhav.hiremath@linaro.org> (raw)
This patch-series adds support for Device tree to 88PM800 mfd and rtc driver.
It also creates the DT binding for 88pm800 driver.
Testing::
- Boot tested on PXA1928 based platform.
- probe of mfd, rtc and regulator function passing.
Attempt has been made to push some of the patches to the list sometime
back in 2013.
Link to previous patch submission:
https://lkml.org/lkml/2013/8/14/86
Vaibhav Hiremath (4):
mfd: 88pm800: add device tree support
mfd: 88pm800: use irq_mode to configure interrupt status reg clear
method
rtc: 88pm80x: add device tree support
mfd: 88pm800: allocate pdata->rtc if not allocated earlier
Documentation/devicetree/bindings/mfd/88pm800.txt | 57 +++++++++++++++++++++
drivers/mfd/88pm800.c | 62 ++++++++++++++++++++++-
drivers/rtc/rtc-88pm80x.c | 28 ++++++----
include/linux/mfd/88pm80x.h | 2 +
4 files changed, 137 insertions(+), 12 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/88pm800.txt
--
1.9.1
next reply other threads:[~2015-05-29 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 22:19 Vaibhav Hiremath [this message]
2015-05-29 22:19 ` [PATCH 2/4] mfd: 88pm800: use irq_mode to configure interrupt status reg clear method Vaibhav Hiremath
2015-06-01 8:31 ` Lee Jones
2015-06-02 8:51 ` Vaibhav Hiremath
2015-05-29 22:19 ` [PATCH 3/4] rtc: 88pm80x: add device tree support Vaibhav Hiremath
[not found] ` <1432937962-4537-1-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-05-29 22:19 ` [PATCH 1/4] mfd: 88pm800: " Vaibhav Hiremath
[not found] ` <1432937962-4537-2-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-01 8:38 ` Lee Jones
2015-06-16 7:52 ` Vaibhav Hiremath
[not found] ` <557FD5AD.5020405-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-16 13:02 ` Rob Herring
[not found] ` <CAL_Jsq+6yk59Z4swi2xq4=_=m89pBUt-fNXJF8smjw7qS8xazA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-16 14:36 ` Vaibhav Hiremath
2015-05-29 22:19 ` [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier Vaibhav Hiremath
2015-06-01 8:22 ` Lee Jones
2015-06-02 5:07 ` Vaibhav Hiremath
[not found] ` <556D3A14.6050505-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-02 7:40 ` Lee Jones
2015-06-02 9:05 ` Vaibhav Hiremath
[not found] ` <556D71F6.4030608-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-02 9:33 ` Lee Jones
2015-06-02 9:49 ` Vaibhav Hiremath
2015-06-02 10:07 ` Lee Jones
2015-06-02 10:18 ` Vaibhav Hiremath
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=1432937962-4537-1-git-send-email-vaibhav.hiremath@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
/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).