From: Tero Kristo <t-kristo@ti.com>
To: Lokesh Vutla <a0131933@ti.com>, Paul Walmsley <paul@pwsan.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
jonathanh@nvidia.com
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
Sekhar Nori <nsekhar@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] ARM: OMAP2+: Fix updating of sysconfig register
Date: Wed, 2 Mar 2016 09:38:43 +0200 [thread overview]
Message-ID: <56D69883.6070603@ti.com> (raw)
In-Reply-To: <56D65FD4.4090206@ti.com>
On 03/02/2016 05:36 AM, Lokesh Vutla wrote:
>
>
> On Tuesday 01 March 2016 10:33 PM, Paul Walmsley wrote:
>> + Jon Hunter
>>
>> On Tue, 1 Mar 2016, Lokesh Vutla wrote:
>>
>>> commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle
>>> when necessary") talks about verification of sysconfig cache value before
>>> updating it, only during idle path. But the patch is adding the
>>> verification in the enable path. So, adding the check in a proper place
>>> as per the commit description.
>>>
>>> Not keeping this check during enable path as there is a chance of losing
>>> context and it is safe to do on idle as the context of the register will
>>> never be lost while the device is active.
>
> When the patch was originally posted[1], this check was in proper place
> itself. Not sure what happened after that.
Looks like a merge conflict to me.
The patch from Lokesh fixes it, so:
Acked-by: Tero Kristo <t-kristo@ti.com>
>
> [1] https://www.mail-archive.com/linux-omap%40vger.kernel.org/msg78032.html
>
> Thanks and regards,
> Lokesh
>
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> ---
>>> arch/arm/mach-omap2/omap_hwmod.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
>>> index e9f65fe..71b3747 100644
>>> --- a/arch/arm/mach-omap2/omap_hwmod.c
>>> +++ b/arch/arm/mach-omap2/omap_hwmod.c
>>> @@ -1416,9 +1416,7 @@ static void _enable_sysc(struct omap_hwmod *oh)
>>> (sf & SYSC_HAS_CLOCKACTIVITY))
>>> _set_clockactivity(oh, oh->class->sysc->clockact, &v);
>>>
>>> - /* If the cached value is the same as the new value, skip the write */
>>> - if (oh->_sysc_cache != v)
>>> - _write_sysconfig(v, oh);
>>> + _write_sysconfig(v, oh);
>>>
>>> /*
>>> * Set the autoidle bit only after setting the smartidle bit
>>> @@ -1481,7 +1479,9 @@ static void _idle_sysc(struct omap_hwmod *oh)
>>> _set_master_standbymode(oh, idlemode, &v);
>>> }
>>>
>>> - _write_sysconfig(v, oh);
>>> + /* If the cached value is the same as the new value, skip the write */
>>> + if (oh->_sysc_cache != v)
>>> + _write_sysconfig(v, oh);
>>> }
>>>
>>> /**
>>> --
>>> 2.1.4
>>>
>>
>>
>> - Paul
>>
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: OMAP2+: Fix updating of sysconfig register
Date: Wed, 2 Mar 2016 09:38:43 +0200 [thread overview]
Message-ID: <56D69883.6070603@ti.com> (raw)
In-Reply-To: <56D65FD4.4090206@ti.com>
On 03/02/2016 05:36 AM, Lokesh Vutla wrote:
>
>
> On Tuesday 01 March 2016 10:33 PM, Paul Walmsley wrote:
>> + Jon Hunter
>>
>> On Tue, 1 Mar 2016, Lokesh Vutla wrote:
>>
>>> commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle
>>> when necessary") talks about verification of sysconfig cache value before
>>> updating it, only during idle path. But the patch is adding the
>>> verification in the enable path. So, adding the check in a proper place
>>> as per the commit description.
>>>
>>> Not keeping this check during enable path as there is a chance of losing
>>> context and it is safe to do on idle as the context of the register will
>>> never be lost while the device is active.
>
> When the patch was originally posted[1], this check was in proper place
> itself. Not sure what happened after that.
Looks like a merge conflict to me.
The patch from Lokesh fixes it, so:
Acked-by: Tero Kristo <t-kristo@ti.com>
>
> [1] https://www.mail-archive.com/linux-omap%40vger.kernel.org/msg78032.html
>
> Thanks and regards,
> Lokesh
>
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> ---
>>> arch/arm/mach-omap2/omap_hwmod.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
>>> index e9f65fe..71b3747 100644
>>> --- a/arch/arm/mach-omap2/omap_hwmod.c
>>> +++ b/arch/arm/mach-omap2/omap_hwmod.c
>>> @@ -1416,9 +1416,7 @@ static void _enable_sysc(struct omap_hwmod *oh)
>>> (sf & SYSC_HAS_CLOCKACTIVITY))
>>> _set_clockactivity(oh, oh->class->sysc->clockact, &v);
>>>
>>> - /* If the cached value is the same as the new value, skip the write */
>>> - if (oh->_sysc_cache != v)
>>> - _write_sysconfig(v, oh);
>>> + _write_sysconfig(v, oh);
>>>
>>> /*
>>> * Set the autoidle bit only after setting the smartidle bit
>>> @@ -1481,7 +1479,9 @@ static void _idle_sysc(struct omap_hwmod *oh)
>>> _set_master_standbymode(oh, idlemode, &v);
>>> }
>>>
>>> - _write_sysconfig(v, oh);
>>> + /* If the cached value is the same as the new value, skip the write */
>>> + if (oh->_sysc_cache != v)
>>> + _write_sysconfig(v, oh);
>>> }
>>>
>>> /**
>>> --
>>> 2.1.4
>>>
>>
>>
>> - Paul
>>
next prev parent reply other threads:[~2016-03-02 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 11:48 [RFC PATCH] ARM: OMAP2+: Fix updating of sysconfig register Lokesh Vutla
2016-03-01 11:48 ` Lokesh Vutla
2016-03-01 17:03 ` Paul Walmsley
2016-03-01 17:03 ` Paul Walmsley
2016-03-02 3:36 ` Lokesh Vutla
2016-03-02 3:36 ` Lokesh Vutla
2016-03-02 7:38 ` Tero Kristo [this message]
2016-03-02 7:38 ` Tero Kristo
2016-03-08 7:01 ` Paul Walmsley
2016-03-08 7:01 ` Paul Walmsley
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=56D69883.6070603@ti.com \
--to=t-kristo@ti.com \
--cc=a0131933@ti.com \
--cc=jonathanh@nvidia.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=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.