public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: r66093@freescale.com
Cc: linux-mmc@vger.kernel.org,
	Jerry Huang <Chang-Ming.Huang@freescale.com>,
	Shaohui Xie <Shaohui.Xie@freescale.com>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	Kumar Gala <galak@kernel.crashing.org>
Subject: Re: [PATCH v3] powerpc/esdhc: disable CMD23 for some Freescale SoCs
Date: Fri, 21 Sep 2012 12:08:49 -0400	[thread overview]
Message-ID: <m3y5k3e4tq.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1348223135-6435-1-git-send-email-r66093@freescale.com> (r66093@freescale.com's message of "Fri, 21 Sep 2012 18:25:35 +0800")

Hi,

On Fri, Sep 21 2012, r66093@freescale.com wrote:
> --- a/drivers/mmc/host/sdhci-of-esdhc.c
> +++ b/drivers/mmc/host/sdhci-of-esdhc.c
> @@ -143,6 +143,35 @@ static void esdhc_of_resume(struct sdhci_host *host)
>  }
>  #endif
>  
> +static const u32 non_cmd23_processor_table[] = {
> +	/* P1020 Dual/Single core */
> +	0x80EC00, 0x80E400, 0x80ED00, 0x80E500,
> +	/* P1021 Dual/Single core */
> +	0x80EC01, 0x80E401, 0x80ED01, 0x80E501,
> +	/* P1022 Dual/Single core */
> +	0x80EE00, 0x80E600, 0x80EF00, 0x80E700,
> +	/* P1024 Dual/Single core */
> +	0x80EC02, 0x80E402, 0x80ED02, 0x80E502,
> +	/* P1025 Dual/Single core */
> +	0x80EC03, 0x80E403, 0x80ED03, 0x80E503,
> +	/* P4080 and P4040 */
> +	0x820000, 0x820800, 0x820100, 0x820900

I don't see how this method improves on either of the previous two we've
discussed.  If anything, Kumar's suggested method seems better than this
one:  it detected the MMC IP revision, which I'd expect to be more
reliable than building a list of which SoCs contain that IP.

Why is this better than using DT or detecting the MMC revision?

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  parent reply	other threads:[~2012-09-21 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 10:25 [PATCH v3] powerpc/esdhc: disable CMD23 for some Freescale SoCs r66093
2012-09-21 11:30 ` Girish K S
2012-09-21 16:08 ` Chris Ball [this message]
2012-09-21 18:36   ` Kumar Gala
2012-09-24  2:37     ` Huang Changming-R66093
2012-09-24  3:13       ` Huang Changming-R66093
2012-09-24 14:28         ` Kumar Gala
2012-09-25  2:05           ` Huang Changming-R66093
2012-09-24  2:30   ` Huang Changming-R66093

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=m3y5k3e4tq.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=Chang-Ming.Huang@freescale.com \
    --cc=Shaohui.Xie@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=galak@kernel.crashing.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=r66093@freescale.com \
    /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