* Jon Hunter jon-hun...@ti.com [121108 12:43]:
On 11/02/2012 07:32 AM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP
Hi Santosh,
On Tue, Nov 06, 2012 at 20:05:40, Bedia, Vaibhav wrote:
Hi Santosh,
On Tue, Nov 06, 2012 at 03:29:22, Shilimkar, Santosh wrote:
[...]
IMO, assuming that idle will not be useful from the begining is leading
down the path to poor design choices that will be much more
On 11/02/2012 07:32 AM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP domain can keep
running in suspend from a 32K clock
Hi Kevin,
On Mon, Nov 05, 2012 at 23:33:07, Kevin Hilman wrote:
Bedia, Vaibhav vaibhav.be...@ti.com writes:
On Sat, Nov 03, 2012 at 18:34:30, Kevin Hilman wrote:
[...]
Doesn't this also mean that you won't get timer wakeups
in idle? Or are you keeping the domain where the
Hi Santosh,
On Tue, Nov 06, 2012 at 03:29:22, Shilimkar, Santosh wrote:
[...]
IMO, assuming that idle will not be useful from the begining is leading
down the path to poor design choices that will be much more difficult to
fixup down the road in order to add idle support later. We need
Bedia, Vaibhav vaibhav.be...@ti.com writes:
On Sat, Nov 03, 2012 at 18:34:30, Kevin Hilman wrote:
[...]
Doesn't this also mean that you won't get timer wakeups
in idle? Or are you keeping the domain where the clockevent is
on during idle?
The lowest idle state that we are
On Monday 05 November 2012 11:33 PM, Kevin Hilman wrote:
Bedia, Vaibhav vaibhav.be...@ti.com writes:
On Sat, Nov 03, 2012 at 18:34:30, Kevin Hilman wrote:
[...]
Doesn't this also mean that you won't get timer wakeups
in idle? Or are you keeping the domain where the clockevent is
on during
On Sat, Nov 03, 2012 at 22:01:46, Shilimkar, Santosh wrote:
As mentioned on other patch comment, I think this might break your
SOC idle.
Unfortunately we don't have SOC idle.
Regards,
Vaibhav
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message
On 11/02/2012 12:32 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
After reading the TRM, it seems there are two: DMTIMER0 and DMTIMER1.
Looking at the hwmod data though, I don't see a hwmod for DMTIMER0. Can
you explain a little about why DMTIMER0 is
Hi Kevin,
On Sat, Nov 03, 2012 at 21:52:00, Kevin Hilman wrote:
On 11/02/2012 12:32 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
After reading the TRM, it seems there are two: DMTIMER0 and DMTIMER1.
Looking at the hwmod data though, I don't see a hwmod
On 11/02/2012 01:32 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP domain can keep
running in suspend from a 32K clock and
Hi Kevin,
On Sat, Nov 03, 2012 at 17:13:54, Kevin Hilman wrote:
On 11/02/2012 01:32 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The
T
On 11/03/2012 12:47 PM, Bedia, Vaibhav wrote:
Hi Kevin,
On Sat, Nov 03, 2012 at 17:13:54, Kevin Hilman wrote:
On 11/02/2012 01:32 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer
On Sat, Nov 03, 2012 at 18:34:30, Kevin Hilman wrote:
[...]
Doesn't this also mean that you won't get timer wakeups
in idle? Or are you keeping the domain where the clockevent is
on during idle?
The lowest idle state that we are targeting will have MPU powered
off with external
On Friday 02 November 2012 06:02 PM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP domain can keep
running in suspend from a
15 matches
Mail list logo
