public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linusw@kernel.org>
Cc: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
	"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>,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com, linux-gpio@vger.kernel.org,
	"Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Subject: Re: [PATCH v5] wifi: ath9k: Obtain system GPIOS from descriptors
Date: Mon, 16 Mar 2026 23:16:13 +0200	[thread overview]
Message-ID: <abhzHdy5hByLnPFu@ashevche-desk.local> (raw)
In-Reply-To: <20260316-descriptors-wireless-v5-1-3f791c6b0cba@kernel.org>

On Mon, Mar 16, 2026 at 09:56:58PM +0100, Linus Walleij wrote:
> 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.

...

> Changes in v5:
> - Collect Bartosz ACK
> - Switch Kalle->Jeff as maintainer.
> - Link to v4: https://lore.kernel.org/r/20260313-descriptors-wireless-v4-1-07ab47c89a98@kernel.org

Seems you forgot to address the LKP report.

> +static int ath79_gpio_register_wifi_descriptors(struct device *dev,
> +						const char *label)
> +{

Should be return SOMETHING; here.

> +}
> +#endif


-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-03-16 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 20:56 [PATCH v5] wifi: ath9k: Obtain system GPIOS from descriptors Linus Walleij
2026-03-16 21:16 ` Andy Shevchenko [this message]

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=abhzHdy5hByLnPFu@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=albeu@free.fr \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brgl@bgdev.pl \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=kernel@kempniu.pl \
    --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