Hi Hans, .... > > p.s. > > I love the work you've been doing on the A64, I've not had a chance > to try it out yet though. Have you made any progress with getting > the mmc slot to work ? If not maybe I can make some time I've > prior experience in bringing up the mmc slot on other Allwinner SoCs Thanks for that! So we made some progress on the weekend (with the help of #linux-sunxi): 1) The regulator node was stupidly put by me into a separate child node without putting address and size cells into. So I just moved it into /soc directly now and that seems to fixed the missing regulator. 2) The reset node is a allwinner,sun6i-a31-ahb1-reset, which does not get registered automatically, but by an explicit call from mach-sunxi/. I wonder why we do this (yes, I saw that comment, but still...) and if it would work with a normal MODULE_DEVICE_TABLE() declaration. There is and will be no equivalent to the mach- directory on arm64. 3) As Jens pointed out, the MMC IP block isn't really compatible. Changing the clocks is easy (done already), but we need to come up with code to cover the new phase setting registers in the A64 MMC register block. Interestingly somehow hacking this (pretending it is compatible) seems to work, though I got reports from people about mysterious kernel crashes, so I'm inclined to leave MMC out of the first patch series. So if you could take a look at the new registers (starting at offset 0x140) and work out what we actually need to do here, that would be great. I have no real clue about what they actually do and how they relate to the current output and sample clock phase. To me it looks like we might get away with just triggering the automatic calibration and the hardware does the rest for us - keep your fingers crossed ;-) Cheers, Andre. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
