From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Mason <slash.tmp@free.fr>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP <linux-omap@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [PATCH] arm: omap2: Kconfig: select TWD and global timer on AM43xx devices
Date: Fri, 13 Nov 2015 08:39:50 -0800 [thread overview]
Message-ID: <56461256.5050209@oracle.com> (raw)
In-Reply-To: <5645E096.1030600@free.fr>
On 11/13/2015 5:07 AM, Mason wrote:
> On 13/11/2015 13:48, Grygorii Strashko wrote:
>> On 11/12/2015 08:06 PM, Felipe Balbi wrote:
>>> Make sure to tell the kernel that AM437x has
>>> TWD and global timers.
>>>
>>> Signed-off-by: Felipe Balbi <balbi@ti.com>
>>> ---
>>>
>>> Hi Tony,
>>>
>>> now that all dependencies are in place, we can
>>> finally enable twd and global_timer for AM437x.
>>>
Is AM437x SMP SOC ? Is TWD on AM437x works in low
power states ?
Probably I haven't followed the recent updates, but does
the TWD supports C3STOP on UP systems ? The broadcast
code was SMP only in past, and TWD use to die in
low power state on past OMAP SOCs.
If either of these are still the issue then
TWD shouldn't be used.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap2: Kconfig: select TWD and global timer on AM43xx devices
Date: Fri, 13 Nov 2015 08:39:50 -0800 [thread overview]
Message-ID: <56461256.5050209@oracle.com> (raw)
In-Reply-To: <5645E096.1030600@free.fr>
On 11/13/2015 5:07 AM, Mason wrote:
> On 13/11/2015 13:48, Grygorii Strashko wrote:
>> On 11/12/2015 08:06 PM, Felipe Balbi wrote:
>>> Make sure to tell the kernel that AM437x has
>>> TWD and global timers.
>>>
>>> Signed-off-by: Felipe Balbi <balbi@ti.com>
>>> ---
>>>
>>> Hi Tony,
>>>
>>> now that all dependencies are in place, we can
>>> finally enable twd and global_timer for AM437x.
>>>
Is AM437x SMP SOC ? Is TWD on AM437x works in low
power states ?
Probably I haven't followed the recent updates, but does
the TWD supports C3STOP on UP systems ? The broadcast
code was SMP only in past, and TWD use to die in
low power state on past OMAP SOCs.
If either of these are still the issue then
TWD shouldn't be used.
Regards,
Santosh
next prev parent reply other threads:[~2015-11-13 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 18:06 [PATCH] arm: omap2: Kconfig: select TWD and global timer on AM43xx devices Felipe Balbi
2015-11-12 18:06 ` Felipe Balbi
2015-11-13 12:48 ` Grygorii Strashko
2015-11-13 12:48 ` Grygorii Strashko
2015-11-13 13:07 ` Mason
2015-11-13 13:07 ` Mason
2015-11-13 16:39 ` santosh shilimkar [this message]
2015-11-13 16:39 ` santosh shilimkar
2015-11-18 14:33 ` Grygorii Strashko
2015-11-18 14:33 ` Grygorii Strashko
2015-11-18 18:01 ` santosh shilimkar
2015-11-18 18:01 ` santosh shilimkar
2015-11-13 17:15 ` Grygorii Strashko
2015-11-13 17:15 ` Grygorii Strashko
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=56461256.5050209@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=balbi@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=slash.tmp@free.fr \
--cc=ssantosh@kernel.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.