On Mon, Oct 12, 2009 at 11:08:58AM +0300, Eduardo Valentin wrote: > I'm afraid using dev_name is not that easy. The mmc driver generates device > name at runtime. That's why this board file setups .dev at runtime as well. > rx51_twlgpio_setup -> twl4030_mmc_init -> omap2_init_mmc > So, changing this supply to something static using .dev_name it is not > possible with current code. That would need refactoring the whole mmc and > hsmmc setup. And the device naming procedure is dependent on cpu as well. > Check arch/arm/mach-omap2/device.c:omap2_init_mmc. Oh, dear - that sounds broken for hardware that's fixed on the board. That said, the code there looks like it's supposed to come out with the same answer each time it's run? How does this work with the clock API? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
