[PATCH] v6 ath10k: add LED and GPIO controlling support for various chipsets

[Julian Calaby]

Hi Sebastian,

On Mon, Feb 19, 2018 at 3:49 AM,  <s.gottschall at dd-wrt.com> wrote:
> From: Sebastian Gottschall <s.gottschall at newmedia-net.de>
>
> Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based chipsets with on chipset connected led's
> using WMI Firmware API.
> The LED device will get available named as "ath10k-phyX" at sysfs and can be controlled with various triggers.
> adds also debugfs interface for gpio control.

You should put the "v6" in the subject _inside_ the "[PATCH]" See the
"-v" option in git format-patch.

> v2  add correct gpio count per chipset and remove IPQ4019 support since this chipset does not make use of specific gpios)
> v5  fix compiling without LED_CLASS and GPIOLIB support, fix also error by kbuild test robot which does not occur in standard builds. curious
> v6  correct return values and fix comment style

The revisions should be between the first "---" and the diffstat.

> Signed-off-by: Sebastian Gottschall <s.gottschall at dd-wrt.com>
> ---

I.e. here.

>  drivers/net/wireless/ath/ath10k/core.c    | 183 +++++++++++++++++++++++++++++-
>  drivers/net/wireless/ath/ath10k/core.h    |  20 +++-
>  drivers/net/wireless/ath/ath10k/debug.c   | 146 ++++++++++++++++++++++++
>  drivers/net/wireless/ath/ath10k/hw.h      |   2 +
>  drivers/net/wireless/ath/ath10k/mac.c     |   6 +
>  drivers/net/wireless/ath/ath10k/wmi-ops.h |  36 +++++-
>  drivers/net/wireless/ath/ath10k/wmi-tlv.c |  65 +++++++++++
>  drivers/net/wireless/ath/ath10k/wmi.c     |  46 ++++++++
>  drivers/net/wireless/ath/ath10k/wmi.h     |  36 ++++++
>  9 files changed, 536 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
> index f3ec13b80b20..5ecda9242d33 100644
> --- a/drivers/net/wireless/ath/ath10k/core.c
> +++ b/drivers/net/wireless/ath/ath10k/core.c
> @@ -2132,12 +2148,148 @@ static int ath10k_core_reset_rx_filter(struct ath10k *ar)
> +/* register GPIO chip */
> +static int ath10k_register_gpio_chip(struct ath10k *ar)
> +{
> +       struct ath10k_gpiocontrol *gpio;
> +       gpio = kzalloc(sizeof(struct ath10k_gpiocontrol), GFP_KERNEL);
> +       if (!gpio) {
> +               return -ENOMEM;
> +       }
> +
> +       snprintf(gpio->label, sizeof(gpio->label), "ath10k-%s",
> +                wiphy_name(ar->hw->wiphy));
> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,5,0)
> +       gpio->gchip.parent = ar->dev;
> +#else
> +       gpio->gchip.dev = ar->dev;
> +#endif

This is why the kbuild test bot is complaining: LINUX_VERSION_CODE is
not used in upstream code - it'll only ever be built on the current
version or newer and if there are any API changes they'll be handled
for you.

("But what about backporting?" if this code is backported, it'll most
likely be through the backports project and will be handled using this
script: https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/tree/patches/0002-gpio-parent.cocci
)

Removing these blocks will make the kbuild bot happy. Also,
checkpatch.pl should have complained about this.

Thanks,

-- 
Julian Calaby

Email: julian.calaby at gmail.com
Profile: http://www.google.com/profiles/julian.calaby/