linux-kernel - Re: [PATCH v3 0/9] qcom: support wakeup capable GPIOs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 11 Mar 2019 11:09:26 +0000
From:   Marc Zyngier <marc.zyngier@....com>
To:     Lina Iyer <ilina@...eaurora.org>, swboyd@...omium.org,
        evgreen@...omium.org
Cc:     linux-kernel@...r.kernel.org, rplsssn@...eaurora.org,
        linux-arm-msm@...r.kernel.org, thierry.reding@...il.com,
        bjorn.andersson@...aro.org, dianders@...omium.org,
        linus.walleij@...aro.org
Subject: Re: [PATCH v3 0/9] qcom: support wakeup capable GPIOs

On 22/02/2019 22:18, Lina Iyer wrote:
> Hi all,
> 
> This series is based on idea of setting up a wakeup parent interrupt controller
> for GPIOs that are wakeup capable. The patch is based on Thierry's hierarchical
> GPIO irqdomains. Much of the idea stem's from Stephen's suggestions in [1] with
> some fixes.

Given how long it took to get there, I'm really keen on moving forward
with this as the first implementation. There is a number of things that
needs fixing, but nothing that looks major so far.

> I am posting this series to help with the discussions around this approach.
> Please take a look at the series and let me know your comments. We need to find
> a good place to add the document the generic irqdomain-map bindings.

How about the obvious
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt.

I'd really like to see a respin of this by -rc1.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...