ath10k: add LED and GPIO controlling support for various chipsets
Subsystems (5)
PATCH v14 1/1 ath10k: add LED and GPIO controlling support for various chipsets
From: Sebastian Gottschall <[email protected]>
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.
---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.
A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Changes v14:
- Fixed SPDX missing tag in leds.c and leds.h
- Fixes discrepancy between From: and Signed-off-by:
- Improve and rework kconfig description
- Improve commit description
- Add very old tested-by tag
(v13 changelog from Kavlo from 2018 [1])
* only compile tested!
* fix all checkpatch warnings
* fix commit log
* sizeof(struct ath10k_gpiocontrol) -> sizeof(*gpio)
* unsigned -> unsigned int
* remove GPIOLIB code, that should be added in a separate patch
* rename gpio.c to leds.c
* add leds.h
* rename some functions:
ath10k_attach_led() -> ath10k_leds_register() ath10k_unregister_led() -> ath10k_leds_unregister() ath10k_reset_led_pin() -> ath10k_leds_start()
* call ath10k_leds_unregister() before ath10k_thermal_unregister() to preserve ordering
* call ath10k_leds_start() only from ath10k_core_start() and not from mac.c
* rename struct ath10k_gpiocontrol as anonymous function under struct ath10k::leds, no need for memory allocation
* merge ath10k_add_led() to ath10k_attach_led(), which is it's only caller
* remove #if IS_ENABLED() checks from most of places, memory savings from those were not worth it
* Kconfig help text improvement and move it lower in the menu, also don't enable it by default
* switch to set_brightness_blocking() so that the callback can sleep, then no need to use ath10k_wmi_cmd_send_nowait() and can take mutex to access ar->state
* don't touch ath10k_wmi_pdev_get_temperature()
* as QCA6174/QCA9377 are not (yet) supported don't add the command to WMI-TLV interface
* remove debugfs interface, that should be added in another patch
* cleanup includes
(old changelog from really old patch v12 from 2018 [1]) v12 fix warning
v11 make register_gpio_chip static. advise by krobot v10 compile fix if gpiolib isnt included
v9 move led and led code to separate sourcefile (gpio.c) v8 fix various code design issues reported by reviewers v7 fix ath10k_unregister_led for compiling without LED_CLASS v6 correct return values and fix comment style v5 fix compiling without LED_CLASS and GPIOLIB support, fix also error by kbuild test robot which does not occur in standard builds. curious v2 add correct gpio count per chipset and remove IPQ4019 support since this chipset does not make use of specific gpios)
[1] https://patchwork.kernel.org/project/ath10k/patch/[email protected]/
[2] https://patchwork.kernel.org/project/ath10k/patch/[email protected]/
drivers/net/wireless/ath/ath10k/Kconfig | 17 +++++ drivers/net/wireless/ath/ath10k/Makefile | 1 + drivers/net/wireless/ath/ath10k/core.c | 21 ++++++ drivers/net/wireless/ath/ath10k/core.h | 8 ++ drivers/net/wireless/ath/ath10k/hw.h | 1 + drivers/net/wireless/ath/ath10k/leds.c | 92 +++++++++++++++++++++++ drivers/net/wireless/ath/ath10k/leds.h | 34 +++++++++ drivers/net/wireless/ath/ath10k/mac.c | 1 + drivers/net/wireless/ath/ath10k/wmi-ops.h | 32 ++++++++ drivers/net/wireless/ath/ath10k/wmi-tlv.c | 2 + drivers/net/wireless/ath/ath10k/wmi.c | 54 +++++++++++++ drivers/net/wireless/ath/ath10k/wmi.h | 35 +++++++++ 12 files changed, 298 insertions(+) create mode 100644 drivers/net/wireless/ath/ath10k/leds.c create mode 100644 drivers/net/wireless/ath/ath10k/leds.h
drivers/net/wireless/ath/ath10k/Kconfig +17 -0
@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDS + default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card. + config ATH10K_SPECTRAL bool "Atheros ath10k spectral scan support" depends on ATH10K_DEBUGFS
drivers/net/wireless/ath/ath10k/Makefile +1 -0
@@ -19,6 +19,7 @@ ath10k_core-$(CONFIG_ATH10K_SPECTRAL) += spectral.o ath10k_core-$(CONFIG_NL80211_TESTMODE) += testmode.o ath10k_core-$(CONFIG_ATH10K_TRACING) += trace.o ath10k_core-$(CONFIG_THERMAL) += thermal.o +ath10k_core-$(CONFIG_ATH10K_LEDS) += leds.o ath10k_core-$(CONFIG_MAC80211_DEBUGFS) += debugfs_sta.o ath10k_core-$(CONFIG_PM) += wow.o ath10k_core-$(CONFIG_DEV_COREDUMP) += coredump.o
drivers/net/wireless/ath/ath10k/core.c +21 -0
@@ -26,6 +26,7 @@#include "testmode.h" #include "wmi-ops.h" #include "coredump.h" +#include "leds.h" unsigned int ath10k_debug_mask;EXPORT_SYMBOL (ath10k_debug_mask);
@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0", + .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,
@@ -146,6 +148,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA9887_1_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca9887 hw1.0", + .led_pin = 1, .patch_load_addr = QCA9887_HW_1_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,
@@ -387,6 +390,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA99X0_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca99x0 hw2.0", + .led_pin = 17, .patch_load_addr = QCA99X0_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .otp_exe_param = 0x00000700,
@@ -433,6 +437,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA9984_1_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca9984/qca9994 hw1.0", + .led_pin = 17, .patch_load_addr = QCA9984_HW_1_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_EACH,
@@ -486,6 +491,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA9888_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca9888 hw2.0", + .led_pin = 17, .patch_load_addr = QCA9888_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_EACH,
@@ -3222,6 +3228,10 @@ int ath10k_core_start(struct ath10k *ar, enum ath10k_firmware_mode mode, goto err_hif_stop; } + status =ath10k_leds_start (ar); +if (status) + goto err_hif_stop; +return 0 ; err_hif_stop:
@@ -3480,9 +3490,18 @@ static void ath10k_core_register_work(struct work_struct *work) goto err_spectral_destroy; } + status =ath10k_leds_register (ar); +if (status) { +ath10k_err (ar,"could not register leds: %d\n" , + status); + goto err_thermal_unregister; + } +set_bit (ATH10K_FLAG_CORE_REGISTERED , &ar->dev_flags);return ; +err_thermal_unregister: +ath10k_thermal_unregister (ar); err_spectral_destroy:ath10k_spectral_destroy (ar); err_debug_destroy:
@@ -3518,6 +3537,8 @@ void ath10k_core_unregister(struct ath10k *ar)if (!test_bit (ATH10K_FLAG_CORE_REGISTERED , &ar->dev_flags))return ; +ath10k_leds_unregister (ar); +ath10k_thermal_unregister (ar);/* Stop spectral before unregistering from mac80211 to remove the * relayfs debugfs file cleanly. Otherwise the parent debugfs tree
drivers/net/wireless/ath/ath10k/core.h +8 -0
@@ -14,6 +14,7 @@#include <linux/pci.h> #include <linux/uuid.h> #include <linux/time.h> +#include <linux/leds.h> #include "htt.h" #include "htc.h"
@@ -1255,6 +1256,13 @@ struct ath10k {bool utf_monitor; } testmode; +struct { +struct gpio_led wifi_led; +struct led_classdev cdev; +char label[48 ]; +u32 gpio_state_pin; + } leds; +struct {/* protected by data_lock */ u32 rx_crc_err_drop;
drivers/net/wireless/ath/ath10k/hw.h +1 -0
@@ -519,6 +519,7 @@ struct ath10k_hw_params {const char *name;u32 patch_load_addr;int uart_pin; +int led_pin;u32 otp_exe_param;/* Type of hw cycle counter wraparound logic, for more info
drivers/net/wireless/ath/ath10k/leds.c new file +92 -0
92 lines not on this page · raw message
drivers/net/wireless/ath/ath10k/leds.h new file +34 -0
@@ -0,0 +1,34 @@ +/* SPDX-License-Identifier: ISC */ +/* +* Copyright (c) 2005-2011 Atheros Communications Inc. +* Copyright (c) 2011-2017 Qualcomm Atheros, Inc. +* Copyright (c) 2018 Sebastian Gottschall <[email protected]> +* Copyright (c) 2018-2023, The Linux Foundation. All rights reserved. +*/ + +#ifndef _LEDS_H_ +#define _LEDS_H_ + +#include "core.h" + +#ifdef CONFIG_ATH10K_LEDS +void ath10k_leds_unregister (struct ath10k *ar); +int ath10k_leds_start (struct ath10k *ar); +int ath10k_leds_register (struct ath10k *ar); +#else +static inline void ath10k_leds_unregister (struct ath10k *ar) +{ +} + +static inline int ath10k_leds_start (struct ath10k *ar) +{ +return 0 ; +} + +static inline int ath10k_leds_register (struct ath10k *ar) +{ +return 0 ; +} + +#endif +#endif /* _LEDS_H_ */
drivers/net/wireless/ath/ath10k/mac.c +1 -0
@@ -24,6 +24,7 @@#include "wmi-tlv.h" #include "wmi-ops.h" #include "wow.h" +#include "leds.h" /*********/ /* Rates */
drivers/net/wireless/ath/ath10k/wmi-ops.h +32 -0
@@ -226,7 +226,10 @@ struct wmi_ops { const struct wmi_bb_timing_cfg_arg *arg);struct sk_buff *(*gen_per_peer_per_tid_cfg)(struct ath10k *ar,const struct wmi_per_peer_per_tid_cfg_arg *arg); +struct sk_buff *(*gen_gpio_config)(struct ath10k *ar,u32 gpio_num, +u32 input,u32 pull_type,u32 intr_mode); +struct sk_buff *(*gen_gpio_output)(struct ath10k *ar,u32 gpio_num,u32 set); };int ath10k_wmi_cmd_send (struct ath10k *ar,struct sk_buff *skb,u32 cmd_id);
@@ -1122,6 +1125,35 @@ ath10k_wmi_force_fw_hang(struct ath10k *ar,return ath10k_wmi_cmd_send (ar, skb, ar->wmi.cmd->force_fw_hang_cmdid); } +static inline int ath10k_wmi_gpio_config (struct ath10k *ar,u32 gpio_num, +u32 input,u32 pull_type,u32 intr_mode) +{ +struct sk_buff *skb; + +if (!ar->wmi.ops->gen_gpio_config) +return -EOPNOTSUPP ; + + skb = ar->wmi.ops->gen_gpio_config (ar, gpio_num, input, pull_type, intr_mode); +if (IS_ERR (skb)) +return PTR_ERR (skb); + +return ath10k_wmi_cmd_send (ar, skb, ar->wmi.cmd->gpio_config_cmdid); +} + +static inline int ath10k_wmi_gpio_output (struct ath10k *ar,u32 gpio_num,u32 set) +{ +struct sk_buff *skb; + +if (!ar->wmi.ops->gen_gpio_config) +return -EOPNOTSUPP ; + + skb = ar->wmi.ops->gen_gpio_output (ar, gpio_num, set); +if (IS_ERR (skb)) +return PTR_ERR (skb); + +return ath10k_wmi_cmd_send (ar, skb, ar->wmi.cmd->gpio_output_cmdid); +} +static inline int ath10k_wmi_dbglog_cfg (struct ath10k *ar,u64 module_enable,u32 log_level) {
drivers/net/wireless/ath/ath10k/wmi-tlv.c +2 -0
@@ -4601,6 +4601,8 @@ static const struct wmi_ops wmi_tlv_ops = { .gen_echo = ath10k_wmi_tlv_op_gen_echo, .gen_vdev_spectral_conf = ath10k_wmi_tlv_op_gen_vdev_spectral_conf, .gen_vdev_spectral_enable = ath10k_wmi_tlv_op_gen_vdev_spectral_enable, +/* .gen_gpio_config not implemented */ +/* .gen_gpio_output not implemented */ };static const struct wmi_peer_flags_map wmi_tlv_peer_flags_map = {
drivers/net/wireless/ath/ath10k/wmi.c +54 -0
90 lines not on this page · raw message
drivers/net/wireless/ath/ath10k/wmi.h +35 -0
@@ -3030,6 +3030,41 @@ enum wmi_10_4_feature_mask { }; +/* WMI_GPIO_CONFIG_CMDID */ +enum { +WMI_GPIO_PULL_NONE , +WMI_GPIO_PULL_UP , +WMI_GPIO_PULL_DOWN , +}; + +enum { +WMI_GPIO_INTTYPE_DISABLE , +WMI_GPIO_INTTYPE_RISING_EDGE , +WMI_GPIO_INTTYPE_FALLING_EDGE , +WMI_GPIO_INTTYPE_BOTH_EDGE , +WMI_GPIO_INTTYPE_LEVEL_LOW , +WMI_GPIO_INTTYPE_LEVEL_HIGH +}; + +/* WMI_GPIO_CONFIG_CMDID */ +struct wmi_gpio_config_cmd { +__le32 gpio_num;/* GPIO number to be setup */ +__le32 input;/* 0 - Output/ 1 - Input */ +__le32 pull_type;/* Pull type defined above */ +__le32 intr_mode;/* Interrupt mode defined above (Input) */ +} __packed; + +/* WMI_GPIO_OUTPUT_CMDID */ +struct wmi_gpio_output_cmd { +__le32 gpio_num;/* GPIO number to be setup */ +__le32 set;/* Set the GPIO pin*/ +} __packed; + +/* WMI_GPIO_INPUT_EVENTID */ +struct wmi_gpio_input_event { +__le32 gpio_num;/* GPIO number which changed state */ +} __packed; +struct wmi_ext_resource_config_10_4_cmd {/* contains enum wmi_host_platform_type */ __le32 host_platform_config;
Signature · 1 line
2.40.1
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.
Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDS
drivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.
I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config ATH10K_LEDS
bool depends on ATH10K depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default y
This follows what mt76 does:
config MT76_LEDS
bool depends on MT76_CORE depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default y
drivers/net/wireless/ath/ath10k/Kconfig static const struct ath10k_hw_params ath10k_hw_params_list[] = { · line 72
Quoted 8 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0", + .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,
I prefer following the field order from struct ath10k_hw_params declaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy));
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP; + + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;
But what to do with this FIXME?
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Quoted 38 lines · Kalle Valo
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.
Quoted 33 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDSbool depends on ATH10K depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default y
Quoted 8 lines
This follows what mt76 does:
config
MT76_LEDSbool depends on MT76_CORE depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default y
I remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 4 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0",
Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig static const struct ath10k_hw_params ath10k_hw_params_list[] = { · line 72
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0+ .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.
Thanks for the change, np for me.
Quoted 14 lines
Quoted 14 lines
drivers/net/wireless/ath/ath10k/Kconfig +14
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP;
Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 6 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the default_trigger to the mac80211 tpt.
We might got both confused by default_trigger and default_state. default_trigger is actually never set and is NULL (actually it's 0)
We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the default_trigger and I will send a follow-up patch to this adding DT support by using led_classdev_register_ext and defining init_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)
Also ideally I will also send a patch for default_state following standard LED implementation. (to set default_state in DT)
I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
Signature · 1 line
Ansuel
Quoted 157 lines · Christian Marangi
Quoted 38 lines · Kalle Valo
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.Quoted 33 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDSbool depends on ATH10K depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yQuoted 8 lines
This follows what mt76 does:
config
MT76_LEDSbool depends on MT76_CORE depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default yI remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 4 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0",Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig static const struct ath10k_hw_params ath10k_hw_params_list[] = { · line 72
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0+ .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.Thanks for the change, np for me.
Quoted 14 lines
Quoted 14 lines
drivers/net/wireless/ath/ath10k/Kconfig +14
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP;Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 6 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the
default_triggerto the mac80211 tpt.We might got both confused by
default_triggeranddefault_state.default_triggeris actually never set and is NULL (actually it's 0)We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the
default_triggerand I will send a follow-up patch to this adding DT support by usingled_classdev_register_extand defininginit_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)
Quoted 6 lines
Also ideally I will also send a patch for
default_statefollowing standard LED implementation. (to setdefault_statein DT)I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
If you want to check out I attached the 2 patch (one dt-bindings and the one for the code) that I will submit when this will be merged (the change is with the assumption that the FIXME line is dropped)
Tested and works correctly with my use case of wifi card attached with pcie. This implementation permits to declare the default trigger in DT instead of hardcoding.
Signature · 1 line
Ansuel
From d1e1a93fbfcbe711659f7ed7480633bf4d382377 Mon Sep 17 00:00:00 2001
From: Christian Marangi <[email protected]>
Date: Fri, 16 Jun 2023 22:58:20 +0200
Subject: [PATCH 1/3] dt-bindings: net: wireless: qcom: ath10k: Document LED
node support
Ath10k based wifi cards can support a LED connected via GPIO internally. The LED is configured used WMI call. Document support for the LED node controllable standard LED bindings.
While at it adds also an example for PCIe where LED is commonly connected and used on routers.
--- .../bindings/net/wireless/qcom,ath10k.yaml | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+)
Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml +42 -0
@@ -157,6 +157,11 @@ properties: vdd-3.3-ch1-supply: description: Secondary Wi-Fi antenna supply + led: + $ref: /schemas/leds/common.yaml# + + unevaluatedProperties: false + required: - compatible - reg
@@ -258,6 +263,43 @@ allOf: - interrupts examples: + # PCIe + - | + #include <dt-bindings/leds/common.h> + + pci@1b500000 { + reg = <0x1b500000 0x1000 + 0x1b502000 0x80 + 0x1b600000 0x100 + 0x0ff00000 0x100000>; + device_type = "pci"; + #address-cells = <3>; + #size-cells = <2>; + + ranges = <0x81000000 0x0 0x00000000 0x0fe00000 0x0 0x00010000 /* I/O */ + 0x82000000 0x0 0x08000000 0x08000000 0x0 0x07e00000>; /* MEM */ + + /* ... */ + + bridge@0,0 { + reg = <0x00000000 0 0 0 0>; + #address-cells = <3>; + #size-cells = <2>; + ranges; + + wifi@1,0 { + compatible = "qcom,ath10k"; + reg = <0x00010000 0 0 0 0>; + + led { + default-state = "keep"; + color = <LED_COLOR_ID_WHITE>; + function = LED_FUNCTION_WLAN; + }; + }; + }; + }; + # SNoC - | #include <dt-bindings/clock/qcom,rpmcc.h>
Signature · 1 line
2.40.1
From 1e867963acbc7dd744fb07949928bc493244ee81 Mon Sep 17 00:00:00 2001
From: Christian Marangi <[email protected]>
Date: Fri, 16 Jun 2023 23:22:28 +0200
Subject: [PATCH 2/3] wifi: ath10k: start LED with the previous defined cdev
brightness
In preparation for DT support for LED, change ath10k_leds_start to init the LED to the previous defined cdev brightness.
The LED is set to OFF by default since we can't understand the previous state of the LED due to a limitation in the WMI calls exposed by the fw.
--- drivers/net/wireless/ath/ath10k/leds.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/wireless/ath/ath10k/leds.c +4 -1
@@ -48,7 +48,8 @@ int ath10k_leds_start(struct ath10k *ar)*/ ath10k_wmi_gpio_config (ar, ar->hw_params.led_pin,0 ,WMI_GPIO_PULL_NONE ,WMI_GPIO_INTTYPE_DISABLE ); -ath10k_wmi_gpio_output (ar, ar->hw_params.led_pin,1 ); +ath10k_wmi_gpio_output (ar, ar->hw_params.led_pin, + ar->leds.cdev.brightness ^ ar->leds.wifi_led.active_low);return 0 ; }
@@ -69,6 +70,8 @@ int ath10k_leds_register(struct ath10k *ar) ar->leds.wifi_led.default_state =LEDS_GPIO_DEFSTATE_KEEP ; ar->leds.cdev.name = ar->leds.label; +/* By default LED is set OFF */ + ar->leds.cdev.brightness =0 ; ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; ret =led_classdev_register (wiphy_dev (ar->hw->wiphy), &ar->leds.cdev);
Signature · 1 line
2.40.1
From 9437101f4ab7e06118be83180be6c8f471c1f804 Mon Sep 17 00:00:00 2001
From: Christian Marangi <[email protected]>
Date: Fri, 16 Jun 2023 23:02:26 +0200
Subject: [PATCH 3/3] wifi: ath10k: add DT support for LED definition
If supported, the LED definition for the ath10k wifi card is all hardcoded with static names, triggers and default-state.
Add DT support for the supported LED to permit custom names, define a default state and a default trigger.
To identify these special LED, devname_mandatory is set to true and each LED is prefixed with ath10k- and the wireless phy name.
The non-DT implementation is still supported and DT definition is not mandatory.
--- drivers/net/wireless/ath/ath10k/leds.c | 38 +++++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-)
drivers/net/wireless/ath/ath10k/leds.c +37 -1
@@ -54,8 +54,39 @@ int ath10k_leds_start(struct ath10k *ar)return 0 ; } +static int ath10k_leds_of_init (struct ath10k *ar,struct led_init_data *init_data) +{ +struct fwnode_handle *led =NULL ; +enum led_default_state state; + + led =device_get_named_child_node (ar->dev,"led" ); +if (!led) +return -ENOENT ; + +/* LED will be init on ath10k core start. */ + state =led_init_default_state_get (led); +switch (state) { +case LEDS_DEFSTATE_ON : + ar->leds.cdev.brightness =1 ; +break ; +/* KEEP will start the LED to OFF by default */ +case LEDS_DEFSTATE_KEEP : +default : + ar->leds.cdev.brightness =0 ; + } + + init_data->default_label ="wifi" ; + init_data->fwnode = led; + init_data->devname_mandatory = true; + init_data->devicename = ar->leds.label; + +return 0 ; +} +int ath10k_leds_register (struct ath10k *ar) { +struct led_init_data *init_data_ptr =NULL ; +struct led_init_data init_data = { };int ret;if (ar->hw_params.led_pin ==0 )
@@ -74,7 +105,12 @@ int ath10k_leds_register(struct ath10k *ar) ar->leds.cdev.brightness =0 ; ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; - ret =led_classdev_register (wiphy_dev (ar->hw->wiphy), &ar->leds.cdev); +/* Support DT defined led. init_data_ptr is NULL if DT is not supported. */ +if (!ath10k_leds_of_init (ar, &init_data)) + init_data_ptr = &init_data; + + ret =led_classdev_register_ext (wiphy_dev (ar->hw->wiphy), &ar->leds.cdev, + init_data_ptr);if (ret)return ret;
Signature · 1 line
2.40.1
Il giorno sab 17 giu 2023 alle ore 19:28 Christian Marangi <[email protected]> ha scritto:
Quoted 166 lines · Christian Marangi
Quoted 157 lines · Kalle Valo
Quoted 38 lines
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.Quoted 33 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDS
bool
depends on ATH10K
depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yQuoted 8 lines
This follows what mt76 does:
config
MT76_LEDS
bool
depends onMT76_CORE
depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default yI remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 4 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0",Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig static const struct ath10k_hw_params ath10k_hw_params_list[] = { · line 72
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0+ .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7, .cc_wraparound_type = ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.Thanks for the change, np for me.
Quoted 14 lines
Quoted 14 lines
drivers/net/wireless/ath/ath10k/Kconfig +14
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP;Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 6 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the
default_triggerto the mac80211 tpt.We might got both confused by
default_triggeranddefault_state.default_triggeris actually never set and is NULL (actually it's 0)We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the
default_triggerand I will send a follow-up patch to this adding DT support by usingled_classdev_register_extand defininginit_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)Quoted 6 lines
Also ideally I will also send a patch for
default_statefollowing standard LED implementation. (to setdefault_statein DT)I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
Quoted 8 lines
If you want to check out I attached the 2 patch (one dt-bindings and the one for the code) that I will submit when this will be merged (the change is with the assumption that the FIXME line is dropped)
Tested and works correctly with my use case of wifi card attached with pcie. This implementation permits to declare the default trigger in DT instead of hardcoding.
Any news with this? Did I notice the LEDs patch are still in pending... Since I notice the process is a bit slow I wonder if we can also queue the 2 patch i attached in the previous email so we can speed things up?
Quoted 174 lines · Ansuel Smith
Il giorno sab 17 giu 2023 alle ore 19:28 Christian Marangi <[email protected]> ha scritto:
Quoted 171 lines · Christian Marangi
Quoted 158 lines · Kalle Valo
Quoted 38 lines
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.Quoted 33 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDS
bool
depends on ATH10K
depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yQuoted 8 lines
This follows what mt76 does:
config
MT76_LEDS
bool
depends onMT76_CORE
depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default yI remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 5 lines
Quoted 5 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0",Quoted 9 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0+ .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7,.cc_wraparound_type =
ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.Thanks for the change, np for me.
Quoted 14 lines
Quoted 14 lines
drivers/net/wireless/ath/ath10k/Kconfig +14
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP;Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 6 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the
default_triggerto the mac80211 tpt.We might got both confused by
default_triggeranddefault_state.default_triggeris actually never set and is NULL (actually it's 0)We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the
default_triggerand I will send a follow-up patch to this adding DT support by usingled_classdev_register_extand defininginit_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)Quoted 6 lines
Also ideally I will also send a patch for
default_statefollowing standard LED implementation. (to setdefault_statein DT)I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
If you want to check out I attached the 2 patch (one dt-bindings and the one for the code) that I will submit when this will be merged (the change is with the assumption that the FIXME line is dropped)
Quoted 6 lines
Quoted 4 lines
Tested and works correctly with my use case of wifi card attached with pcie. This implementation permits to declare the default trigger in DT instead of hardcoding.
Any news with this? Did I notice the LEDs patch are still in pending...
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Quoted 181 lines · Kalle Valo
Quoted 179 lines · Ansuel Smith
Il giorno sab 17 giu 2023 alle ore 19:28 Christian Marangi <[email protected]> ha scritto:
Quoted 175 lines · Christian Marangi
Quoted 158 lines · Kalle Valo
Quoted 38 lines
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.Quoted 33 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDS
bool
depends on ATH10K
depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yQuoted 8 lines
This follows what mt76 does:
config
MT76_LEDS
bool
depends onMT76_CORE
depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default yI remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 5 lines
Quoted 5 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI, .name = "qca988x hw2.0",Quoted 9 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0+ .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7,.cc_wraparound_type =
ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.Thanks for the change, np for me.
Quoted 14 lines
Quoted 14 lines
drivers/net/wireless/ath/ath10k/Kconfig +14
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label; + ar->leds.wifi_led.default_state = LEDS_GPIO_DEFSTATE_KEEP;Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 6 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the
default_triggerto the mac80211 tpt.We might got both confused by
default_triggeranddefault_state.default_triggeris actually never set and is NULL (actually it's 0)We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the
default_triggerand I will send a follow-up patch to this adding DT support by usingled_classdev_register_extand defininginit_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)Quoted 6 lines
Also ideally I will also send a patch for
default_statefollowing standard LED implementation. (to setdefault_statein DT)I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
If you want to check out I attached the 2 patch (one dt-bindings and the one for the code) that I will submit when this will be merged (the change is with the assumption that the FIXME line is dropped)
Tested and works correctly with my use case of wifi card attached with pcie. This implementation permits to declare the default trigger in DT instead of hardcoding.
Quoted 8 lines
Quoted 1 line
Any news with this? Did I notice the LEDs patch are still in pending...
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
All ok for me, Just I notice the ATH10K_LEDS is not exposed anymore? Is that intended?
Aside from this very happy that we are finally finishing with this long lasting feature!
Signature · 1 line
Ansuel
Am 09.05.2024 um 12:04 schrieb Christian Marangi:
Quoted 176 lines · Kalle Valo
Quoted 175 lines
Quoted 164 lines · Ansuel Smith
Il giorno sab 17 giu 2023 alle ore 19:28 Christian Marangi <[email protected]> ha scritto:
Quoted 161 lines · Christian Marangi
Quoted 150 lines · Kalle Valo
Quoted 37 lines
Quoted 31 lines · Christian Marangi
From: Sebastian Gottschall <[email protected]>
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.Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>---
Hi,
this is a very old patch from 2018 that somehow was talked till 2020 with Kavlo asked to rebase and resubmit and nobody did. So here we are in 2023 with me trying to finally have this upstream.A summarize of the situation.
- The patch is from years in OpenWRT. Used by anything that has ath10k card and a LED connected.
- This patch is also used by the fw variant from Candela Tech with no problem reported.
- It was pointed out that this caused some problem with ipq4019 SoC but the problem was actually caused by a different bug related to interrupts.Quoted 4 lines
I honestly hope we can have this feature merged since it's really funny to have something that was so near merge and jet still not present and with devices not supporting this simple but useful feature.
Quoted 9 lines
Indeed, we should finally get this in. Thanks for working on it.
I did some minor changes to the patch, they are in my pending branch:
My comments below, please review my changes. No need to resend because of these.
Hi,
very happy this is going further.Quoted 32 lines
Quoted 12 lines
drivers/net/wireless/ath/ath10k/Kconfig +6
-0@@ -67,6 +67,23 @@ config ATH10K_DEBUGFS If unsure, say Y to make it easier to debug problems. +config ATH10K_LEDS + bool "Atheros ath10k LED support" + depends on ATH10K + select MAC80211_LEDS + select LEDS_CLASS + select NEW_LEDSdrivers/net/wireless/ath/ath10k/Kconfig config ATH10K_DEBUGFS · line 85
Quoted 10 lines
drivers/net/wireless/ath/ath10k/Kconfig +10
-0+ default y + help + This option enables LEDs support for chipset LED pins. + Each pin is connected via GPIO and can be controlled using + WMI Firmware API. + + The LED device will get available named as "ath10k-phyX" at sysfs and + can be controlled with various triggers. + + Say Y, if you have LED pins connected to the ath10k wireless card.I'm not sure anymore if we should ask anything from the user, better to enable automatically if LED support is enabled in the kernel. So I simplified this to:
config
ATH10K_LEDS
bool
depends on ATH10K
depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yQuoted 8 lines
This follows what mt76 does:
config
MT76_LEDS
bool
depends onMT76_CORE
depends on LEDS_CLASS=y || MT76_CORE=LEDS_CLASS default yI remember there was the same discussion in a previous series. OK for me for making this by default, only concern is any buildbot error (if any)
Anyway OK for the change.
Quoted 4 lines
Quoted 4 lines
drivers/net/wireless/ath/ath10k/Kconfig +0
-0@@ -65,6 +66,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .dev_id = QCA988X_2_0_DEVICE_ID, .bus = ATH10K_BUS_PCI,Quoted 9 lines
Quoted 5 lines
drivers/net/wireless/ath/ath10k/Kconfig +1
-0.name = "qca988x hw2.0", + .led_pin = 1, .patch_load_addr = QCA988X_HW_2_0_PATCH_LOAD_ADDR, .uart_pin = 7,.cc_wraparound_type =
ATH10K_HW_CC_WRAP_SHIFTED_ALL,I prefer following the field order from struct
ath10k_hw_paramsdeclaration and also setting fields explicitly to zero (even though there are gaps still) so I changed that for every entry.Thanks for the change, np for me.
Quoted 13 lines
Quoted 13 lines
drivers/net/wireless/ath/ath10k/Kconfig +13
-0+int ath10k_leds_register(struct ath10k *ar) +{ + int ret; + + if (ar->hw_params.led_pin == 0) + /* leds not supported */ + return 0; + + snprintf(ar->leds.label, sizeof(ar->leds.label), "ath10k-%s", + wiphy_name(ar->hw->wiphy)); + ar->leds.wifi_led.active_low = 1; + ar->leds.wifi_led.gpio = ar->hw_params.led_pin; + ar->leds.wifi_led.name = ar->leds.label;Quoted 9 lines
drivers/net/wireless/ath/ath10k/Kconfig
Quoted 7 lines
+
ar->leds.wifi_led.default_state=LEDS_GPIO_DEFSTATE_KEEP;drivers/net/wireless/ath/ath10k/Kconfig +6
-0+ + ar->leds.cdev.name = ar->leds.label; + ar->leds.cdev.brightness_set_blocking = ath10k_leds_set_brightness_blocking; + + /* FIXME: this assignment doesn't make sense as it's NULL, remove it? */ + ar->leds.cdev.default_trigger = ar->leds.wifi_led.default_trigger;But what to do with this FIXME?
It was pushed by you in v13.
I could be wrong but your idea was to prepare for future support of other patch that would set the
default_triggerto the mac80211 tpt.We might got both confused by
default_triggeranddefault_state.default_triggeris actually never set and is NULL (actually it's 0)We have other 2 patch that adds tpt rates for the mac80211 LED trigger and set this trigger as the default one but honestly I would chose a different implementation than hardcoding everything.
If it's ok for you, I would drop the comment and the
default_triggerand I will send a follow-up patch to this adding DT support by usingled_classdev_register_extand defininginit_data.
(and this indirectly would permit better LED naming and defining of default-trigger in DT)Quoted 6 lines
Also ideally I will also send a patch for
default_statefollowing standard LED implementation. (to setdefault_statein DT)I would prefer this approach as the LED patch already took way too much time and I think it's better to merge this initial version and then improve it.
If you want to check out I attached the 2 patch (one dt-bindings and the one for the code) that I will submit when this will be merged (the change is with the assumption that the FIXME line is dropped)
Quoted 5 lines
Quoted 4 lines
Tested and works correctly with my use case of wifi card attached with pcie. This implementation permits to declare the default trigger in DT instead of hardcoding.
Any news with this? Did I notice the LEDs patch are still in pending...
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 7 lines
Quoted 2 lines
All ok for me, Just I notice the
ATH10K_LEDSis not exposed anymore? Is that intended?Aside from this very happy that we are finally finishing with this long lasting feature!
since ATH10K_LEDS is no exposed option anymore. how is this feature enabled then? Its not selected by any dependency
Sebastian
Quoted 1 line
Quoted 10 lines · Christian Marangi
Quoted 7 lines
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
All ok for me, Just I notice the
ATH10K_LEDSis not exposed anymore? Is that intended?
Yes. It follows the same idea as other wireless drivers do, for example iwlwifi:
config IWLWIFI_LEDS
bool depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 depends on IWLMVM || IWLDVM select LEDS_TRIGGERS select MAC80211_LEDS default y
So what this patch now does:
config ATH10K_LEDS
bool depends on ATH10K depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default y
The idea being that if LEDS_CLASS is enabled then ATH10K_LEDS is automatically enabled. But please let us know if something is wrong here.
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Quoted 26 lines · Kalle Valo
Quoted 10 lines · Christian Marangi
Quoted 7 lines
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
All ok for me, Just I notice the
ATH10K_LEDSis not exposed anymore? Is that intended?Yes. It follows the same idea as other wireless drivers do, for example iwlwifi:
config
IWLWIFI_LEDSbool depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 depends on IWLMVM || IWLDVM select LEDS_TRIGGERS select MAC80211_LEDS default ySo what this patch now does:
config
ATH10K_LEDS
Quoted 9 lines
bool depends on ATH10K depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211 default yThe idea being that if
LEDS_CLASSis enabled thenATH10K_LEDSis automatically enabled. But please let us know if something is wrong here.
Sure, was just asking some clarification about it. Not a problem for me since we are using other pattern to handle this.
Signature · 1 line
Ansuel
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.
My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.
and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.
So Ansuel, is your work on behalf of The Linux Foundation?
Quoted 18 lines · Jeff Johnson
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 7 lines
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.So Ansuel, is your work on behalf of The Linux Foundation?
BTW in the pending branch I can change the copyright back to original so no need to resend because of this. But I'll need guidance from Ansuel.
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Quoted 18 lines · Jeff Johnson
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 8 lines
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.So Ansuel, is your work on behalf of The Linux Foundation?
When I resubmitted this at times, I just updated the copyright to the current year so I guess it was wrong doing that?
As you can see from the copyright header this patch went all around and I think at the end (around 2018) the Linux copyright was added as it was submitted upstream. (can't remember if maintainers were asking that)
So me watching the old year and resubmitting it, just updated the date.
Soo I think we should revert to 2018?
Signature · 1 line
Ansuel
Quoted 31 lines · Christian Marangi
Quoted 18 lines · Jeff Johnson
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 8 lines
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.So Ansuel, is your work on behalf of The Linux Foundation?
When I resubmitted this at times, I just updated the copyright to the current year so I guess it was wrong doing that?
Quoted 8 lines
As you can see from the copyright header this patch went all around and I think at the end (around 2018) the Linux copyright was added as it was submitted upstream. (can't remember if maintainers were asking that)
So me watching the old year and resubmitting it, just updated the date.
Soo I think we should revert to 2018?
Yes, in this case changing the Linux Foundation copyright back to 2018 is correct.
/jeff
Quoted 37 lines · Jeff Johnson
Quoted 35 lines · Christian Marangi
Quoted 18 lines · Jeff Johnson
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 8 lines
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.So Ansuel, is your work on behalf of The Linux Foundation?
When I resubmitted this at times, I just updated the copyright to the current year so I guess it was wrong doing that?
As you can see from the copyright header this patch went all around and I think at the end (around 2018) the Linux copyright was added as it was submitted upstream. (can't remember if maintainers were asking that)
Quoted 6 lines
Quoted 4 lines
So me watching the old year and resubmitting it, just updated the date.
Soo I think we should revert to 2018?
Yes, in this case changing the Linux Foundation copyright back to 2018 is correct.
I changed it now back to 2018, please check:
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Quoted 41 lines · Kalle Valo
Quoted 39 lines · Jeff Johnson
Quoted 37 lines · Christian Marangi
Quoted 18 lines · Jeff Johnson
Quoted 8 lines · Jeff Johnson
Quoted 6 lines · Kalle Valo
Sorry for the delay but finally I looked at this again. I decided to just remove the fixme and otherwise it looks good for me. Please check my changes:
Quoted 8 lines
I have a question about the copyrights in the two new files:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.My understanding is that Qualcomm's affiliation with Linux Foundation via Code Aurora ended in December 2021, and hence any contributions in 2022-2023 should be the copyright of Qualcomm Innovation Center, Inc.
Quoted 8 lines
ok it seems like Kalle's v13 had:
+ * Copyright (c) 2018, The Linux Foundation. All rights reserved.and Ansuel's v14 has:
+ * Copyright (c) 2018-2023, The Linux Foundation. All rights reserved.So Ansuel, is your work on behalf of The Linux Foundation?
When I resubmitted this at times, I just updated the copyright to the current year so I guess it was wrong doing that?
As you can see from the copyright header this patch went all around and I think at the end (around 2018) the Linux copyright was added as it was submitted upstream. (can't remember if maintainers were asking that)
So me watching the old year and resubmitting it, just updated the date.
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
Soo I think we should revert to 2018?
Yes, in this case changing the Linux Foundation copyright back to 2018 is correct.
I changed it now back to 2018, please check:
LGTM, thanks!
Quoted 6 lines · Christian Marangi
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.
Quoted 8 lines
Signed-off-by Sebastian Gottschall <[email protected]>Reviewed-by Steve deRosier <[email protected]>[kvalo: major reorg and cleanup]Signed-off-by Kalle Valo <[email protected]>[ansuel: rebase and small cleanup]Signed-off-by Christian Marangi <[email protected]>Signed-off-by Kalle Valo <[email protected]>
Patch applied to ath-next branch of ath.git, thanks.
8e1debd82466 wifi: ath10k: add LED and GPIO controlling support for various chipsets
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/patch/[email protected]/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches