Hi, On 02/10/2012 12:05 PM, Peter Ujfalusi wrote: > Hello, > > This series depends on the V3 of MFD: twl6040: Conversion to i2c driver set. > > In order to have proper regulator support for twl6040 on SDP4430, and > PandaBoards I needed to add support for the V1V8, and V2V1 SMPS supplies from > twl6030. > The configuration on both boards (and the TRM recommendations) are the same, so > it make sens to have the V1V8, V2V1 supply configured in the twl-common to avoid > duplicated code in board files. > > The last patch in this series was part of the V2 of MFD: twl6040: Conversion to > i2c driver set. I have added Mark's Reviewd-by tag, and also addressed his > comment regarding to the supplies member of the twl6040 struct (no need to > allocate it separately). > > Regards, > Peter > --- > Peter Ujfalusi (7): > OMAP: 4430SDP: Correct fixed regulator device ID > regulator: twl-regulator: Add fixed LDO for V1V8, V2V1 supply > MFD: twl-core: regulator configuration for twl6030 V1V8, V2V1 SMPS > OMAP4: twl-common: Add twl6030 V1V8, V2V1 SMPS common configuration > OMAP: 4430SDP: Use common configuration for V1V8, V2V1 supplies > OMAP: omap4panda: Use common configuration for V1V8, V2V1 supplies > MFD: TWL6040: Add regulator support for VIO, V2V1 supplies > > arch/arm/mach-omap2/board-4430sdp.c | 11 ++++++-- > arch/arm/mach-omap2/board-omap4panda.c | 4 ++- > arch/arm/mach-omap2/twl-common.c | 43 ++++++++++++++++++++++++++++++++ > arch/arm/mach-omap2/twl-common.h | 2 + > drivers/mfd/twl-core.c | 10 +++++++ > drivers/mfd/twl6040-core.c | 33 +++++++++++++++++++++--- > drivers/regulator/twl-regulator.c | 2 + > include/linux/i2c/twl.h | 2 + > include/linux/mfd/twl6040.h | 2 + > 9 files changed, 101 insertions(+), 8 deletions(-) It has been a week since I have sent this series. It would be great if this be on time for 3.4 merge window (with the depending series which converts the twl6040 mfd part into i2c driver). Thank you, Péter -- 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
