From: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Anton Vorontsov
<avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>,
Phillips Kim-R1AAHA
<Kim.Phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
devicetree-discuss
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: Re: esdhc binding compatiable
Date: Tue, 5 May 2009 06:29:38 -0500 [thread overview]
Message-ID: <12EB7A56-CD13-4F7F-9E36-CDD6D579AC3A@kernel.crashing.org> (raw)
In-Reply-To: <20090504211110.GC28413-VKaLA/mbEU932VTgPCOETVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
On May 4, 2009, at 4:11 PM, Scott Wood wrote:
> On Mon, May 04, 2009 at 08:54:28AM -0500, Kumar Gala wrote:
>> There has been some discussion on various lists about what the
>> binding
>> doc says w/regards to compat binding for eSHDC on 83xx, 85xx, pxxxx.
>>
>> My thinking is that we wanted to avoid "fsl,eshdc" as possibly being
>> to generic (some theory that esdhc might be same or similar
>> controller
>> on iMX devices from FSL). If that's the case I'm thinking something
>> like:
>
> If it's the *same* controller, then it should have the same compatible
> (and the same driver).
Define the *same*. I believe things might be 90/95% the same but
there is probably some 5/10% SoC unique integration changes between an
eSDHC on a PPC vs ARM SoC from FSL. For example in the imx version
they have a few registers called ADMA Error Status & ADMA Address
which we don't have on PQ devices.
- k
next prev parent reply other threads:[~2009-05-05 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 13:54 esdhc binding compatiable Kumar Gala
[not found] ` <54E4E37F-460A-4BB4-9DE1-670360D649A6-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2009-05-04 21:11 ` Scott Wood
[not found] ` <20090504211110.GC28413-VKaLA/mbEU932VTgPCOETVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-05-05 0:34 ` Kim Phillips
[not found] ` <20090504193416.7ec102bd.kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-05-05 1:07 ` Scott Wood
[not found] ` <49FF914B.1080909-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-05-05 11:10 ` Kumar Gala
2009-05-05 11:29 ` Kumar Gala [this message]
[not found] ` <12EB7A56-CD13-4F7F-9E36-CDD6D579AC3A-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2009-05-05 17:01 ` Mitch Bradley
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=12EB7A56-CD13-4F7F-9E36-CDD6D579AC3A@kernel.crashing.org \
--to=galak-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
--cc=Kim.Phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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