linux-kernel - Re: [PATCH 00/12] 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]

Message-ID: <20191115162050.GE18786@codeaurora.org>
Date:   Fri, 15 Nov 2019 09:20:50 -0700
From:   Lina Iyer <ilina@...eaurora.org>
To:     Marc Zyngier <maz@...nel.org>
Cc:     swboyd@...omium.org, linus.walleij@...aro.org,
        bjorn.andersson@...aro.org, evgreen@...omium.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        mkshah@...eaurora.org, linux-gpio@...r.kernel.org,
        agross@...nel.org, dianders@...omium.org
Subject: Re: [PATCH 00/12] Support wakeup capable GPIOs

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