[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZ4A3Lw2U+_jXfbuXJFhpesi3SzNN1Codqxi4sLNu5zPw@mail.gmail.com>
Date: Tue, 10 Aug 2021 15:34:39 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Andrew Jeffery <andrew@...id.au>
Cc: Linux LED Subsystem <linux-leds@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Cédric Le Goater <clg@...d.org>,
Rob Herring <robh+dt@...nel.org>,
Joel Stanley <joel@....id.au>, Pavel Machek <pavel@....cz>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/6] pinctrl: Add pinctrl_gpio_as_pin()
On Fri, Jul 23, 2021 at 9:59 AM Andrew Jeffery <andrew@...id.au> wrote:
> Allow gpiochips to map the GPIO numberspace onto a pin numberspace when
> the register layout for GPIO control is implemented in terms of the
> pin numberspace.
>
> This requirement sounds kind of strange, but the patch is driven by
> trying to resolve a bug in the leds-pca955x driver where this mapping is
> not correctly performed.
>
> Signed-off-by: Andrew Jeffery <andrew@...id.au>
(...)
Hm this looks a bit strange...
> +int pinctrl_gpio_as_pin(struct pinctrl_dev *pctldev, unsigned int gpio)
This is not a good name for this function. Try to come up with
a name that says exactly what the function does.
E.g. "apple pear as apple slice" isn't very helpful, the use case for
this is really hard to understand.
> +EXPORT_SYMBOL_GPL(pinctrl_find_gpio_range_from_pin);
This looks completely wrong.
Yours,
Linus Walleij
Powered by blists - more mailing lists