On Tue, May 19, 2009 at 10:56:16PM +0530, Trilok Soni wrote: > I don't know but why people are not encouraging to use mfd_xxx apis > here? Lot's of drivers are available under drivers/mfd, but only > couple of them are using real mfd_xxx apis? Is there anything missing > in those apis? The mfd_ APIs only really help with memory mapped platform devices but a lot of MFD devices are controlled using I2C and SPI interfaces instead. On registration they need to at least do something extra to allow the client devices to access the I2C or SPI control structure, or the client drivers have to do something like fish around using their parent pointer. It's not so much that there's something wrong with the MFD APIs as issues with splitting up I2C and SPI devices for access in a generic manner. With things mapped through struct resource the MFD API is able to provide some help. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
