On 3.2.2016 09:31, Mason wrote: > On 03/02/2016 08:20, Michal Simek wrote: > >> 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. > > Hello Michal, > > I'm even more confused. > > Arasan's 2010-02-19 data sheet is titled > SD3.0 / SDIO3.0 / eMMC4.4 AHB Host Controller > > Page 28 of the Xilinx data sheet mentions > SD2.0 / SDIO2.0 / MMC3.31 AHB Host Controller > Version 8.9A_apr02nd_2010 > > It does not make sense that Arasan would support SD3.0 in February, > then go back to SD 2.0 in April. > > I do note eMMC4.4 vs MMC3.31 => perhaps these are two *different* > IP blocks? > > Do your data sheets come with revision history? I don't have datasheet for this IP in my hand that's why I can't check it. But I can't see any problem with it. Our zynq SoC supports SD2.0 and it was requirement at that time. Bugs can happen. Arasan fixed it and create new version. At the same time can have 3.0 versions but vendor is just decide not to use it for whatever reason. That's why timing of features and versions can upgrade any time and unfortunately bugs happen. Thanks, Michal -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
