From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: enable support for mx35 rtc
Date: Wed, 4 Jul 2012 08:55:01 +0200 [thread overview]
Message-ID: <20120704065501.GF2698@pengutronix.de> (raw)
In-Reply-To: <1161104963.340229.1340983241008.JavaMail.root@advansee.com>
Hi Beno?t,
On Fri, Jun 29, 2012 at 05:20:41PM +0200, Beno?t Th?baudeau wrote:
> The i.MX35 has an RTC compatible with the i.MX31's, so enable its support even
> if it's not very useful because it's not battery backed.
Given that you do not add board for this rtc and we all want to convert
to devicetree I would rather drop this patch.
Sascha
>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: <linux-arm-kernel@lists.infradead.org>
> Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> ---
> .../arch/arm/mach-imx/devices-imx35.h | 4 ++++
> .../arch/arm/plat-mxc/devices/platform-mxc_rtc.c | 5 +++++
> 2 files changed, 9 insertions(+)
>
> diff --git linux-next-HEAD-d1d2d3a.orig/arch/arm/mach-imx/devices-imx35.h linux-next-HEAD-d1d2d3a/arch/arm/mach-imx/devices-imx35.h
> index 7b99ef0..82d6ea0 100644
> --- linux-next-HEAD-d1d2d3a.orig/arch/arm/mach-imx/devices-imx35.h
> +++ linux-next-HEAD-d1d2d3a/arch/arm/mach-imx/devices-imx35.h
> @@ -68,6 +68,10 @@ extern const struct imx_mxc_nand_data imx35_mxc_nand_data;
> #define imx35_add_mxc_nand(pdata) \
> imx_add_mxc_nand(&imx35_mxc_nand_data, pdata)
>
> +extern const struct imx_mxc_rtc_data imx35_mxc_rtc_data;
> +#define imx35_add_mxc_rtc(pdata) \
> + imx_add_mxc_rtc(&imx35_mxc_rtc_data)
> +
> extern const struct imx_mxc_w1_data imx35_mxc_w1_data;
> #define imx35_add_mxc_w1(pdata) \
> imx_add_mxc_w1(&imx35_mxc_w1_data)
> diff --git linux-next-HEAD-d1d2d3a.orig/arch/arm/plat-mxc/devices/platform-mxc_rtc.c linux-next-HEAD-d1d2d3a/arch/arm/plat-mxc/devices/platform-mxc_rtc.c
> index 16d0ec4..a5c9ad5 100644
> --- linux-next-HEAD-d1d2d3a.orig/arch/arm/plat-mxc/devices/platform-mxc_rtc.c
> +++ linux-next-HEAD-d1d2d3a/arch/arm/plat-mxc/devices/platform-mxc_rtc.c
> @@ -20,6 +20,11 @@ const struct imx_mxc_rtc_data imx31_mxc_rtc_data __initconst =
> imx_mxc_rtc_data_entry_single(MX31);
> #endif /* ifdef CONFIG_SOC_IMX31 */
>
> +#ifdef CONFIG_SOC_IMX35
> +const struct imx_mxc_rtc_data imx35_mxc_rtc_data __initconst =
> + imx_mxc_rtc_data_entry_single(MX35);
> +#endif /* ifdef CONFIG_SOC_IMX35 */
> +
> struct platform_device *__init imx_add_mxc_rtc(
> const struct imx_mxc_rtc_data *data)
> {
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-07-04 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1061486785.340218.1340983236720.JavaMail.root@advansee.com>
2012-06-29 15:20 ` [PATCH] ARM: imx: enable support for mx35 rtc Benoît Thébaudeau
2012-07-04 6:55 ` Sascha Hauer [this message]
2012-07-04 14:35 ` [PATCH 1 of 3] ARM: imx: remove unused pdata from device macros Benoît Thébaudeau
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=20120704065501.GF2698@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).