Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume

On Fri, Nov 20, 2015 at 10:35 AM, Grygorii Strashko wrote: > Hi Santosh, > > On 11/20/2015 07:23 PM, santosh shilimkar wrote: >> + Thomas, Marc >> >> On 11/20/2015 5:57 AM, Grygorii Strashko wrote: >>> Now the System stall is observed on TI AM437x based board >>>

Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume

On Fri, Nov 20, 2015 at 11:28 AM, Grygorii Strashko <grygorii.stras...@ti.com> wrote: > On 11/20/2015 09:09 PM, John Stultz wrote: >> On Fri, Nov 20, 2015 at 10:35 AM, Grygorii Strashko >> <grygorii.stras...@ti.com> wrote: >>> Hi Santosh, >>> >&g

Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume

On Fri, Nov 20, 2015 at 10:46 AM, Marc Zyngier wrote: > > This patch has a very specific purpose: instructing the core code that > this timer will never stop ticking, ever. It is really targeted at > virtual machines, whose timer is backed by the host timer, even when the >

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

On Tue, Sep 29, 2015 at 1:44 PM, Felipe Balbi wrote: > Introduce a new clocksource driver for Texas > Instruments 32.768 Hz device which is available > on most OMAP-like devices. > > Signed-off-by: Felipe Balbi > --- > drivers/clocksource/Kconfig| 8 +++ >

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

On Tue, Sep 29, 2015 at 1:44 PM, Felipe Balbi wrote: > Introduce a new clocksource driver for Texas > Instruments 32.768 Hz device which is available > on most OMAP-like devices. > > Signed-off-by: Felipe Balbi > --- > drivers/clocksource/Kconfig| 8 +++ >

Re: [PATCH] clocksource: Allow toggling between runtime and persistent clocksource for idle

On Mon, Jul 6, 2015 at 12:12 AM, Tony Lindgren t...@atomide.com wrote: Some persistent clocksources can be on a slow external bus. For shorter latencies for RT use, let's allow toggling the clocksource during idle between a faster non-persistent runtime clocksource and a slower persistent

Re: [PATCH] clocksource: Allow toggling between runtime and persistent clocksource for idle

On Mon, Jul 6, 2015 at 10:34 AM, Thomas Gleixner t...@linutronix.de wrote: On Mon, 6 Jul 2015, John Stultz wrote: On Mon, Jul 6, 2015 at 12:12 AM, Tony Lindgren t...@atomide.com wrote: Some persistent clocksources can be on a slow external bus. For shorter latencies for RT use, let's allow

Re: [PATCH] clocksource: Allow toggling between runtime and persistent clocksource for idle

the resolution between the clocksources can be different.. In the test case I have the slow timer is always on and of a lower resolution than the ARM global timer being used during runtime. Got some handy timer test in mind you want me to run to provide data on the accuracy? John Stultz might have

Re: [PATCH 1/8] time: Add y2038 safe read_boot_clock64()

On Wed, Mar 18, 2015 at 5:48 AM, pang.xun...@zte.com.cn wrote: Ping ... Thanks for the reminder. Since there's not been any objections, I'm queuing this up. thanks -john -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org

Re: [PATCH] ARM: convert arm/arm64 arch timer to use CLKSRC_OF init

On 03/25/2013 03:36 PM, Arnd Bergmann wrote: On Monday 25 March 2013, Rob Herring wrote: I count integrator-cp, realview, versatile and non-DT VExpress that do this (not surprisingly) and 25 platforms or timer implementations plus arm64 that do sched_clock setup in time_init. What's broken by

Re: Minimum timing resolution in Ubuntu/Linaro on the PandaBoard ES

On Tue, 2012-02-07 at 21:21 -0800, Dmitry Antipov wrote: BTW, I have no ideas why clock_getres(CLOCK_REALTIME,...) returns {0, 1} regardless of underlying clock source. I expect {0, 30517} for 32K timer and {0, 26} for MPU timer. Yea. I had proposed to export the underlying clocksource's

Re: Minimum timing resolution in Ubuntu/Linaro on the PandaBoard ES

On Wed, 2012-02-08 at 04:32 -0500, Andrew Richardson wrote: Ah, very interesting. dmesg | grep clock [0.00] OMAP clockevent source: GPTIMER1 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms Hrm. So

Re: Minimum timing resolution in Ubuntu/Linaro on the PandaBoard ES

On Wed, 2012-02-08 at 04:32 -0500, Andrew Richardson wrote: Ah, very interesting. dmesg | grep clock [0.00] OMAP clockevent source: GPTIMER1 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms Hrm. So

Re: [RFC PATCH 1/5] arm:omap1/2/3/4:Convert 32k-Sync clocksource driver to platform_driver

On Wed, 2012-01-18 at 16:58 +0530, Vaibhav Hiremath wrote: +/** + * read_persistent_clock - Return time from a persistent clock. + * + * Reads the time from a source which isn't disabled during PM, the + * 32k sync timer. Convert the cycles elapsed since last read into + * nsecs and adds

Re: [PATCH] rtc: twl: Fix registration vs. init order

On Wed, 2011-08-10 at 20:20 -0700, Todd Poynor wrote: Only register as an RTC device after the hardware has been successfully initialized. The RTC class driver will call back to this driver to read a pending alarm, and other drivers watching for new devices on the RTC class may read the RTC

Re: [PATCH] rtc-twl: Switch to using threaded irq

On Mon, 2011-06-27 at 18:45 +0200, Sebastian Reichel wrote: On Tue, May 31, 2011 at 10:51:39AM +0200, Sebastian Reichel wrote: The driver is accessing to i2c bus in interrupt handler. Therefore, it should use threaded irq. I think the patch should also remove the local_irq_enable() call

RE: [PATCH] rtc-twl: Switch to using threaded irq

On Thu, 2011-05-05 at 07:51 +, ilkka.koski...@nokia.com wrote: Hi, Tony and John: What would be the appropriate path for this patch? I'd probably push it through omap maintainer path, as its hardware specific and can be better tested there. thanks -john On Apr 13, 2011 Krishnamoorthy,

Re: [regression] 2.6.39-rc1 - Beagleboard usbnet broken

On Mon, Apr 4, 2011 at 2:22 AM, Mark Jackson mpfj-l...@mimc.co.uk wrote: Running 2.6.38 on my beagleboard, I can boot using nfs:- [snip] I have just tried out 2.6.39-rc1, and the usbnet is no longer detected:- Yea, I hit something similar, where on the beagleboard I only see the root hubs, and

Re: Timekeeping issue on aggressive suspend/resume

On Mon, 2010-06-14 at 00:46 -0700, Suresh Rajashekara wrote: On Thu, Jun 10, 2010 at 12:52 PM, john stultz johns...@us.ibm.com wrote: I think Thomas was suggesting that you consider creating a option for where CLOCK_MONOTONIC included total_sleep_time. In that case the *hack

Re: Timekeeping issue on aggressive suspend/resume

On Wed, 2010-06-09 at 23:34 -0700, Suresh Rajashekara wrote: On Wed, Jun 9, 2010 at 1:22 PM, Thomas Gleixner t...@linutronix.de wrote: Though we could change that conditionally - the default would still be the freeze of jiffies and CLOCK_MONOTONIC for historical compability. If I were to