On 05/29/2014 06:09 PM, Mark Rutland wrote:
> Hi Preeti,
>
> On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
>> Hi Lorenzo,
>>
>> On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
>>> On platforms implementing CPU power management, the CPUidle subsystem
>>> can allow CPUs to enter
On 05/29/2014 06:09 PM, Mark Rutland wrote:
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states
table as a broadcast source for
> > oneshot events. So we can't conditionally register the hrtimer based
> > broadcast device.
> >
> > Perhaps we could replace "now present by default" with "which is
> > unconditionally registered in case no suita
ces
> that may have been registered are suitable as a broadcast source for
> oneshot events. So we can't conditionally register the hrtimer based
> broadcast device.
>
> Perhaps we could replace "now present by default" with "which is
> unconditionally registered in cas
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
> Hi Lorenzo,
>
> On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
> > On platforms implementing CPU power management, the CPUidle subsystem
> > can allow CPUs to enter idle states where local timers logic is lost on
>
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
> Hi Lorenzo,
>
> On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
> > On platforms implementing CPU power management, the CPUidle subsystem
> > can allow CPUs to enter idle states where local timers logic is lost on
>
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
> always-on
On Thu, May 29, 2014 at 10:23:01AM +0100, Lorenzo Pieralisi wrote:
> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
>
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt
On Thu, May 29, 2014 at 10:23:01AM +0100, Lorenzo Pieralisi wrote:
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on
power
Hi Preeti,
On Thu, May 29, 2014 at 12:04:36PM +0100, Preeti U Murthy wrote:
Hi Lorenzo,
On 05/29/2014 02:53 PM, Lorenzo Pieralisi wrote:
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on
power
this:
-- 8 --
Subject: [PATCH] arm64: kernel: initialize broadcast hrtimer based clock event
device
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional
by default with which is
unconditionally registered in case no suitable hardware device is
present?
How about this:
-- 8 --
Subject: [PATCH] arm64: kernel: initialize broadcast hrtimer based clock event
device
On platforms implementing CPU power management, the CPUidle subsystem
can
16 matches
Mail list logo