Message ID | 20190313211844.29416-1-ilina@codeaurora.org (mailing list archive) |
---|---|
Headers | show |
Series | support wakeup capable GPIOs | expand |
On 13/03/2019 21:18, Lina Iyer wrote: > Hi all, > > This series adds support for wakeup capable GPIOs. It is based on Thierry's > hiearchical GPIO domains. This approach is based on Stephen's idea [1]. The SoC > that is used for this development is a QCOM SDM845. The current patchset is > rebased on top of 5.0 and adds documentation for the wakeup-parent and > irqdomain-map DT properties along with the the optional irqdomain-map-mask and > irqdomain-map-pass-thru properties. Also incorporating comments from Marc on > the earlier submission [2]. I cleaned up some of the change history in these > patches to match the version number with that of the submission. > > The dtsi patches are based on Bjorn's changes for increased address and cell > size [3] and [4]. > > Kindly review the series. What the status of this? What is the expected merge strategy? Thanks, M.
On Mon, Apr 15 2019 at 06:43 -0600, Marc Zyngier wrote: >On 13/03/2019 21:18, Lina Iyer wrote: >> Hi all, >> >> This series adds support for wakeup capable GPIOs. It is based on Thierry's >> hiearchical GPIO domains. This approach is based on Stephen's idea [1]. The SoC >> that is used for this development is a QCOM SDM845. The current patchset is >> rebased on top of 5.0 and adds documentation for the wakeup-parent and >> irqdomain-map DT properties along with the the optional irqdomain-map-mask and >> irqdomain-map-pass-thru properties. Also incorporating comments from Marc on >> the earlier submission [2]. I cleaned up some of the change history in these >> patches to match the version number with that of the submission. >> >> The dtsi patches are based on Bjorn's changes for increased address and cell >> size [3] and [4]. >> >> Kindly review the series. > >What the status of this? What is the expected merge strategy? > Hi Mark, I ran into a couple of issues, most of which have been sorted out. But there is a hardware requirement to write up another register (to set type), for GPIO wakeup that was missed earlier. I am trying to get that tested out. That's the hold up. Sorry about that. --Lina