linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: Add some core definitions for MX53
Date: Wed, 27 Oct 2010 15:22:13 +0200	[thread overview]
Message-ID: <20101027132213.GJ6017@pengutronix.de> (raw)
In-Reply-To: <20101027102253.GA7822@angua.secretlab.ca>

On Wed, Oct 27, 2010 at 11:22:53AM +0100, Grant Likely wrote:
> On Wed, Oct 27, 2010 at 11:09:21AM +0200, Uwe Kleine-K?nig wrote:
> > Hello,
> > 
> > On Wed, Oct 27, 2010 at 09:29:59AM +0100, Grant Likely wrote:
> > > > ---
> > > >  arch/arm/plat-mxc/include/mach/iomux-mx53.h |  301 +++++++++++++++++++
> > > >  arch/arm/plat-mxc/include/mach/mx53.h       |  433 +++++++++++++++++++++++++++
> > > 
> > > Hi Dinh.
> > > 
> > > In general, these definitions should not be added until they are
> > > actually needed by driver code.
> > ack.
> > 
> > > Also, from my understanding, the mx53 is very similar to the mx51.
> > > If I'm correct, then they should be sharing the same set of #defines.
> > Note, I asked for a seperate header file.  See
> > http://thread.gmane.org/gmane.linux.kernel/1051001/focus=1051352
> 
> For the record, I disagree with that approach.  The approach I would
> take is for the imx53 code to use the imx51 defines by default, and to
> only define imx53 variants where there are differences.  Otherwise the
> code to support imx53 has to be completely divergent from imx51
> because the defines are different symbols.

That's a way we can go but only if the common name is not MX5 or MX5x.
We've done it with the mx21/27 and it failed when the mx25 came out
which was completely incompatible. Since then everybody looking at
the code must know that mx2x is mx21/27 but not mx25. I suggest
something like MX513 instead.

On the other hand I think there won't be much divergency. The way
devices are registered won't produce much overhead in sourcecode
and none in binary size.

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 |

  reply	other threads:[~2010-10-27 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 18:53 [PATCH] ARM: imx: Add some core definitions for MX53 Dinh.Nguyen at freescale.com
2010-10-26 19:10 ` Uwe Kleine-König
2010-10-26 22:37   ` Nguyen Dinh-R00091
2010-10-27  8:29 ` Grant Likely
2010-10-27  9:09   ` Uwe Kleine-König
2010-10-27 10:22     ` Grant Likely
2010-10-27 13:22       ` Sascha Hauer [this message]
2010-10-27 13:33         ` Eric Bénard
2010-10-27 13:56           ` Sascha Hauer
2010-10-27 14:57             ` Nguyen Dinh-R00091
2010-10-27 16:31               ` Sascha Hauer
2010-10-27 23:44         ` Robert Schwebel
2010-10-27 13:36     ` Rob Herring

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=20101027132213.GJ6017@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).