From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/2] ARM: imx: Add core definitions for MX53
Date: Wed, 10 Nov 2010 17:46:40 +0100 [thread overview]
Message-ID: <20101110164640.GV6017@pengutronix.de> (raw)
In-Reply-To: <86A0E76937111F4C92FABEC0A20988510523D224@az33exm21>
On Wed, Nov 10, 2010 at 08:51:19AM -0700, Nguyen Dinh-R00091 wrote:
> Hi Sascha,
>
> >-----Original Message-----
> >From: Sascha Hauer [mailto:s.hauer at pengutronix.de]
> >Sent: Tuesday, November 09, 2010 3:46 PM
> >To: Nguyen Dinh-R00091
> >Cc: linux-kernel at vger.kernel.org; linux-arm-kernel at lists.infradead.org;
> linux at arm.linux.org.uk;
> >u.kleine-koenig at pengutronix.de; amit.kucheria at canonical.com;
> eric at eukrea.com
> >Subject: Re: [PATCHv3 1/2] ARM: imx: Add core definitions for MX53
> >
> >Hi Dinh,
> >
> >On Fri, Nov 05, 2010 at 10:55:50AM -0500, Dinh.Nguyen at freescale.com
> wrote:
> >> From: Dinh Nguyen <Dinh.Nguyen@freescale.com>
> >>
> >> Add iomux, clocks, and memory map for Freescale's MX53 SoC.
> >> Add cpu_is_mx53 function to common.h.
> >> Add 3 more banks of gpio's to mxc_gpio_ports.
> >> Add MX53 phys offset address.
> >>
> >> Signed-off-by: Dinh Nguyen <Dinh.Nguyen@freescale.com>
> >> ---
> >> arch/arm/mach-mx5/clock-mx53.c | 857
> +++++++++++++++++++++++++++
> >> arch/arm/mach-mx5/devices.c | 27 +
> >> arch/arm/plat-mxc/include/mach/common.h | 4 +
> >> arch/arm/plat-mxc/include/mach/iomux-mx53.h | 303 ++++++++++
> >> arch/arm/plat-mxc/include/mach/memory.h | 1 +
> >> arch/arm/plat-mxc/include/mach/mx53.h | 406 +++++++++++++
> >> 6 files changed, 1598 insertions(+), 0 deletions(-)
> >> create mode 100644 arch/arm/mach-mx5/clock-mx53.c
> >> create mode 100644 arch/arm/plat-mxc/include/mach/iomux-mx53.h
> >> create mode 100644 arch/arm/plat-mxc/include/mach/mx53.h
> >>
> >> diff --git a/arch/arm/mach-mx5/clock-mx53.c
> b/arch/arm/mach-mx5/clock-mx53.c
> >> new file mode 100644
> >> index 0000000..d547cb8
> >> --- /dev/null
> >> +++ b/arch/arm/mach-mx5/clock-mx53.c
> >
> >Most of this code looks like it could be shared with clock-mx51.c
>
> Agreed, but I was unsure how to proceed with adding clock code for mx53.
> Should I merge mx53 clock code into clock-mx51 and rename clock-mx51?
Yes, to something like clock-mx51-mx53.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 |
next prev parent reply other threads:[~2010-11-10 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 15:55 [PATCHv3 1/2] ARM: imx: Add core definitions for MX53 Dinh.Nguyen at freescale.com
2010-11-05 15:55 ` [PATCHv3 2/2] ARM: imx: Add mx53 support to common msl functions Dinh.Nguyen at freescale.com
2010-11-09 22:02 ` Sascha Hauer
2010-11-09 22:12 ` Uwe Kleine-König
2010-11-09 22:26 ` Sascha Hauer
2010-11-09 21:46 ` [PATCHv3 1/2] ARM: imx: Add core definitions for MX53 Sascha Hauer
2010-11-10 15:51 ` Nguyen Dinh-R00091
2010-11-10 16:46 ` Sascha Hauer [this message]
2010-11-10 17:04 ` Fabio Estevam
2010-11-10 17:09 ` Sascha Hauer
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=20101110164640.GV6017@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).