On Fri, 2013-07-26 at 18:10 +0100, Stephen Warren wrote: > > +- uhs-sdr12: the host supports UHS SDR12 mode > > +- uhs-sdr25: the host supports UHS SDR25 mode > > +- uhs-sdr50: the host supports UHS SDR50 mode > > +- uhs-sdr104: the host supports UHS SDR104 mode > > +- uhs-ddr50: the host supports UHS DDR50 mode > > +- ddr-1v2: the host can support DDR, using 1.2V VccQ > > +- ddr-1v8: the host can support DDR, using 1.8V VccQ I understand that they are equivalent of the mmc caps #defines. Having absolutely no UHS knowledge (nor access to the spec) I'm just wondering if some of them couldn't be derived from the "environment", being the way the host is wired up? An example would be the classic OCR VDD fields - the voltage range bits are taken from the regulator "vmmc" supply (see mmc_regulator_get_supply()). Of course I this may be completely wrong approach here... Pawel -- 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
