From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: "Linus Walleij" <linusw@kernel.org>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, linux-gpio@vger.kernel.org,
"Kalle Valo" <kvalo@kernel.org>, "Arnd Bergmann" <arnd@arndb.de>,
"Alban Bedel" <albeu@free.fr>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Michał Kępień" <kernel@kempniu.pl>
Subject: Re: [PATCH v4] wifi: ath9k: Obtain system GPIOS from descriptors
Date: Mon, 16 Mar 2026 11:29:13 +0200 [thread overview]
Message-ID: <abfNaRH10hnXug4l@ashevche-desk.local> (raw)
In-Reply-To: <CAMRc=MdJXhXyid1a4ycmKv6nwOf3FYd=rFEaBqQ7k3SFq_j4FQ@mail.gmail.com>
On Mon, Mar 16, 2026 at 05:09:22AM -0400, Bartosz Golaszewski wrote:
> On Fri, 13 Mar 2026 22:53:43 +0100, Linus Walleij <linusw@kernel.org> said:
> > The ath9k has an odd use of system-wide GPIOs: if the chip
> > does not have internal GPIO capability, it will try to obtain a
> > GPIO line from the system GPIO controller:
> >
> > if (BIT(gpio) & ah->caps.gpio_mask)
> > ath9k_hw_gpio_cfg_wmac(...);
> > else if (AR_SREV_SOC(ah))
> > ath9k_hw_gpio_cfg_soc(ah, gpio, out, label);
> >
> > Where ath9k_hw_gpio_cfg_soc() will attempt to issue
> > gpio_request_one() passing the local GPIO number of the controller
> > (0..31) to gpio_request_one().
> >
> > This is somewhat peculiar and possibly even dangerous: there is
> > nowadays no guarantee of the numbering of these system-wide
> > GPIOs, and assuming that GPIO 0..31 as used by ath9k would
> > correspond to GPIOs 0..31 on the system as a whole seems a bit
> > wild.
> >
> > Register all 32 GPIOs at index 0..31 directly in the ATH79K
> > GPIO driver and associate with the NULL device (making them
> > widely available) if and only if we are probing ATH79K wifi
> > from the AHB bus (used for SoCs). We obtain these offsets from
> > the NULL device if necessary.
> >
> > These GPIOs should ideally be defined in the device tree
> > instead, but we have no control over that for the legacy
> > code path.
> >
> > Testcompiled with the ath79 defconfig.
> >
> > Reported-by: Michał Kępień <kernel@kempniu.pl>
> > Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Linus Walleij <linusw@kernel.org>
> > ---
> > This patch set is a long standing attempt to get rid of the global
> > GPIO numbers from the ath9k Wireless driver.
> >
> > Maybe Kalle can merge this to the Wireless tree if we agree on this
> > hack solution.
> >
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > Changes in v4:
> > - Fix review comments from Andy.
> > - Collect ACKs.
>
> I think this did not work. :)
It's just extra SoB where it's not needed, but the tags are collected in
the proper commit message.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 21:53 [PATCH v4] wifi: ath9k: Obtain system GPIOS from descriptors Linus Walleij
2026-03-16 9:09 ` Bartosz Golaszewski
2026-03-16 9:29 ` Andy Shevchenko [this message]
2026-03-16 20:02 ` Jeff Johnson
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=abfNaRH10hnXug4l@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=albeu@free.fr \
--cc=arnd@arndb.de \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brgl@bgdev.pl \
--cc=brgl@kernel.org \
--cc=kernel@kempniu.pl \
--cc=kvalo@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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