Hi Linus,
On 2019/8/14 17:04, Linus Walleij wrote:
Hi Wei,
thanks for your patch!
This doesn't apply for my "devel" branch, can you rebase
on this:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=devel
We have moved some ACPI headers around recently.
Thanks to
On Thu, Aug 15, 2019 at 3:10 PM Andy Shevchenko
wrote:
> On Mon, Aug 12, 2019 at 2:30 PM Wei Xu wrote:
> Linus, I'm wondering if we can do this for all inside the GPIO library.
> Thoughts?
If it's supposed to happen exactly the same way on all ACPI-enabled
gpiochips, I think it is more or less
On Mon, Aug 12, 2019 at 2:30 PM Wei Xu wrote:
>
> Invoke acpi_gpiochip_request_interrupts after the acpi data has been
> attached to the pl061 acpi node to register interruption.
>
> Otherwise it will be failed to register interruption for the ACPI case.
> Because in the
Hi Wei,
thanks for your patch!
This doesn't apply for my "devel" branch, can you rebase
on this:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=devel
We have moved some ACPI headers around recently.
On Mon, Aug 12, 2019 at 1:28 PM Wei Xu wrote:
> Invoke
Invoke acpi_gpiochip_request_interrupts after the acpi data has been
attached to the pl061 acpi node to register interruption.
Otherwise it will be failed to register interruption for the ACPI case.
Because in the gpiochip_add_data_with_key, acpi_gpiochip_add is invoked
after
5 matches
Mail list logo