On 11/04/16 17:26, Laurent Pinchart wrote:
> On Friday 19 Feb 2016 11:59:40 Marc Zyngier wrote:
>> On 19/02/16 09:18, Linus Walleij wrote:
>>> Top-quoting so everyone on the new To:-line gets the context.
>>>
>>> I definately need an indication from an irqchip maintainer like tglx or
>>> Marc Z
Hi Linus,
On Thu, Feb 25, 2016 at 3:19 PM, Linus Walleij wrote:
> On Thu, Feb 25, 2016 at 10:37 AM, Geert Uytterhoeven
> wrote:
>> On Thu, Feb 25, 2016 at 10:07 AM, Linus Walleij
>> wrote:
>>> On Thu, Feb 18, 2016 at
Hi Linus,
On Thu, Feb 25, 2016 at 10:07 AM, Linus Walleij
wrote:
> On Thu, Feb 18, 2016 at 5:06 PM, Geert Uytterhoeven
> wrote:
>
>> The R-Car GPIO driver handles Runtime PM for requested GPIOs only.
>>
>> When using a GPIO purely as an
On Thu, Feb 18, 2016 at 5:06 PM, Geert Uytterhoeven
wrote:
> The R-Car GPIO driver handles Runtime PM for requested GPIOs only.
>
> When using a GPIO purely as an interrupt source, no Runtime PM handling
> is done, and the GPIO module's clock may not be enabled.
>
> To
Hi Linus,
On 19/02/16 09:18, Linus Walleij wrote:
> Top-quoting so everyone on the new To:-line gets the context.
>
> I definately need an indication from an irqchip maintainer like tglx or Marc Z
> before I merge this. Also, as in reply to the previous letter, coordinate
> efforts with Jon
The R-Car GPIO driver handles Runtime PM for requested GPIOs only.
When using a GPIO purely as an interrupt source, no Runtime PM handling
is done, and the GPIO module's clock may not be enabled.
To fix this:
- Add .irq_request_resources() and .irq_release_resources() callbacks
to handle