linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] imx-esdhc: update devices registration
Date: Tue, 12 Oct 2010 17:31:56 +0200	[thread overview]
Message-ID: <20101012153155.GE4470@pengutronix.de> (raw)
In-Reply-To: <4CB47BCF.3060709@eukrea.com>

On Tue, Oct 12, 2010 at 05:16:31PM +0200, Eric B?nard wrote:
> Hi Uwe,
> 
> Le 12/10/2010 17:08, Uwe Kleine-K?nig a ?crit :
> >>+#define MX25_MMC_SDHC1_BASE_ADDR	0x53fb4000
> >>+#define MX25_MMC_SDHC2_BASE_ADDR	0x53fb8000
> >I wonder about the name in the reference manual.  Is it really MMC_SDHC
> >for all socs?  I always wonder what it the best here (if they are named
> >inconsitently there), have it equal over all SoCs or have it match the
> >respective reference manual?!
> >
> reference manual, section Memory Map :
> i.MX25 : eSDHC-x
> i.MX35 : eSDHCv2-x
> i.MX51 : ESDHC x
> 
> so the manual are not consistent ... "MMC_SDHC" seems easy to
> understand but of course we can have ESDHC, or SDHC or something
> else if you have a better name to suggest.

I'd go for ESDHC, that seems to be the common part in all refmans. (And
comparing it to the SDHC-spec, it is also not really a straightforward
SDHC anyway ;))

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101012/d2fe3d70/attachment.sig>

  reply	other threads:[~2010-10-12 15:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 12:23 [PATCH 1/3] imx-esdhc: update devices registration Eric Bénard
2010-10-12 12:23 ` [PATCH 2/3] mx25: fix compile error in platform-imx-dma.c Eric Bénard
2010-10-12 12:35   ` Uwe Kleine-König
2010-10-12 12:23 ` [PATCH 3/3] iomux-mx51: fix GPIO_1_xx 's IOMUX configuration Eric Bénard
2010-10-12 12:31 ` [PATCH v2 1/3] imx-esdhc: update devices registration Eric Bénard
2010-10-12 12:33 ` [PATCH " Uwe Kleine-König
2010-10-12 12:57   ` Eric Bénard
2010-10-12 13:04     ` Uwe Kleine-König
2010-10-12 14:58       ` [PATCH v3] " Eric Bénard
2010-10-12 15:08         ` Uwe Kleine-König
2010-10-12 15:16           ` Eric Bénard
2010-10-12 15:31             ` Wolfram Sang [this message]
2010-10-12 17:33               ` [PATCH v4] " Eric Bénard
2010-10-15  9:01                 ` Uwe Kleine-König
2010-10-15  9:16                   ` Eric Bénard
2010-10-20 14:55                 ` Uwe Kleine-König
2010-10-20 15:05                   ` Eric Bénard
2010-10-20 15:44                     ` Uwe Kleine-König
2010-10-21 19:47                       ` Eric Bénard
2010-10-22  7:20                         ` [PATCH v2] ARM: mx3: fix build failure concerning MXC_INT_MMC_SDHC2 Uwe Kleine-König
2010-10-22  9:56                           ` Fabio Estevam

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=20101012153155.GE4470@pengutronix.de \
    --to=w.sang@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).