Hi, On 8/3/2010 11:34 PM, Alan Cox wrote: > (And the correct patch attached this time) > > From: Wen Wang <wen.w.wang@xxxxxxxxx> > > Initial release of the driver. Updated and verified on hardware. > > Cleaned up as follows > > Alan Cox: > Squash down the switches into tables, and use the PCI ident field. We > could perhaps take this further and put the platform and port number into > this. > uint32t -> u32 > bracketing of case statements > spacing and '!' usage > Check the speed (which is now 0/1/2) is valid and ignore otherwise. > > Arjan van de Ven: > Initial power management hooks > > > Signed-off-by: Wen Wang <wen.w.wang@xxxxxxxxx> > Signed-off-by: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx> > Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx> > --- > > drivers/i2c/busses/Kconfig | 9 > drivers/i2c/busses/Makefile | 1 > drivers/i2c/busses/i2c-mrst.c | 1082 +++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 1092 insertions(+), 0 deletions(-) > create mode 100644 drivers/i2c/busses/i2c-mrst.c > > > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig > index 15a9702..46b9acb 100644 > --- a/drivers/i2c/busses/Kconfig > +++ b/drivers/i2c/busses/Kconfig > @@ -420,6 +420,15 @@ config I2C_IXP2000 > This driver is deprecated and will be dropped soon. Use i2c-gpio > instead. > > +config I2C_MRST > + tristate "Intel Moorestown/Medfield Platform I2C controller" > + help > + Say Y here if you have an Intel Moorestown/Medfield platform I2C > + controller. > + > + This support is also available as a module. If so, the module > + will be called i2c-mrst. > + > config I2C_MPC > tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" > depends on PPC32 I'm not sure how commonly used MRST mnemonic is in the Intel's hardware/software resources, but IMO, MRST is not easy to imagine that it represents "Moorstone". But this is not such a big deal. > diff --git a/drivers/i2c/busses/i2c-mrst.c b/drivers/i2c/busses/i2c-mrst.c > new file mode 100644 > index 0000000..79f45fb > --- /dev/null > +++ b/drivers/i2c/busses/i2c-mrst.c > @@ -0,0 +1,1082 @@ > +/* > + * Support for Moorestown/Medfield I2C chip > + * > + * Copyright (c) 2009 Intel Corporation. > + * Copyright (c) 2009 Synopsys. Inc. Having a quick glance of the patch, the driver is similar to the existing I2C_DESIGNWARE driver. Presumably Intel people have already checkekd the i2c-designware.c and made a decision that it would be reasonable to create a new I2C driver to incorporate its requirements (such as PCI resource handlings, power management code, etc.), rather than to extend the existing one. Is my understanding correct? I'm not objecting to the patch, but would like to know the background of this driver, as one of the DW users. -- Shinya Kuribayashi Renesas Electronics -- 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
