From: Mason <slash.tmp@free.fr>
To: Rameshwar Sahu <rsahu@apm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Soren Brinkmann <soren.brinkmann@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Michal Simek <monstr@monstr.eu>,
Anton Vorontsov <anton@enomsg.org>,
Xiaobo Xie <x.xie@freescale.com>,
Suman Tripathi <stripathi@apm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Zach Brown <zach.brown@ni.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
Jisheng Zhang <jszhang@marvell.com>, Suneel Garapati <sunee>
Subject: Re: arasan,sdhci.txt "compatibility" DT binding
Date: Fri, 18 Nov 2016 13:42:44 +0100 [thread overview]
Message-ID: <582EF744.8090307@free.fr> (raw)
In-Reply-To: <CAFd313x6MJeO90_+rxditdPn762g7TqZc0_D6ojGTKmtGJKjPA@mail.gmail.com>
On 18/11/2016 11:49, Rameshwar Sahu wrote:
> Mason wrote:
>
>> Suman/APM added "arasan,sdhci-4.9a" in 308f3f8d8112
>> @Suman, @Rameshwar: what specific IP block does your SoC embed?
>> What does 4.9a refer to? The documentation revision number?
>
> We have Arasan SD3.0/ SDIO3.0/ eMMC4.41 AHB Host Controller IP
> embedded in our SoC and 4.9a is documentation revision number which
> was given by Arasan.
> FYI this documentation date was May, 2012.
Hello Ram,
Thanks for the information.
Xilinx is using "SD2.0/SDIO2.0/MMC3.31 AHB Host Controller"
APM is using "SD3.0/SDIO3.0/eMMC4.41 AHB Host Controller"
Sigma is using "SD3.0/SDIO3.0/eMMC4.4 AHB Host Controller"
Rockchip is using ? (Shawn could you specify exactly which IP you use?)
And it looks like Arasan is using different revision numbers for
every documentation they have.
The "SD3.0/SDIO3.0/eMMC4.4 AHB Host Controller" doc I have is
at rev number 6.0, dated 2010-02-19.
Regards.
next prev parent reply other threads:[~2016-11-18 12:43 UTC|newest]
Thread overview: 20+ 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
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:49 ` Rameshwar Sahu
2016-11-18 12:42 ` Mason [this message]
2016-11-18 13:22 ` Michal Simek
2016-11-28 15:44 ` Mason
2016-11-28 16:15 ` Arnd Bergmann
2016-11-28 16:52 ` Mason
2016-11-29 7:29 ` Rameshwar Sahu
2016-11-30 10:51 ` Sebastian Frias
2016-11-30 13:17 ` Michal Simek
2016-11-28 16:23 ` Sebastian Frias
2016-12-01 4:09 ` Shawn Lin
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=582EF744.8090307@free.fr \
--to=slash.tmp@free.fr \
--cc=adrian.hunter@intel.com \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jszhang@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh@kernel.org \
--cc=rsahu@apm.com \
--cc=shawn.lin@rock-chips.com \
--cc=soren.brinkmann@xilinx.com \
--cc=stripathi@apm.com \
--cc=ulf.hansson@linaro.org \
--cc=x.xie@freescale.com \
--cc=zach.brown@ni.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 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).