From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: alexandre.belloni@free-electrons.com, k.kozlowski@samsung.com,
javier@osg.samsung.com, broonie@kernel.org,
gregkh@linuxfoundation.org, a.zummo@towertech.it,
cw00.choi@samsung.com, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH V7 5/5] rtc: max77686: move initialisation of rtc regmap, irq chip locally
Date: Wed, 10 Feb 2016 16:08:28 +0000 [thread overview]
Message-ID: <20160210160828.GE26950@x1> (raw)
In-Reply-To: <1455038794-9921-6-git-send-email-ldewangan@nvidia.com>
On Tue, 09 Feb 2016, Laxman Dewangan wrote:
> To make RTC block of MAX77686/MAX77802 as independent driver,
> move the registration of i2c device, regmap for register access
> and irq_chip for interrupt support inside the RTC driver.
> Removed the same initialisation from MFD driver.
>=20
> Having this change will allow to reuse this driver for different
> PMIC/devices from Maxim Semiconductor if they kept same RTC IP on
> different PMIC. Some of examples as PMIC MAX77620, MAX20024 where
> same RTC IP used and hence driver for these chips will use this
> driver only for RTC support.
>=20
> Suggested-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> CC: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> CC: Javier Martinez Canillas <javier@osg.samsung.com>
> Tested-by: Javier Martinez Canillas <javier@osg.samsung.com>
> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
>=20
> ---
> Changes 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.
>=20
> Changes from V2:
> - Taken care of missed sequence for removing the resource.
> - Fix the crash when doing unbind by using requested_threaded_irq()
> instead of demv_requested_threaded_irq().
>=20
> Changes from V3:
> - Fix the issue of suspend-resume with unbind/bind by unmapping the
> virq.
>=20
> Changes from V4:
> - Dispose mapped irq in error path in probe
>=20
> Changes from V5:
> - Remove the new APIs from regmap as functionality added to dispose the
> virq inside the regmap_del_irq_chip().
>=20
> Changes from V6:
> Make this as 5th of series as regmap change applied independently.
> Also rebase on linux-next 20160209
>=20
> drivers/mfd/max77686.c | 85 +-------------------
> drivers/rtc/rtc-max77686.c | 148 +++++++++++++++++++++++++++++=
+-----
> include/linux/mfd/max77686-private.h | 3 -
> 3 files changed, 130 insertions(+), 106 deletions(-)
Yes, yes, yes!
This is how it should have been done in the first place IMHO.
Acked-by: Lee Jones <lee.jones@linaro.org>
--=20
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org =E2=94=82 Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--=20
--=20
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.
---=20
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 e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: alexandre.belloni@free-electrons.com, k.kozlowski@samsung.com,
javier@osg.samsung.com, broonie@kernel.org,
gregkh@linuxfoundation.org, a.zummo@towertech.it,
cw00.choi@samsung.com, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com
Subject: Re: [PATCH V7 5/5] rtc: max77686: move initialisation of rtc regmap, irq chip locally
Date: Wed, 10 Feb 2016 16:08:28 +0000 [thread overview]
Message-ID: <20160210160828.GE26950@x1> (raw)
In-Reply-To: <1455038794-9921-6-git-send-email-ldewangan@nvidia.com>
On Tue, 09 Feb 2016, Laxman Dewangan wrote:
> To make RTC block of MAX77686/MAX77802 as independent driver,
> move the registration of i2c device, regmap for register access
> and irq_chip for interrupt support inside the RTC driver.
> Removed the same initialisation from MFD driver.
>
> Having this change will allow to reuse this driver for different
> PMIC/devices from Maxim Semiconductor if they kept same RTC IP on
> different PMIC. Some of examples as PMIC MAX77620, MAX20024 where
> same RTC IP used and hence driver for these chips will use this
> driver only for RTC support.
>
> Suggested-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> CC: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> CC: Javier Martinez Canillas <javier@osg.samsung.com>
> Tested-by: Javier Martinez Canillas <javier@osg.samsung.com>
> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> ---
> Changes 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:
> - Taken care of missed sequence for removing the resource.
> - Fix the crash when doing unbind by using requested_threaded_irq()
> instead of demv_requested_threaded_irq().
>
> Changes from V3:
> - Fix the issue of suspend-resume with unbind/bind by unmapping the
> virq.
>
> Changes from V4:
> - Dispose mapped irq in error path in probe
>
> Changes from V5:
> - Remove the new APIs from regmap as functionality added to dispose the
> virq inside the regmap_del_irq_chip().
>
> Changes from V6:
> Make this as 5th of series as regmap change applied independently.
> Also rebase on linux-next 20160209
>
> drivers/mfd/max77686.c | 85 +-------------------
> drivers/rtc/rtc-max77686.c | 148 ++++++++++++++++++++++++++++++-----
> include/linux/mfd/max77686-private.h | 3 -
> 3 files changed, 130 insertions(+), 106 deletions(-)
Yes, yes, yes!
This is how it should have been done in the first place IMHO.
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-02-10 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 17:26 [rtc-linux] [PATCH V7 0/5] rtc: max77686: make max77686 rtc driver as IP driver Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-09 17:26 ` [rtc-linux] [PATCH V7 1/5] rtc: max77686: fix checkpatch error Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-09 17:26 ` [rtc-linux] [PATCH V7 2/5] rtc: max77686: use rtc regmap to access RTC registers Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-09 17:26 ` [rtc-linux] [PATCH V7 3/5] rtc: max77686: avoid reference of parent device info multiple places Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-09 17:26 ` [rtc-linux] [PATCH V7 4/5] mfd: max77686: do not set i2c client data for rtc i2c client Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-10 16:09 ` [rtc-linux] " Lee Jones
2016-02-10 16:09 ` Lee Jones
2016-02-14 23:46 ` [rtc-linux] " Krzysztof Kozlowski
2016-02-14 23:46 ` Krzysztof Kozlowski
2016-02-09 17:26 ` [rtc-linux] [PATCH V7 5/5] rtc: max77686: move initialisation of rtc regmap, irq chip locally Laxman Dewangan
2016-02-09 17:26 ` Laxman Dewangan
2016-02-10 16:08 ` Lee Jones [this message]
2016-02-10 16:08 ` Lee Jones
2016-02-14 23:48 ` [rtc-linux] " Krzysztof Kozlowski
2016-02-14 23:48 ` Krzysztof Kozlowski
2016-02-16 1:09 ` [rtc-linux] Re: [PATCH V7 0/5] rtc: max77686: make max77686 rtc driver as IP driver Alexandre Belloni
2016-02-16 1:09 ` Alexandre Belloni
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=20160210160828.GE26950@x1 \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=ldewangan@nvidia.com \
--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 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.