Message ID | 1573756521-27373-1-git-send-email-ilina@codeaurora.org (mailing list archive) |
---|---|
Headers | show |
Series | Support wakeup capable GPIOs | expand |
Hi Lina, On 2019-11-14 18:35, Lina Iyer wrote: > Hi all, > > Thanks for all the reviews. > > Here is the next spin of the wakeup capable GPIO support. In order to > facilitate basic support available in the kernel, I have dropped the > SPI > register configuration. The feature was added when this series was > restarted based on new hierarchy support in gpiolib. But, the SPI > configuration can be done in the firmware. This would avoid a whole > lot > of code in linux that serve little to no purpose. Users of GPIO never > have the need to change the trigger type (level edge and vice-versa) > and > the basic configuration can be set in the firmware before boot. > > Changes in v1: > - Address review comments > - Add Reviewed-by tags > - Drop SPI config patches > - Rebase on top of Rajendra's PDC changes [6] > > Changes in RFC v2[5]: > - Address review comments #3, #4, #6, #7, #8, #9, #10 > - Rebased on top of linux-next GPIO latest patches > [1],[3],[4] > - Increase PDC max irqs in #2 (avoid merge conflicts with > downstream) > - Add Reviewed-by #5 > > Please consider reviewing these patches. It has been a long time coming, and I'm minded to take the first 9 patches into the irqchip tree. Anyone objects? The last 3 patches can go via the platform maintainer tree. M.
On Fri, Nov 15 2019 at 03:36 -0700, Marc Zyngier wrote: >Hi Lina, > >On 2019-11-14 18:35, Lina Iyer wrote: >>Hi all, >> >>Thanks for all the reviews. >> >>Here is the next spin of the wakeup capable GPIO support. In order to >>facilitate basic support available in the kernel, I have dropped the >>SPI >>register configuration. The feature was added when this series was >>restarted based on new hierarchy support in gpiolib. But, the SPI >>configuration can be done in the firmware. This would avoid a whole >>lot >>of code in linux that serve little to no purpose. Users of GPIO never >>have the need to change the trigger type (level edge and vice-versa) >>and >>the basic configuration can be set in the firmware before boot. >> >>Changes in v1: >> - Address review comments >> - Add Reviewed-by tags >> - Drop SPI config patches >> - Rebase on top of Rajendra's PDC changes [6] >> >>Changes in RFC v2[5]: >> - Address review comments #3, #4, #6, #7, #8, #9, #10 >> - Rebased on top of linux-next GPIO latest patches >>[1],[3],[4] >> - Increase PDC max irqs in #2 (avoid merge conflicts with >> downstream) >> - Add Reviewed-by #5 >> >>Please consider reviewing these patches. > >It has been a long time coming, and I'm minded to take the first 9 >patches into the irqchip tree. Anyone objects? The last 3 patches >can go via the platform maintainer tree. > Sounds good Marc. Thanks, Lina
Quoting Lina Iyer (2019-11-14 10:35:09) > Hi all, > > Thanks for all the reviews. > > Here is the next spin of the wakeup capable GPIO support. In order to > facilitate basic support available in the kernel, I have dropped the SPI > register configuration. The feature was added when this series was > restarted based on new hierarchy support in gpiolib. But, the SPI > configuration can be done in the firmware. This would avoid a whole lot > of code in linux that serve little to no purpose. Users of GPIO never > have the need to change the trigger type (level edge and vice-versa) and > the basic configuration can be set in the firmware before boot. Awesome! I'm glad we don't need to worry about configuring that in the kernel.