Devicetree
 help / color / mirror / Atom feed
From: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Anton Vorontsov <avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
Cc: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	devicetree-discuss
	<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
	Phillips Kim-R1AAHA
	<Kim.Phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: esdhc binding compatiable
Date: Mon, 4 May 2009 08:54:28 -0500	[thread overview]
Message-ID: <54E4E37F-460A-4BB4-9DE1-670360D649A6@kernel.crashing.org> (raw)

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:

fsl,pq-eshdc	(covers 83xx, 85xx family)
fsl,qoirq-esdhc (covers any new p2xxx, p4xxx, etc..)

and if imx needs it

fsl,imx-esdhc

this would be the base compatible.  In addition to that we've  
discussed having a fsl,pq-eshdc-vX.Y compat to match the IP version in  
the specific SoC.

thoughts?

- k

             reply	other threads:[~2009-05-04 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 13:54 Kumar Gala [this message]
     [not found] ` <54E4E37F-460A-4BB4-9DE1-670360D649A6-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2009-05-04 21:11   ` esdhc binding compatiable 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
     [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=54E4E37F-460A-4BB4-9DE1-670360D649A6@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