On Sep 17, 2012, at 7:36 AM, Chris Ball wrote:
Hi,
=20
On Thu, Sep 13 2012, Kumar Gala wrote:
quoted
quoted
quoted
Can you list out which SoCs support it and which don't. Having =
this list
quoted
quoted
quoted
will be useful in understanding which controller versions supported =
it.
quoted
quoted
quoted
=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.
quoted
=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?
Why? I only ask because I agree with Scott that this means you have to =
update your device tree to get proper functionality.
(I think the argument that there isn't going to be any new hardware
with this problem is equally in favor of both methods.)
- k=