On Thu, Jan 19, 2012 at 09:08:43AM +0100, Uwe Kleine-König wrote: > Hello, > > On Thu, Jan 19, 2012 at 12:01:33PM +1100, Marc Reilly wrote: > > All spi specific code is moved into a new module. The mc13xxx > > struct moves to the include file by necessity. > > > > A new config choice selects the bus type with SPI as the first item > > (default selection) to remain compatible with existing configs. > > > > Signed-off-by: Marc Reilly <marc@xxxxxxxxxxxxxxx> > > --- > > +choice > > + tristate "MC13XXX Bus interface type" > > + depends on MFD_MC13XXX > > + default MFD_MC13XXX_SPI > > + help > > + The MC13XXX family can be connected over an SPI or I2C bus. > > + Select the appropriate option for your hardware configuration. > > + > > +config MFD_MC13XXX_SPI > > + tristate "SPI interface" > > + depends on SPI_MASTER > > + help > > + Select this if your MC13xxx is connected via an SPI bus. > > + > > +endchoice > > + > Hmm, you cannot have both, spi and i2c support? +1 on Uwe's comment. We're going multiplatform. I2C and SPI support should not be mutually exclusive. g. -- 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
