From: Mason <slash.tmp@free.fr>
To: linux-mmc <linux-mmc@vger.kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
Rameshwar Sahu <rsahu@apm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Soren Brinkmann <soren.brinkmann@xilinx.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>,
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 <suneel.garapati@xilinx.com>,
Russell King <linux@arm.linux.org.uk>, Sebastian Frias <sf84@l>
Subject: Re: arasan,sdhci.txt "compatibility" DT binding
Date: Mon, 28 Nov 2016 16:44:39 +0100 [thread overview]
Message-ID: <583C50E7.6030400@free.fr> (raw)
In-Reply-To: <a20b2b4f-15d4-3c29-324c-1ced5dbcc67f@xilinx.com>
Hello,
@Shawn Lin, could you take a look below and tell me exactly
which IP core(s) Rockchip is using in its SoCs?
Based on the feedback I received, here is an updated list of
compatible strings and controller versions dealt with by the
drivers/mmc/host/sdhci-of-arasan.c code.
Xilinx Zynq:
"SD2.0 / SDIO2.0 / MMC3.31 AHB Host Controller"
"arasan,sdhci-8.9a"
NB: 8.9a is the documentation revision (dated 2011-10-19)
subsequent tweaks labeled 9.0a, 9.1a, 9.2a
Xilinx ZynqMP:
"SD3.0 / SDIO3.0 / eMMC4.51 AHB Host Controller"
"arasan,sdhci-8.9a"
NB: using the same compatible string as Zynq
Sigma SMP87xx
"SD3.0 / SDIO3.0 / eMMC4.4 AHB Host Controller"
no compatible string yet, platform-specific init required
APM:
"SD3.0 / SDIO3.0 / eMMC4.41 AHB Host Controller"
"arasan,sdhci-4.9a"
NB: 4.9a appears to be the documentation revision
no functional diff with "arasan,sdhci-8.9a"
Rockchip
Exact IP unknown, waiting for Shawn's answer
"arasan,sdhci-5.1"
NB: 5.1 appears to refer to the eMMC standard supported
On a final note, there are many variations of the Arasan IP.
I've tracked down at least the following:
SD_2.0_SDIO_2.0__MMC_3.31_AHB_Host_Controller.pdf
SD_3.0_SDIO_3.0_eMMC_4.41_OCP_Host_Controller.pdf
SD_3.0_SDIO_3.0_eMMC_4.4__AHB_Host_Controller.pdf
SD_3.0_SDIO_3.0_eMMC_4.51_Host_Controller.pdf
SD_3.0_SDIO_3.0_eMMC_4.5__Host_Controller.pdf
SD_4.1_SDIO_4.1_eMMC_4.51_Host_Controller.pdf
SD_4.1_SDIO_4.1_eMMC_5.1__Host_Controller.pdf
It seems to me the compatible string should specify
the SD/SDIO version AND the eMMC version, since it
seems many combinations are allowed, e.g. eMMC 4.51
has two possible SD versions.
What do you think?
Regards.
next prev parent reply other threads:[~2016-11-28 15:45 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
2016-11-18 13:22 ` Michal Simek
2016-11-28 15:44 ` Mason [this message]
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=583C50E7.6030400@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=linux@arm.linux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh@kernel.org \
--cc=rsahu@apm.com \
--cc=sf84@l \
--cc=shawn.lin@rock-chips.com \
--cc=soren.brinkmann@xilinx.com \
--cc=stripathi@apm.com \
--cc=suneel.garapati@xilinx.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).