From: Laxman Dewangan <ldewangan@nvidia.com> To: <lee.jones@linaro.org>, <alexandre.belloni@free-electrons.com>, <k.kozlowski@samsung.com>, <javier@osg.samsung.com> Cc: <cw00.choi@samsung.com>, <linux-kernel@vger.kernel.org>, <rtc-linux@googlegroups.com>, Laxman Dewangan <ldewangan@nvidia.com> Subject: [PATCH V2 0/5] rtc: max77686: make max77686 rtc driver as IP driver Date: Wed, 3 Feb 2016 15:00:43 +0530 [thread overview] Message-ID: <1454491848-26551-1-git-send-email-ldewangan@nvidia.com> (raw) 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.kozlowski@samsung.com> CC: Javier Martinez Canillas <javier@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. 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 palces mfd: max77686: do not set i2c client data for rtc i2c client rtc: max77686: move initialisation of rtc regmap, irq chip locally drivers/mfd/max77686.c | 86 +------------- drivers/rtc/rtc-max77686.c | 212 ++++++++++++++++++++++++++--------- include/linux/mfd/max77686-private.h | 3 - 3 files changed, 160 insertions(+), 141 deletions(-) -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com> To: <lee.jones@linaro.org>, <alexandre.belloni@free-electrons.com>, <k.kozlowski@samsung.com>, <javier@osg.samsung.com> Cc: <cw00.choi@samsung.com>, <linux-kernel@vger.kernel.org>, <rtc-linux@googlegroups.com>, Laxman Dewangan <ldewangan@nvidia.com> Subject: [rtc-linux] [PATCH V2 0/5] rtc: max77686: make max77686 rtc driver as IP driver Date: Wed, 3 Feb 2016 15:00:43 +0530 [thread overview] Message-ID: <1454491848-26551-1-git-send-email-ldewangan@nvidia.com> (raw) 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.kozlowski@samsung.com> CC: Javier Martinez Canillas <javier@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. 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 palces mfd: max77686: do not set i2c client data for rtc i2c client rtc: max77686: move initialisation of rtc regmap, irq chip locally drivers/mfd/max77686.c | 86 +------------- drivers/rtc/rtc-max77686.c | 212 ++++++++++++++++++++++++++--------- include/linux/mfd/max77686-private.h | 3 - 3 files changed, 160 insertions(+), 141 deletions(-) -- 2.1.4 -- -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
next reply other threads:[~2016-02-03 9:42 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-03 9:30 Laxman Dewangan [this message] 2016-02-03 9:30 ` [rtc-linux] [PATCH V2 0/5] rtc: max77686: make max77686 rtc driver as IP driver Laxman Dewangan 2016-02-03 9:30 ` [PATCH V2 1/5] rtc: max77686: fix checkpatch error Laxman Dewangan 2016-02-03 9:30 ` [rtc-linux] " Laxman Dewangan 2016-02-03 9:30 ` [PATCH V2 2/5] rtc: max77686: use rtc regmap to access RTC registers Laxman Dewangan 2016-02-03 9:30 ` [rtc-linux] " Laxman Dewangan 2016-02-03 9:30 ` [PATCH V2 3/5] rtc: max77686: avoid reference of parent device info multiple palces Laxman Dewangan 2016-02-03 9:30 ` [rtc-linux] " Laxman Dewangan 2016-02-03 12:45 ` Javier Martinez Canillas 2016-02-03 12:45 ` [rtc-linux] " Javier Martinez Canillas 2016-02-03 9:30 ` [PATCH V2 4/5] mfd: max77686: do not set i2c client data for rtc i2c client Laxman Dewangan 2016-02-03 9:30 ` [rtc-linux] " Laxman Dewangan 2016-02-03 10:19 ` Krzysztof Kozlowski 2016-02-03 10:19 ` [rtc-linux] " Krzysztof Kozlowski 2016-02-03 12:47 ` Javier Martinez Canillas 2016-02-03 12:47 ` [rtc-linux] " Javier Martinez Canillas 2016-02-03 9:30 ` [PATCH V2 5/5] rtc: max77686: move initialisation of rtc regmap, irq chip locally Laxman Dewangan 2016-02-03 9:30 ` [rtc-linux] " Laxman Dewangan 2016-02-03 10:45 ` Krzysztof Kozlowski 2016-02-03 10:45 ` [rtc-linux] " Krzysztof Kozlowski 2016-02-03 11:22 ` Krzysztof Kozlowski 2016-02-03 11:22 ` [rtc-linux] " Krzysztof Kozlowski 2016-02-03 13:13 ` Laxman Dewangan 2016-02-03 13:13 ` [rtc-linux] " Laxman Dewangan 2016-02-03 12:56 ` Javier Martinez Canillas 2016-02-03 12:56 ` [rtc-linux] " Javier Martinez Canillas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1454491848-26551-1-git-send-email-ldewangan@nvidia.com \ --to=ldewangan@nvidia.com \ --cc=alexandre.belloni@free-electrons.com \ --cc=cw00.choi@samsung.com \ --cc=javier@osg.samsung.com \ --cc=k.kozlowski@samsung.com \ --cc=lee.jones@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rtc-linux@googlegroups.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.