From: Paul Bolle <pebolle@tiscali.nl>
To: Stanimir Varbanov <svarbanov@mm-sol.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Josh Cartwright <joshc@codeaurora.org>
Subject: Re: [PATCH] rtc: pm8xxx: rework to support pm8941 rtc
Date: Tue, 23 Sep 2014 10:50:45 +0200 [thread overview]
Message-ID: <1411462245.20236.17.camel@x220> (raw)
In-Reply-To: <1410515044-31689-1-git-send-email-svarbanov@mm-sol.com>
Hi Stanimar,
On Fri, 2014-09-12 at 12:44 +0300, Stanimir Varbanov wrote:
> Adds support for RTC device inside PM8941 PMIC. The RTC
> in this PMIC have two register spaces. Thus the rtc-pm8xxx
> is slightly reworked to reflect these differences.
>
> The register set for different PMIC chips are selected
> on DT compatible string base.
>
> Signed-off-by: Stanimir Varbanov <svarbanov@mm-sol.com>
This patch just landed in next-20140923 as commit 99abd227988a
("drivers/rtc/rtc-pm8xxx.c: rework to support pm8941 rtc").
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -1283,7 +1283,7 @@ config RTC_DRV_LPC32XX
>
> config RTC_DRV_PM8XXX
> tristate "Qualcomm PMIC8XXX RTC"
> - depends on MFD_PM8XXX
> + depends on MFD_PM8XXX || MFD_SPMI_PMIC
There's currently no Kconfig symbol MFD_SPMI_PMIC in linux-next. I guess
it's currently queued somewhere. Is that correct?
> help
> If you say yes here you get support for the
> Qualcomm PMIC8XXX RTC.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2014-09-23 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 9:44 [PATCH] rtc: pm8xxx: rework to support pm8941 rtc Stanimir Varbanov
2014-09-19 23:03 ` Andrew Morton
2014-09-23 9:02 ` Stanimir Varbanov
2014-09-23 8:50 ` Paul Bolle [this message]
2014-09-23 9:56 ` Stanimir Varbanov
2014-09-24 10:06 ` Lee Jones
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=1411462245.20236.17.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=joshc@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sboyd@codeaurora.org \
--cc=svarbanov@mm-sol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.