On Thursday, November 24, 2016 10:48:58 AM CET Thomas Petazzoni wrote: > Hello, > > On Thu, 24 Nov 2016 10:44:48 +0100, Gregory CLEMENT wrote: > > > "A single Xenon IP can support multiple slots. > > Each slot acts as an independent SDHC. It owns independent resources, such > > as register sets clock and PHY. > > Each slot should have an independent device tree node." > > I think this wording is still very confusing, and continues to cause > confusion. > > We should just state that each Xenon controller supports a single slot, > and that's it. > > The text still says "a single Xenon IP can support multiple slots", > which continues to cause confusion. Agreed. Ideally we'd find out why exactly the slot number must be used for accessing some of the registers to have a better explanation to put in there, aside from stating that only one slot is supported but the number must be set. Could it be that this is some form of pinmuxing, i.e. that each controller could in theory be used for any of the slots but you have to pick one of them? Arnd -- 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
