2015-08-10 11:26 GMT+02:00 Mika Westerberg <[email protected]>: > On Mon, Aug 10, 2015 at 11:20:04AM +0200, Christian Hartmann wrote: >> @Mika: I actually view a patch by you from 6. May 2015 where you >> added dev_gpio_irq_get() and the acpi_dev_gpio_irq_get() functions, >> seems to be related here to, right?? > > That's right if you have GpioInt -resource somewhere you need to > translate to Linux IRQ number (and use it via irqchip instead of gpiolib > API). > > What was done for I2C core with addition of acpi_dev_gpio_irq_get() is > that now it automatically takes first GpioInt of an I2C device and > assigns the translated IRQ number to client->irq if it is not yet > assigned to a valid IRQ.
Hi, @Mika some feedback to the first patch today I have patched it to use the acpi_dev_gpio_irq_get() and after reboot I have a message seen below, it seems the irq uses actually the gpio pin 146 . [ 6.195479] acpi WM510205:00: GPIO: looking up 0 in _CRS [ 6.195560] arizona spi-WM510205:00: arizona_of_get_core_pdata (ACPI) using irq 146 So I go on and patching again to have also the ldoena and reset lines getting via acpi... cheers chris -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
