All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Shawn Lin <shawn.lin@rock-chips.com>, Mason <slash.tmp@free.fr>,
	linux-mmc <linux-mmc@vger.kernel.org>
Cc: Michal Simek <monstr@monstr.eu>,
	Anton Vorontsov <anton@enomsg.org>,
	Xiaobo Xie <x.xie@freescale.com>,
	Suman Tripathi <stripathi@apm.com>,
	Michal Simek <michal.simek@xilinx.com>,
	soren.brinkmann@xilinx.com
Subject: Re: arasan,sdhci.txt "compatibility" DT binding
Date: Wed, 3 Feb 2016 08:20:36 +0100	[thread overview]
Message-ID: <56B1AA44.1010108@xilinx.com> (raw)
In-Reply-To: <56B166F1.5080605@rock-chips.com>

Hi,

On 3.2.2016 03:33, Shawn Lin wrote:
> + Michal, Sören Brinkmann
> 
> On 2016/2/2 17:49, Mason wrote:
>> Hello everyone,
>>
>> Documentation/devicetree/bindings/mmc/arasan,sdhci.txt states:
>>
>> Required Properties:
>>    - compatible: Compatibility string. Must be 'arasan,sdhci-8.9a' or
>>                  'arasan,sdhci-4.9a' or 'arasan,sdhci-5.1'
>>
>> What do 8.9a, 4.9a, and 5.1 refer to?
>>
> 
> Good question.
> 
> Michal told me that 8.9a and 4.9a came from Xilinx
> databook which define their available arasan controller to be version
> 4.9a and 8.9a.

Our version is coming from here.
http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf
page 28

Datasheets from 2012 and 2010 doesn't look too recent and I expect that
Arasan did a lot of work from that time that's why I am not surprised
that you are not able to see that versions.

Thanks,
Michal


  reply	other threads:[~2016-02-03  7:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  9:49 arasan,sdhci.txt "compatibility" DT binding Mason
2016-02-03  2:33 ` Shawn Lin
2016-02-03  7:20   ` Michal Simek [this message]
2016-02-03  8:31     ` Mason
2016-02-03  9:58       ` Michal Simek
2016-02-03 15:21         ` Sören Brinkmann
2016-02-03 15:33           ` Mason
2016-11-18 10:37             ` Mason
2016-11-18 10:37               ` Mason
2016-11-18 10:49               ` Rameshwar Sahu
2016-11-18 10:49                 ` Rameshwar Sahu
2016-11-18 12:42                 ` Mason
2016-11-18 12:42                   ` Mason
2016-11-18 13:22                   ` Michal Simek
2016-11-18 13:22                     ` Michal Simek
2016-11-28 15:44                     ` Mason
2016-11-28 15:44                       ` Mason
2016-11-28 16:15                       ` Arnd Bergmann
2016-11-28 16:15                         ` Arnd Bergmann
2016-11-28 16:52                         ` Mason
2016-11-28 16:52                           ` Mason
2016-11-29  7:29                           ` Rameshwar Sahu
2016-11-29  7:29                             ` Rameshwar Sahu
2016-11-30 10:51                             ` Sebastian Frias
2016-11-30 10:51                               ` Sebastian Frias
2016-11-30 13:17                               ` Michal Simek
2016-11-30 13:17                                 ` Michal Simek
2016-11-28 16:23                       ` Sebastian Frias
2016-11-28 16:23                         ` Sebastian Frias
2016-12-01  4:09                       ` Shawn Lin
2016-12-01  4:09                         ` Shawn Lin
2016-12-01 12:29                         ` Mason
2016-12-01 12:29                           ` Mason

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=56B1AA44.1010108@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=anton@enomsg.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=shawn.lin@rock-chips.com \
    --cc=slash.tmp@free.fr \
    --cc=soren.brinkmann@xilinx.com \
    --cc=stripathi@apm.com \
    --cc=x.xie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.