From: Mason <slash.tmp@free.fr>
To: Felipe Balbi <balbi@ti.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Shawn Guo <shawn.guo@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Linux OMAP <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC/NOT FOR MERGING] HACK: add global/private timers for A9
Date: Thu, 04 Jun 2015 23:00:06 +0200 [thread overview]
Message-ID: <5570BC56.1090305@free.fr> (raw)
In-Reply-To: <20150604203732.GI5710@saruman.tx.rr.com>
On 04/06/2015 22:37, Felipe Balbi wrote:
> On Thu, Jun 04, 2015 at 10:32:40PM +0200, Mason wrote:
>> On 04/06/2015 22:08, Felipe Balbi wrote:
>>
>>> On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
>>>> Also, check /proc/timer_list for a "Broadcast device". If you don't
>>>> define one, the TWD timers are set to periodic mode, with hrtimers
>>>> disabled.
>>>
>>> Did you manage to turn global timer into Broadcast device ?
>>
>> Disclaimer: I am a kernel noob, take everything I say with
>> a rock of salt.
>>
>> As far as I can see, the global timer code doesn't handle
>> frequency changes, whereas the TWD code does.
>
> All right, but TWD has C3STOP and that prevents it from being used as
> broadcast device.
AFAICT, my platform doesn't stop the local timers in low-power
mode, so I just dropped the CLOCK_EVT_FEAT_C3STOP flag.
There's even a patch approved by Arnd somewhere in the thread,
although he did recommend I should investigate to understand
the problem better.
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/NOT FOR MERGING] HACK: add global/private timers for A9
Date: Thu, 04 Jun 2015 23:00:06 +0200 [thread overview]
Message-ID: <5570BC56.1090305@free.fr> (raw)
In-Reply-To: <20150604203732.GI5710@saruman.tx.rr.com>
On 04/06/2015 22:37, Felipe Balbi wrote:
> On Thu, Jun 04, 2015 at 10:32:40PM +0200, Mason wrote:
>> On 04/06/2015 22:08, Felipe Balbi wrote:
>>
>>> On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
>>>> Also, check /proc/timer_list for a "Broadcast device". If you don't
>>>> define one, the TWD timers are set to periodic mode, with hrtimers
>>>> disabled.
>>>
>>> Did you manage to turn global timer into Broadcast device ?
>>
>> Disclaimer: I am a kernel noob, take everything I say with
>> a rock of salt.
>>
>> As far as I can see, the global timer code doesn't handle
>> frequency changes, whereas the TWD code does.
>
> All right, but TWD has C3STOP and that prevents it from being used as
> broadcast device.
AFAICT, my platform doesn't stop the local timers in low-power
mode, so I just dropped the CLOCK_EVT_FEAT_C3STOP flag.
There's even a patch approved by Arnd somewhere in the thread,
although he did recommend I should investigate to understand
the problem better.
Regards.
next prev parent reply other threads:[~2015-06-04 21:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 20:32 [RFC/NOT FOR MERGING] HACK: add global/private timers for A9 Felipe Balbi
2015-06-03 20:32 ` Felipe Balbi
2015-06-03 20:44 ` Tony Lindgren
2015-06-03 20:44 ` Tony Lindgren
2015-06-03 20:55 ` Arnd Bergmann
2015-06-03 20:55 ` Arnd Bergmann
2015-06-03 21:04 ` Felipe Balbi
2015-06-03 21:04 ` Felipe Balbi
2015-06-03 21:28 ` Felipe Balbi
2015-06-03 21:28 ` Felipe Balbi
2015-06-03 21:41 ` Stephen Boyd
2015-06-03 21:41 ` Stephen Boyd
2015-06-03 21:54 ` Felipe Balbi
2015-06-03 21:54 ` Felipe Balbi
2015-06-04 9:46 ` Mason
2015-06-04 9:46 ` Mason
2015-06-04 19:05 ` Felipe Balbi
2015-06-04 19:05 ` Felipe Balbi
2015-06-04 20:08 ` Felipe Balbi
2015-06-04 20:08 ` Felipe Balbi
2015-06-04 20:18 ` Felipe Balbi
2015-06-04 20:18 ` Felipe Balbi
2015-06-04 20:29 ` Felipe Balbi
2015-06-04 20:29 ` Felipe Balbi
2015-06-04 22:20 ` Stephen Boyd
2015-06-04 22:20 ` Stephen Boyd
2015-06-05 15:42 ` Felipe Balbi
2015-06-05 15:42 ` Felipe Balbi
2015-06-04 20:32 ` Mason
2015-06-04 20:32 ` Mason
2015-06-04 20:37 ` Felipe Balbi
2015-06-04 20:37 ` Felipe Balbi
2015-06-04 21:00 ` Mason [this message]
2015-06-04 21:00 ` Mason
2015-06-04 21:46 ` Tony Lindgren
2015-06-04 21:46 ` Tony Lindgren
2015-06-03 22:26 ` Tony Lindgren
2015-06-03 22:26 ` Tony Lindgren
2015-06-04 3:45 ` Felipe Balbi
2015-06-04 3:45 ` Felipe Balbi
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=5570BC56.1090305@free.fr \
--to=slash.tmp@free.fr \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sboyd@codeaurora.org \
--cc=shawn.guo@linaro.org \
--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.