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
| ||
|
Date: Tue, 6 Sep 2022 23:42:15 +0200 From: Pali Rohár <pali@...nel.org> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: Shawn Guo <shawn.guo@...aro.org>, Lorenzo Pieralisi <lpieralisi@...nel.org>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, Bjorn Helgaas <bhelgaas@...gle.com>, Rob Herring <robh@...nel.org>, Krzysztof Wilczyński <kw@...ux.com>, Linus Walleij <linus.walleij@...aro.org>, Bartosz Golaszewski <brgl@...ev.pl>, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] PCI: mvebu: switch to using gpiod API On Tuesday 06 September 2022 14:40:15 Dmitry Torokhov wrote: > On Tue, Sep 06, 2022 at 02:26:32PM -0700, Dmitry Torokhov wrote: > > Hi Pali, > > > > On Tue, Sep 06, 2022 at 11:16:28PM +0200, Pali Rohár wrote: > > > Hello! > > > > > > On Tuesday 06 September 2022 13:43:01 Dmitry Torokhov wrote: > > > > This patch switches the driver away from legacy gpio/of_gpio API to > > > > gpiod API, and removes use of of_get_named_gpio_flags() which I want to > > > > make private to gpiolib. > > > > > > There are many pending pci-mvebu.c patches waiting for review and merge, > > > so I would suggest to wait until all other mvebu patches are processed > > > and then process this one... longer waiting period :-( > > > > OK, it is not super urgent. OTOH it is a very simple patch :) > > By the way, do the pending patches address soft-leaking of reset GPIO > when the driver fails to acquire clock for a port (I called it > soft-leaking since devm will free it on unbind)? I think no, because there is not any patch related to GPIO reset.
Powered by blists - more mailing lists