On 09/02/2016 at 22:56:29 +0530, Laxman Dewangan wrote : > Based on discussion on patch series of MAX77620 when adding separate > driver for max77620 RTC, it is discussed to reuse the max77686 driver > for all CHips MAX77802, MAX77686 and MAX77620. For this, the rtc-max77686 > need to make as IP driver independent of their MFD parent driver. > > This series makes the rtc-max77686 as independent driver from its > parent. Required information is passed through the device parent > which is generic and does not depends on any max77686 specific > header ifnromation. > > CC: Krzysztof Kozlowski <k.kozlow...@samsung.com> > CC: Javier Martinez Canillas <jav...@osg.samsung.com> > > Changes from V1: > - Added reviewed/tested by tag which we got from V1. > - Remove changes from Kconfig. > - Maintain all register definition in max77686 private header and remove > the movement to rtc driver. > - Taken care of all comments on V1 from Krzysztof and Javier. > > Changes from V2: > - Fix the issue of crash in unbind. > > Changes from V3: > - Fix suspend-resume after unbind/bind by unmapping virq in remove callback. > > Changes from V5: > - Abandon the addition of new API in regmap-irq and add dispose of virq > in regmap_del_irq_chip(). > > Changes from V6: > - make regmap change as independent of this series and rebase it on linux-next > 20160209 > > Laxman Dewangan (5): > rtc: max77686: fix checkpatch error > rtc: max77686: use rtc regmap to access RTC registers > rtc: max77686: avoid reference of parent device info multiple places > mfd: max77686: do not set i2c client data for rtc i2c client > rtc: max77686: move initialisation of rtc regmap, irq chip locally >
All applied, thanks. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
