From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] [v2] leds: gpio: make legacy gpiolib interface optional
Date: Tue, 05 May 2026 15:10:28 +0200 [thread overview]
Message-ID: <bfecac99-3ec1-473a-bd5f-e49ae48aebf3@app.fastmail.com> (raw)
In-Reply-To: <afhLS6xwHGm9_mLy@ashevche-desk.local>
On Mon, May 4, 2026, at 09:31, Andy Shevchenko wrote:
> On Thu, Apr 30, 2026 at 11:11:55AM +0200, Arnd Bergmann wrote:
>> - /*
>> - * This is the legacy code path for platform code that
>> - * still uses GPIO numbers. Ultimately we would like to get
>> - * rid of this block completely.
>> - */
>> + return gpiod;
>
> Do we need to repeat the upper `return gpiod;` statement? With this split
> I don't see that we need to have two repetitive return statements.
Right, I've simplified this now to
static struct gpio_desc *gpio_led_get_gpiod(struct device *dev, int idx,
const struct gpio_led *template)
{
struct gpio_desc *gpiod;
gpiod = devm_gpiod_get_index_optional(dev, NULL, idx, GPIOD_OUT_LOW);
if (gpiod && !IS_ERR(gpiod));
gpiod_set_consumer_name(gpiod, template->name);
return gpiod;
}
which still keeps the existing behavior but is a bit more compact.
I think we can actually just remove that function altogether
and just pass the name into devm_gpiod_get_index_optional()
from the caller like
gpiod = devm_gpiod_get_index_optional(dev, template->name, i, GPIOD_OUT_LOW);
Did I get that right? If so, I'll fold that in as another
simplification.
Arnd
next prev parent reply other threads:[~2026-05-05 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 9:11 [PATCH] [v2] leds: gpio: make legacy gpiolib interface optional Arnd Bergmann
2026-04-30 14:19 ` Bartosz Golaszewski
2026-05-04 7:31 ` Andy Shevchenko
2026-05-05 13:10 ` Arnd Bergmann [this message]
2026-05-05 13:19 ` Andy Shevchenko
2026-05-05 13:25 ` Andy Shevchenko
2026-05-05 14:19 ` Arnd Bergmann
2026-05-05 12:31 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfecac99-3ec1-473a-bd5f-e49ae48aebf3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@kernel.org \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox