Cc Eric since he can add SFI table for MMC driver.
> -----Original Message----- > From: Alan Cox [mailto:[email protected]] > Sent: Wednesday, November 10, 2010 12:19 AM > To: Dong, Chuanxiao > Cc: [email protected]; [email protected]; Brown, Len > Subject: Re: [Meego-kernel] [PATCH v1 3/3]mmc:implement the reset eMMC card > part for MFLD sdhci host controller > > > > Can we get something like mmc_reset_0, mmc_reset_1, mmc_reset_2 in > > > the SFI names so that for any future product we won't need code > > > changes. > > > > Alan, I have a question about the SFI table. > > I have checked some drivers which also need request GPIO lines. Found > > that those drivers can get the GPIO lines' number from the driver > > specified platform data passed in their 'probe' routine. They are > > registered as a platform device. However MMC driver is registered as > > a PCI device, how can it get the GPIO lines' number from a driver > > specified platform data? Any idea? > > The ideal case if the firmware people can do it would be to put the > GPIO number in the PCI configuration space somewhere for each device. > That would future proof it totally. > > Otherwise we should probably expose the get_gpio_by_name function either > in mrst.c or the sfi driver > > Cc'd Len to see what he thinks - should it be in the SFI or the MRST > code ? _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
