[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <789b7ca0-80c5-449a-99eb-8c05b5380245@app.fastmail.com>
Date: Thu, 01 Feb 2024 15:00:05 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>
Cc: "Linus Walleij" <linus.walleij@...aro.org>,
Toke Høiland-Jørgensen <toke@...e.dk>,
"Kalle Valo" <kvalo@...nel.org>, "Arend van Spriel" <aspriel@...il.com>,
"Franky Lin" <franky.lin@...adcom.com>,
"Hante Meuleman" <hante.meuleman@...adcom.com>, "Lee Jones" <lee@...nel.org>,
"Brian Norris" <briannorris@...omium.org>,
"Srinivasan Raju" <srini.raju@...elifi.com>, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org, brcm80211-dev-list.pdl@...adcom.com
Subject: Re: [PATCH 1/6] wifi: ath9k: Obtain system GPIOS from descriptors
On Thu, Feb 1, 2024, at 14:17, Andy Shevchenko wrote:
> On Thu, Feb 01, 2024 at 01:20:16PM +0100, Arnd Bergmann wrote:
>> On Wed, Jan 31, 2024, at 23:37, Linus Walleij wrote:
>
>> + } else if (ah->led_pin < 0) {
>
> ...
>
>> + if (sc->sc_ah->led_gpio)
>
> Dup check
I don't know what you mean here. To explain what I'm
trying to do: The idea is that the LED is always backed
by either gpiolib or the internal gpio controller on
the PCI device. This means every access to an LED must
be guarded with
if (gpiodesc)
gpio_*(gpiodesc);
else
internal(ah);
We could probably go a little further in the cleanup and
throw out the gpiolib path entirely, instead relying
on the existing leds-gpio driver. Since there are currently
no upstream users of the gpiolib path, that would likely
lead to cleaner code but require more changes to any
out-of-tree users that rely on the platform_data to
pass the GPIOs today.
Arnd
Powered by blists - more mailing lists