From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] imx3: Add rtc platform device support
Date: Fri, 26 Mar 2010 08:54:52 +0100 [thread overview]
Message-ID: <20100326075452.GD2241@pengutronix.de> (raw)
In-Reply-To: <87d3yshbuo.fsf@vovsem.com>
On Thu, Mar 25, 2010 at 02:36:31PM +0300, Vladimir Zapolskiy wrote:
> Hi Sasha,
>
> >
> > On Wed, Mar 24, 2010 at 02:32:17PM +0300, Vladimir Zapolskiy wrote:
> >> This patch adds support for build-in RTC device found on
> >> Freescale imx31 and imx35 SoCs.
> >>
> >> Signed-off-by: Vladimir Zapolskiy <vzapolskiy@gmail.com>
> >> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> >> ---
> >> arch/arm/mach-mx3/devices.c | 19 +++++++++++++++++++
> >> arch/arm/mach-mx3/devices.h | 1 +
> >> 2 files changed, 20 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/arch/arm/mach-mx3/devices.c b/arch/arm/mach-mx3/devices.c
> >> index f891115..1ffed28 100644
> >> --- a/arch/arm/mach-mx3/devices.c
> >> +++ b/arch/arm/mach-mx3/devices.c
> >> @@ -588,6 +588,25 @@ struct platform_device imx_wdt_device0 = {
> >> .resource = imx_wdt_resources,
> >
> > This patch does not apply. We do not have the watchdog in devices.c atm.
> >
>
> please could you suggest the appropriate branch, because this patch is
> based on mxc-master branch, where the watchdog is already pushed, see
> http://git.pengutronix.de/?p=imx/linux-2.6.git;a=shortlog;h=refs/heads/mxc-master
Oh, my bad. I myself tried to push it on master and not on mxc-master.
>
> >> };
> >>
> >> +static struct resource imx_rtc_resources[] = {
> >> + {
> >> + .start = MX31_RTC_BASE_ADDR,
> >> + .end = MX31_RTC_BASE_ADDR + 0x3fff,
> >> + .flags = IORESOURCE_MEM,
> >> + },
> >> + {
> >> + .start = MX31_INT_RTC,
> >> + .flags = IORESOURCE_IRQ,
> >> + },
> >
> > Can you provide a fixup for i.MX35, please? See mx3_devices_init().
>
> Surely. Before patch submission I just checked that base address, size
> and interrupt number are equal for i.MX31 and i.MX35 SoCs, and I've
> found that in such cases the resources are defined using MX31 macros,
> see imx_ssi_resources or mxc_usbhX_resources as reference.
Ok. I just saw that there are two defines without checking that they are
actually identical.
>
> Probably better to separate the devices.c file into two files? You see
> one day I hope i.MX37 support will be included into the Linux kernel,
> and it would be quite uncomfortable to support three kinds of peripheral
> in a single file.
We are already working on seperating them. Have a look at the i.MX21/27
devices.c.
Sascha
--
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 |
prev parent reply other threads:[~2010-03-26 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 11:32 [PATCH 1/3] imx31: fix parent clock for rtc Vladimir Zapolskiy
2010-03-24 11:32 ` [PATCH 2/3] imx3: Add rtc platform device support Vladimir Zapolskiy
2010-03-24 11:32 ` [PATCH 3/3] imx31: add rtc device on litekit board Vladimir Zapolskiy
2010-03-25 7:35 ` [PATCH 2/3] imx3: Add rtc platform device support Sascha Hauer
2010-03-25 11:36 ` Vladimir Zapolskiy
2010-03-26 7:54 ` Sascha Hauer [this message]
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=20100326075452.GD2241@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).