linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Huang Changming-R66093 <R66093@freescale.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	"linuxppc-dev@lists.ozlabs.org list"
	<linuxppc-dev@lists.ozlabs.org>,
	Anton Vorontsov <cbouatmailru@gmail.com>
Subject: Re: [PATCH 2/3] powerpc/esdhc: add property to disable the CMD23
Date: Tue, 18 Sep 2012 00:00:55 -0500	[thread overview]
Message-ID: <02298E64-619A-4F41-A329-5FA3C909B224@kernel.crashing.org> (raw)
In-Reply-To: <110EED8CC96DFC488B7E717A2027A27C17DBCA@039-SN1MPN1-002.039d.mgd.msft.net>


On Sep 17, 2012, at 8:09 PM, Huang Changming-R66093 wrote:

>> On Sep 17, 2012, at 7:36 AM, Chris Ball wrote:
>>=20
>>> Hi,
>>>=20
>>> On Thu, Sep 13 2012, Kumar Gala wrote:
>>>>>> Can you list out which SoCs support it and which don't.  Having
>>>>>> this list will be useful in understanding which controller =
versions
>> supported it.
>>>>>>=20
>>>>> P1020, p1021, p1022, p1024, p1015 and p4080 can't support it.
>>>>> Mpc8536, p2020, and the other current DPAA silicon (e.g. p5020, =
p3041)
>> support it.
>>>>=20
>>>> Based on this, why don't we use the HOSTVER register to detect =
instead
>> of device tree:
>>>=20
>>> I've got a mild preference for handling quirk assignment in the DT
>>> rather than in driver code, so I'd prefer to just push the original
>>> patch to mmc-next as-is.  Does that sound okay?
>>=20
>> Why?  I only ask because I agree with Scott that this means you have =
to
>> update your device tree to get proper functionality.
>>=20
> When the new silicon does not support CMD23,
> if we don't update the device tree, then we must update the SDHC =
driver.
> I prefer to add the property in device tree,
> because we just add this property in new device tree, we don't need =
more effort to modify driver.
>=20

Jerry,

I think doing it driver makes more sense because:

1. means older device tree's still work
2. odds that CMD23 not being supported in future devices is near 0%
   (Now that we support AutoCMD23 [and thus CMD23] we aren't likely to =
stop supporting it in future)
3. If IP changes you are going to have to update driver anyways for new =
features

I really think we should NOT utilize device tree for this.

- k

  reply	other threads:[~2012-09-18  5:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347347565-17474-1-git-send-email-Chang-Ming.Huang@freescale.com>
     [not found] ` <1347347565-17474-2-git-send-email-Chang-Ming.Huang@freescale.com>
     [not found]   ` <20120911075429.GA27028@lizard>
2012-09-11  8:04     ` [PATCH 2/3] powerpc/esdhc: add property to disable the CMD23 Anton Vorontsov
2012-09-11  9:36       ` Huang Changming-R66093
2012-09-11 12:43         ` Kumar Gala
2012-09-11 12:49           ` Kumar Gala
2012-09-11 14:44             ` Chris Ball
2012-09-11 20:26               ` Kumar Gala
2012-09-11 20:59                 ` Chris Ball
2012-09-12  6:18                   ` Huang Changming-R66093
2012-09-12 12:13                     ` Kumar Gala
2012-09-13  2:02                       ` Huang Changming-R66093
2012-09-13 12:47                         ` Kumar Gala
2012-09-14  2:02                           ` Huang Changming-R66093
2012-09-14 12:40                             ` Kumar Gala
2012-09-17 12:36                           ` Chris Ball
2012-09-17 13:12                             ` Kumar Gala
2012-09-17 13:45                               ` Chris Ball
2012-09-18  1:09                               ` Huang Changming-R66093
2012-09-18  5:00                                 ` Kumar Gala [this message]
2012-09-18  5:07                                   ` Chris Ball
2012-09-11 18:28       ` Scott Wood
2012-09-12  3:19         ` Huang Changming-R66093
2012-09-12  3:38           ` Anton Vorontsov
2012-09-13  7:57             ` 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=02298E64-619A-4F41-A329-5FA3C909B224@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=R66093@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).