From: Lee Jones <lee.jones@linaro.org>
To: Eddie Huang <eddie.huang@mediatek.com>
Cc: "Alessandro Zummo" <a.zummo@towertech.it>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Tomasz Figa" <tfiga@google.com>,
"Uwe Kleine-König" <kernel@pengutronix.de>,
srv_heupstream@mediatek.com,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Joe Perches" <joe@perches.com>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 1/3] mfd: provide RTC resource in MT6397 MFD
Date: Tue, 28 Apr 2015 11:07:19 +0100 [thread overview]
Message-ID: <20150428100719.GN11956@x1> (raw)
In-Reply-To: <1430206556-18254-2-git-send-email-eddie.huang@mediatek.com>
On Tue, 28 Apr 2015, Eddie Huang wrote:
> Provide MT6397 RTC interrupt, base address, and register in
> MT6397 MFD.
>
> Signed-off-by: Eddie Huang <eddie.huang@mediatek.com>
> ---
> drivers/mfd/mt6397-core.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
*after* Uwe's concerns have been attended to, you may add my:
Acked-by: Lee Jones <lee.jones@linaro.org>
FWIW, I quite like straight lines. :)
> diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
> index 09bc780..08cfbd1 100644
> --- a/drivers/mfd/mt6397-core.c
> +++ b/drivers/mfd/mt6397-core.c
> @@ -21,9 +21,27 @@
> #include <linux/mfd/mt6397/core.h>
> #include <linux/mfd/mt6397/registers.h>
>
> +#define MT6397_RTC_BASE 0xe000
> +#define MT6397_RTC_SIZE 0x3e
> +
> +static const struct resource mt6397_rtc_resources[] = {
> + {
> + .start = MT6397_RTC_BASE,
> + .end = MT6397_RTC_BASE + MT6397_RTC_SIZE,
> + .flags = IORESOURCE_MEM,
> + },
> + {
> + .start = MT6397_IRQ_RTC,
> + .end = MT6397_IRQ_RTC,
> + .flags = IORESOURCE_IRQ,
> + },
> +};
> +
> static const struct mfd_cell mt6397_devs[] = {
> {
> .name = "mt6397-rtc",
> + .num_resources = ARRAY_SIZE(mt6397_rtc_resources),
> + .resources = mt6397_rtc_resources,
> .of_compatible = "mediatek,mt6397-rtc",
> }, {
> .name = "mt6397-regulator",
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-04-28 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:35 [PATCH v3 0/3] Add Mediatek SoC RTC driver Eddie Huang
2015-04-28 7:35 ` [PATCH v3 1/3] mfd: provide RTC resource in MT6397 MFD Eddie Huang
2015-04-28 7:45 ` Uwe Kleine-König
2015-04-28 10:07 ` Lee Jones [this message]
2015-04-28 7:35 ` [PATCH v3 2/3] rtc: mediatek: Add MT6397 RTC driver Eddie Huang
2015-05-05 20:00 ` [rtc-linux] " Alexandre Belloni
2015-05-05 20:44 ` Joe Perches
2015-05-05 21:01 ` Alexandre Belloni
2015-05-06 3:32 ` Eddie Huang
2015-04-28 7:35 ` [PATCH v3 3/3] MAINTAINERS: add Mediatek " Eddie Huang
2015-05-05 20:03 ` [rtc-linux] " Alexandre Belloni
2015-05-06 3:36 ` Eddie Huang
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=20150428100719.GN11956@x1 \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=eddie.huang@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.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).