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>,
Krzysztof Mazur <krzysiek@podlesie.net>
Subject: [PATCH 0/4] rtc: max77686: make max77686 rtc driver as IP driver
Date: Tue, 2 Feb 2016 18:46:48 +0530 [thread overview]
Message-ID: <1454419012-18050-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 Mazur <krzysiek@podlesie.net>
CC: Javier Martinez Canillas <javier@osg.samsung.com>
Laxman Dewangan (4):
rtc: max77686: fix checkpatch error
rtc: max77686: use rtc regmap to access RTC registers
rtc: max77686: avoid reference of parent device info multiple palces
rtc: max77686: move initialisation of rtc regmap, irq chip locally
drivers/mfd/max77686.c | 82 +---------
drivers/rtc/Kconfig | 7 +-
drivers/rtc/rtc-max77686.c | 295 ++++++++++++++++++++++++++++-------
include/linux/mfd/max77686-private.h | 16 --
4 files changed, 244 insertions(+), 156 deletions(-)
--
2.1.4
next reply other threads:[~2016-02-02 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 13:16 Laxman Dewangan [this message]
2016-02-02 13:16 ` [PATCH 1/4] rtc: max77686: fix checkpatch error Laxman Dewangan
2016-02-02 23:57 ` Krzysztof Kozlowski
2016-02-03 3:04 ` Javier Martinez Canillas
2016-02-02 13:16 ` [PATCH 2/4] rtc: max77686: use rtc regmap to access RTC registers Laxman Dewangan
2016-02-02 23:59 ` Krzysztof Kozlowski
2016-02-03 3:08 ` Javier Martinez Canillas
2016-02-02 13:16 ` [PATCH 3/4] rtc: max77686: avoid reference of parent device info multiple palces Laxman Dewangan
2016-02-03 0:05 ` Krzysztof Kozlowski
2016-02-03 3:16 ` Javier Martinez Canillas
2016-02-02 13:16 ` [PATCH 4/4] rtc: max77686: move initialisation of rtc regmap, irq chip locally Laxman Dewangan
2016-02-03 1:17 ` Krzysztof Kozlowski
2016-02-03 3:48 ` 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=1454419012-18050-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=krzysiek@podlesie.net \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®