From: Lokesh Vutla <a0131933@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Lokesh Vutla <lokeshvutla@ti.com>
Cc: tony@atomide.com, t-kristo@ti.com, linux-omap@vger.kernel.org,
nsekhar@ti.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: AMx3xx: hwmod: RTC: Add lock and unlock functions
Date: Thu, 16 Jul 2015 17:58:47 +0530 [thread overview]
Message-ID: <55A7A37F.4080803@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507160013370.32764@utopia.booyaka.com>
Hi Paul,
On Thursday 16 July 2015 05:44 AM, Paul Walmsley wrote:
> Hi
>
> On Wed, 10 Jun 2015, Lokesh Vutla wrote:
>
>> RTC IP have kicker feature which prevents spurious writes to its registers.
>> In order to write into any of the RTC registers, KICK values has to be
>> written to KICK registers.
>>
>> omap_hwmod_rtc_unlock/lock functions writes into these KICK registers
>> inorder to lock and unlock RTC registers.
>> This patch hooks omap_hwmod_rtc_unlock/lock functions into RTC hwmod,
>> so that SYSCONFIG register is updated properly.
>>
>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>> ---
>> arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> index cabc569..2d92958 100644
>> --- a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> +++ b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> @@ -904,6 +904,8 @@ static struct omap_hwmod_class_sysconfig am33xx_rtc_sysc = {
>> static struct omap_hwmod_class am33xx_rtc_hwmod_class = {
>> .name = "rtc",
>> .sysc = &am33xx_rtc_sysc,
>> + .unlock = &omap_hwmod_rtc_unlock,
>> + .lock = &omap_hwmod_rtc_lock,
>> };
>>
>> struct omap_hwmod am33xx_rtc_hwmod = {
>
> The DRA7xx integration from the previous patch should either be combined
> with this patch, or moved into a separate patch like this one (your
> preference).
Ill make a separate patch for DRA7xx integration and repost it.
Thanks and regards,
Lokesh
>
>
> - Paul
>
WARNING: multiple messages have this Message-ID (diff)
From: a0131933@ti.com (Lokesh Vutla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: AMx3xx: hwmod: RTC: Add lock and unlock functions
Date: Thu, 16 Jul 2015 17:58:47 +0530 [thread overview]
Message-ID: <55A7A37F.4080803@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507160013370.32764@utopia.booyaka.com>
Hi Paul,
On Thursday 16 July 2015 05:44 AM, Paul Walmsley wrote:
> Hi
>
> On Wed, 10 Jun 2015, Lokesh Vutla wrote:
>
>> RTC IP have kicker feature which prevents spurious writes to its registers.
>> In order to write into any of the RTC registers, KICK values has to be
>> written to KICK registers.
>>
>> omap_hwmod_rtc_unlock/lock functions writes into these KICK registers
>> inorder to lock and unlock RTC registers.
>> This patch hooks omap_hwmod_rtc_unlock/lock functions into RTC hwmod,
>> so that SYSCONFIG register is updated properly.
>>
>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>> ---
>> arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> index cabc569..2d92958 100644
>> --- a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> +++ b/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
>> @@ -904,6 +904,8 @@ static struct omap_hwmod_class_sysconfig am33xx_rtc_sysc = {
>> static struct omap_hwmod_class am33xx_rtc_hwmod_class = {
>> .name = "rtc",
>> .sysc = &am33xx_rtc_sysc,
>> + .unlock = &omap_hwmod_rtc_unlock,
>> + .lock = &omap_hwmod_rtc_lock,
>> };
>>
>> struct omap_hwmod am33xx_rtc_hwmod = {
>
> The DRA7xx integration from the previous patch should either be combined
> with this patch, or moved into a separate patch like this one (your
> preference).
Ill make a separate patch for DRA7xx integration and repost it.
Thanks and regards,
Lokesh
>
>
> - Paul
>
next prev parent reply other threads:[~2015-07-16 12:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:26 [PATCH 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks Lokesh Vutla
2015-06-10 9:26 ` Lokesh Vutla
2015-06-10 9:26 ` [PATCH 1/3] ARM: OMAP2+: hwmod: add support for " Lokesh Vutla
2015-06-10 9:26 ` Lokesh Vutla
2015-07-16 0:07 ` Paul Walmsley
2015-07-16 0:07 ` Paul Walmsley
2015-06-10 9:26 ` [PATCH 2/3] ARM: DRA: hwmod: RTC: Add lock and unlock functions Lokesh Vutla
2015-06-10 9:26 ` Lokesh Vutla
2015-07-16 0:13 ` Paul Walmsley
2015-07-16 0:13 ` Paul Walmsley
2015-07-16 12:34 ` Lokesh Vutla
2015-07-16 12:34 ` Lokesh Vutla
2015-06-10 9:26 ` [PATCH 3/3] ARM: AMx3xx: " Lokesh Vutla
2015-06-10 9:26 ` Lokesh Vutla
2015-07-16 0:14 ` Paul Walmsley
2015-07-16 0:14 ` Paul Walmsley
2015-07-16 12:28 ` Lokesh Vutla [this message]
2015-07-16 12:28 ` Lokesh Vutla
2015-07-14 10:09 ` [PATCH 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks Lokesh Vutla
2015-07-14 10:09 ` Lokesh Vutla
2015-07-14 14:51 ` Tero Kristo
2015-07-14 14:51 ` Tero Kristo
2015-07-16 0:15 ` Paul Walmsley
2015-07-16 0:15 ` Paul Walmsley
2015-07-16 7:09 ` Tero Kristo
2015-07-16 7:09 ` Tero Kristo
2015-07-16 10:13 ` Paul Walmsley
2015-07-16 10:13 ` Paul Walmsley
2015-07-16 12:03 ` Tero Kristo
2015-07-16 12:03 ` Tero Kristo
2015-07-16 12:26 ` Lokesh Vutla
2015-07-16 12:26 ` Lokesh Vutla
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=55A7A37F.4080803@ti.com \
--to=a0131933@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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.