On Fri, Feb 13, 2015 at 02:11:52PM +, Russell King - ARM Linux wrote:
> I think what's going on is that there's a difference in the expectations
> from the PM domain code vs the runtime PM code. I refer to section 5
> of the runtime PM documentation:
>
> | 5. Runtime PM Initialization, Device
On Fri, Feb 13, 2015 at 01:29:25PM +, Russell King - ARM Linux wrote:
> On Mon, Apr 28, 2014 at 01:55:40PM +0200, Ulf Hansson wrote:
> > On 27 April 2014 15:29, Russell King wrote:
> > > The PMU device contains an interrupt controller, power control and
> > > resets. The interrupt controller
On Mon, Apr 28, 2014 at 01:55:40PM +0200, Ulf Hansson wrote:
> On 27 April 2014 15:29, Russell King wrote:
> > The PMU device contains an interrupt controller, power control and
> > resets. The interrupt controller is a little sub-standard in that
> > there is no race free way to clear down pendi
On Mon, Apr 28, 2014 at 01:55:40PM +0200, Ulf Hansson wrote:
> On 27 April 2014 15:29, Russell King wrote:
> > The PMU device contains an interrupt controller, power control and
> > resets. The interrupt controller is a little sub-standard in that
> > there is no race free way to clear down pendi
On 27 April 2014 15:29, Russell King wrote:
> The PMU device contains an interrupt controller, power control and
> resets. The interrupt controller is a little sub-standard in that
> there is no race free way to clear down pending interrupts, so we try
> to avoid problems by reducing the window a
The PMU device contains an interrupt controller, power control and
resets. The interrupt controller is a little sub-standard in that
there is no race free way to clear down pending interrupts, so we try
to avoid problems by reducing the window as much as possible, and
clearing as infrequently as p
