[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220906210811.5kzdq66eeeauk2d3@pali>
Date: Tue, 6 Sep 2022 23:08:11 +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 1/2] PCI: histb: switch to using gpiod API
On Tuesday 06 September 2022 13:43:00 Dmitry Torokhov wrote:
> + ret = gpiod_set_consumer_name(hipcie->reset_gpio,
> + "PCIe device power control");
Just unrelated thing, I know it was there before, but I saw it just now
and have to comment it: This is absolute nonsense name. "reset-gpios"
device tree property specifies PERST# signal pin (PciE ReSeT) as defined
in PCIe CEM (Card ElectroMagnetic) specification and it has absolute
nothing with PCIe power control.
My suggestion for maintainers would be to remove this critic name at
all as it would just mislead other people reading that code.
> + if (ret) {
> + dev_err(dev, "unable to set reset gpio name: %d\n", ret);
> + return ret;
> }
Powered by blists - more mailing lists