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 18:09:12 +0100 [thread overview]
Message-ID: <20101110170912.GC8950@pengutronix.de> (raw)
In-Reply-To: <AANLkTinmXin65ReWsUf02ia7FMvHfeqkVeaGu6Usmdw5@mail.gmail.com>
On Wed, Nov 10, 2010 at 03:04:27PM -0200, Fabio Estevam wrote:
> On Wed, Nov 10, 2010 at 2:46 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> ...
>
> >> 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
> >
>
> Or maybe clock-mx5x.c would be more generic.
>
> This way when any other MX5x processor gets added we don't need to
> change the file name again.
This can happen with mx5x also when the next MX5x is incompatible like
we had with i.MX2x when i.MX25 came out. Anyway, in this case I don't
care much.
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-11-10 17:09 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
2010-11-10 17:04 ` Fabio Estevam
2010-11-10 17:09 ` 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=20101110170912.GC8950@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).