ath10k: Allow setting coverage class
v3 cover ath10k: Allow setting coverage class
Hi,
This revision of the patch has quite a number of changes, most notably the handler to set the registers is now called from a work queue after a WMI event.
The reason for this is that Sebastian reported that at least the WAVE2 chipsets do not behave well when the calls happen before the hardware is initialized. This means we need to check ar->state, which in turn is protected by conf_mutex, so the task is now pushed to the general work queue to prevent having to hold the lock during the WMI event processing.
Changes in v3:
* Only update register values if hardware is initialized
* Use the SM/MS macros instead of manual bitshifts and masks
* Use the hardware phyclk register instead of assuming a clock speed
* Force dbglog_mask of ~0 and dbglog_level of at least WARN if active
* Only call code for selected WMI events
The last two items are a bit of a guess for me. In particular it looks like the default log level is already WARN, but I suppose that this should be good enough to get reports for internal chip resets. I have no way of verifying this myself though.
Changes in v2 were:
* Move code into hw.c and run from new hw_ops depending on chip revision
* Error message corrections
The patch assumes that a new hw_ops struct exists based on work by Vasanthakumar. The rename patch is on top of "ath10k: Add provision for Rx descriptor abstraction" and adjustment in either patchset will be neccessary for merging.
What are the plans with regard to getting those patches merged (ath10k:
Padding related clean ups in rx)?
Benjamin Berg (2):
ath10k: Rename hw_rx_desc_ops to hw_ops to use it for other purposes
ath10k: Allow setting coverage class
drivers/net/wireless/ath/ath10k/core.c | 35 +++++--- drivers/net/wireless/ath/ath10k/core.h | 12 +++ drivers/net/wireless/ath/ath10k/hw.c | 143 ++++++++++++++++++++++++++++++++- drivers/net/wireless/ath/ath10k/hw.h | 36 +++++++-- drivers/net/wireless/ath/ath10k/mac.c | 19 +++++ drivers/net/wireless/ath/ath10k/wmi.c | 37 +++++++++ 6 files changed, 263 insertions(+), 19 deletions(-)
Signature · 7 lines
2.9.3 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
PATCH v3 1/2 ath10k: Rename hw_rx_desc_ops to hw_ops to use it for other purposes
The structure contains hardware specific operations. Rename the struct so that it is appropriate to be used for other operations.
--- drivers/net/wireless/ath/ath10k/core.c | 24 ++++++++++++------------ drivers/net/wireless/ath/ath10k/hw.c | 4 ++-- drivers/net/wireless/ath/ath10k/hw.h | 8 ++++---- 3 files changed, 18 insertions(+), 18 deletions(-)
drivers/net/wireless/ath/ath10k/core.c +12 -12
@@ -68,7 +68,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA988X_BOARD_DATA_SZ, .board_ext_size = QCA988X_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA9887_HW_1_0_VERSION,
@@ -88,7 +88,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA9887_BOARD_DATA_SZ, .board_ext_size = QCA9887_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA6174_HW_2_1_VERSION,
@@ -106,7 +106,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA6174_BOARD_DATA_SZ, .board_ext_size = QCA6174_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA6174_HW_2_1_VERSION,
@@ -125,7 +125,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA6174_BOARD_DATA_SZ, .board_ext_size = QCA6174_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA6174_HW_3_0_VERSION,
@@ -144,7 +144,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA6174_BOARD_DATA_SZ, .board_ext_size = QCA6174_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA6174_HW_3_2_VERSION,
@@ -164,7 +164,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA6174_BOARD_DATA_SZ, .board_ext_size = QCA6174_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA99X0_HW_2_0_DEV_VERSION,
@@ -188,7 +188,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA99X0_BOARD_DATA_SZ, .board_ext_size = QCA99X0_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca99x0_rx_desc_ops, + .hw_ops = &qca99x0_ops, }, { .id = QCA9984_HW_1_0_DEV_VERSION,
@@ -212,7 +212,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA99X0_BOARD_DATA_SZ, .board_ext_size = QCA99X0_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca99x0_rx_desc_ops, + .hw_ops = &qca99x0_ops, }, { .id = QCA9888_HW_2_0_DEV_VERSION,
@@ -235,7 +235,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA99X0_BOARD_DATA_SZ, .board_ext_size = QCA99X0_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca99x0_rx_desc_ops, + .hw_ops = &qca99x0_ops, }, { .id = QCA9377_HW_1_0_DEV_VERSION,
@@ -253,7 +253,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA9377_BOARD_DATA_SZ, .board_ext_size = QCA9377_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA9377_HW_1_1_DEV_VERSION,
@@ -271,7 +271,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA9377_BOARD_DATA_SZ, .board_ext_size = QCA9377_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca988x_rx_desc_ops, + .hw_ops = &qca988x_ops, }, { .id = QCA4019_HW_1_0_DEV_VERSION,
@@ -296,7 +296,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[] = { .board_size = QCA4019_BOARD_DATA_SZ, .board_ext_size = QCA4019_BOARD_EXT_DATA_SZ, }, - .hw_rx_desc_ops = &qca99x0_rx_desc_ops, + .hw_ops = &qca99x0_ops, }, };
drivers/net/wireless/ath/ath10k/hw.c +2 -2
@@ -220,7 +220,7 @@ void ath10k_hw_fill_survey_time(struct ath10k *ar, struct survey_info *survey, survey->time_busy =CCNT_TO_MSEC (ar, rcc); } -const struct ath10k_hw_rx_desc_ops qca988x_rx_desc_ops = { +const struct ath10k_hw_ops qca988x_ops = { };static int ath10k_qca99x0_rx_desc_get_l3_pad_bytes (struct htt_rx_desc *rxd)
@@ -229,6 +229,6 @@ static int ath10k_qca99x0_rx_desc_get_l3_pad_bytes(struct htt_rx_desc *rxd) RX_MSDU_END_INFO1_L3_HDR_PAD); } -const struct ath10k_hw_rx_desc_ops qca99x0_rx_desc_ops = { +const struct ath10k_hw_ops qca99x0_ops = { .rx_desc_get_l3_pad_bytes = ath10k_qca99x0_rx_desc_get_l3_pad_bytes, };
drivers/net/wireless/ath/ath10k/hw.h +4 -4
@@ -410,18 +410,18 @@ struct ath10k_hw_params {size_t board_ext_size; } fw; -const struct ath10k_hw_rx_desc_ops *hw_rx_desc_ops; +const struct ath10k_hw_ops *hw_ops; };struct htt_rx_desc ;/* Defines needed for Rx descriptor abstraction */ -struct ath10k_hw_rx_desc_ops { +struct ath10k_hw_ops {int (*rx_desc_get_l3_pad_bytes)(struct htt_rx_desc *rxd); }; -extern const struct ath10k_hw_rx_desc_ops qca988x_rx_desc_ops; -extern const struct ath10k_hw_rx_desc_ops qca99x0_rx_desc_ops; +extern const struct ath10k_hw_ops qca988x_ops; +extern const struct ath10k_hw_ops qca99x0_ops;/* Target specific defines for MAIN firmware */ #define TARGET_NUM_VDEVS 8
Signature · 7 lines
2.9.3 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
PATCH v3 2/2 ath10k: Allow setting coverage class
In reply to Benjamin BergUnfortunately ath10k does not generally allow modifying the coverage class with the stock firmware and Qualcomm has so far refused to implement this feature so that it can be properly supported in ath10k. If we however know the registers that need to be modified for proper operation with a higher coverage class, then we can do these modifications from the driver.
This patch implements this hack for first generation cards which are based on a core that is similar to ath9k. The registers are modified in place and need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
--- drivers/net/wireless/ath/ath10k/core.c | 11 +++ drivers/net/wireless/ath/ath10k/core.h | 12 +++ drivers/net/wireless/ath/ath10k/hw.c | 139 +++++++++++++++++++++++++++++++++ drivers/net/wireless/ath/ath10k/hw.h | 28 ++++++- drivers/net/wireless/ath/ath10k/mac.c | 19 +++++ drivers/net/wireless/ath/ath10k/wmi.c | 37 +++++++++ 6 files changed, 245 insertions(+), 1 deletion(-)
drivers/net/wireless/ath/ath10k/core.c +11 -0
@@ -1552,6 +1552,15 @@ static void ath10k_core_restart(struct work_struct *work)mutex_unlock (&ar->conf_mutex); } +static void ath10k_core_set_coverage_class_work (struct work_struct *work) +{ + struct ath10k *ar = container_of(work, struct ath10k, + set_coverage_class_work); + +if (ar->hw_params.hw_ops->set_coverage_class) + ar->hw_params.hw_ops->set_coverage_class (ar,-1 ); +} +static int ath10k_core_init_firmware_features (struct ath10k *ar) {struct ath10k_fw_file *fw_file = &ar->normal_mode_fw.fw_file;
@@ -2260,6 +2269,8 @@ struct ath10k *ath10k_core_create(size_t priv_size, struct device *dev,INIT_WORK (&ar->register_work, ath10k_core_register_work);INIT_WORK (&ar->restart_work, ath10k_core_restart); +INIT_WORK (&ar->set_coverage_class_work, + ath10k_core_set_coverage_class_work); ret =ath10k_debug_create (ar);if (ret)
drivers/net/wireless/ath/ath10k/core.h +12 -0
@@ -890,6 +890,18 @@ struct ath10k {struct ath10k_thermal thermal;struct ath10k_wow wow; +struct work_struct set_coverage_class_work; +/* protected by conf_mutex */ +struct { +s16 coverage_class; + +u32 reg_phyclk; +u32 reg_slottime_conf; +u32 reg_slottime_orig; +u32 reg_ack_cts_timeout_conf; +u32 reg_ack_cts_timeout_orig; + } fw_coverage; +/* must be last */ u8 drv_priv[0 ]__aligned(sizeof(void *)) ; };
drivers/net/wireless/ath/ath10k/hw.c +139 -0
175 lines not on this page · raw message
drivers/net/wireless/ath/ath10k/hw.h +27 -1
@@ -230,6 +230,7 @@ struct ath10k_hw_regs {u32 rtc_soc_base_address;u32 rtc_wmac_base_address;u32 soc_core_base_address; +u32 wlan_mac_base_address;u32 ce_wrapper_base_address;u32 ce0_base_address;u32 ce1_base_address;
@@ -418,6 +419,7 @@ struct htt_rx_desc;/* Defines needed for Rx descriptor abstraction */ struct ath10k_hw_ops {int (*rx_desc_get_l3_pad_bytes)(struct htt_rx_desc *rxd); +void (*set_coverage_class)(struct ath10k *ar,s16 value); };extern const struct ath10k_hw_ops qca988x_ops;
@@ -605,7 +607,7 @@ extern const struct ath10k_hw_ops qca99x0_ops;#define WLAN_SI_BASE_ADDRESS 0x00010000#define WLAN_GPIO_BASE_ADDRESS 0x00014000#define WLAN_ANALOG_INTF_BASE_ADDRESS 0x0001c000 -#define WLAN_MAC_BASE_ADDRESS 0x00020000 +#define WLAN_MAC_BASE_ADDRESS ar->regs->wlan_mac_base_address#define EFUSE_BASE_ADDRESS 0x00030000#define FPGA_REG_BASE_ADDRESS 0x00039000#define WLAN_UART2_BASE_ADDRESS 0x00054c00
@@ -805,4 +807,28 @@ extern const struct ath10k_hw_ops qca99x0_ops;#define RTC_STATE_V_GET (x) (((x) & RTC_STATE_V_MASK) >> RTC_STATE_V_LSB) +/* Register definitions for first generation ath10k cards. These cards include +* a mac thich has a register allocation similar to ath9k and at least some +* registers including the ones relevant for modifying the coverage class are +* identical to the ath9k definitions. +* These registers are usually managed by the ath10k firmware. However by +* overriding them it is possible to support coverage class modifications. +*/ +#define WAVE1_PCU_ACK_CTS_TIMEOUT 0x8014 +#define WAVE1_PCU_ACK_CTS_TIMEOUT_MAX 0x00003FFF +#define WAVE1_PCU_ACK_CTS_TIMEOUT_ACK_MASK 0x00003FFF +#define WAVE1_PCU_ACK_CTS_TIMEOUT_ACK_LSB 0 +#define WAVE1_PCU_ACK_CTS_TIMEOUT_CTS_MASK 0x3FFF0000 +#define WAVE1_PCU_ACK_CTS_TIMEOUT_CTS_LSB 16 + +#define WAVE1_PCU_GBL_IFS_SLOT 0x1070 +#define WAVE1_PCU_GBL_IFS_SLOT_MASK 0x0000FFFF +#define WAVE1_PCU_GBL_IFS_SLOT_MAX 0x0000FFFF +#define WAVE1_PCU_GBL_IFS_SLOT_LSB 0 +#define WAVE1_PCU_GBL_IFS_SLOT_RESV0 0xFFFF0000 + +#define WAVE1_PHYCLK 0x801C +#define WAVE1_PHYCLK_USEC_MASK 0x0000007F +#define WAVE1_PHYCLK_USEC_LSB 0 +#endif /* _HW_H_ */
drivers/net/wireless/ath/ath10k/mac.c +19 -0
@@ -5372,6 +5372,20 @@ static void ath10k_bss_info_changed(struct ieee80211_hw *hw,mutex_unlock (&ar->conf_mutex); } +static void ath10k_mac_op_set_coverage_class (struct ieee80211_hw *hw,s16 value) +{ +struct ath10k *ar = hw->priv; + +/* This function should never be called if setting the coverage class +* is not supported on this hardware. +*/ +if (!ar->hw_params.hw_ops->mac_op_set_coverage_class) { +WARN_ON_ONCE (1 ); +return ; + } + ar->hw_params.hw_ops->mac_op_set_coverage_class (ar, value); +} +static int ath10k_hw_scan (struct ieee80211_hw *hw,struct ieee80211_vif *vif,struct ieee80211_scan_request *hw_req)
@@ -7397,6 +7411,7 @@ static const struct ieee80211_ops ath10k_ops = { .remove_interface = ath10k_remove_interface, .configure_filter = ath10k_configure_filter, .bss_info_changed = ath10k_bss_info_changed, + .set_coverage_class = ath10k_mac_op_set_coverage_class, .hw_scan = ath10k_hw_scan, .cancel_hw_scan = ath10k_cancel_hw_scan, .set_key = ath10k_set_key,
@@ -7974,6 +7989,10 @@ int ath10k_mac_register(struct ath10k *ar) ar->running_fw->fw_file.fw_features)) ar->ops->wake_tx_queue =NULL ; +/* Disable set_coverage_class for chipsets that do not support it. */ +if (!ar->hw_params.hw_ops->mac_op_set_coverage_class) + ar->ops->set_coverage_class =NULL ; + ret =ath_regd_init (&ar->ath_common.regulatory, ar->hw->wiphy, ath10k_reg_notifier);if (ret) {
drivers/net/wireless/ath/ath10k/wmi.c +37 -0
@@ -4879,6 +4879,12 @@ exit:return 0 ; } +static inline void ath10k_wmi_queue_set_coverage_class_work (struct ath10k *ar) +{ +if (ar->hw_params.hw_ops->set_coverage_class) +queue_work (ar->workqueue, &ar->set_coverage_class_work); +} +static void ath10k_wmi_op_rx (struct ath10k *ar,struct sk_buff *skb) {struct wmi_cmd_hdr *cmd_hdr;
@@ -4899,6 +4905,7 @@ static void ath10k_wmi_op_rx(struct ath10k *ar, struct sk_buff *skb)return ;case WMI_SCAN_EVENTID :ath10k_wmi_event_scan (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_CHAN_INFO_EVENTID :ath10k_wmi_event_chan_info (ar, skb);
@@ -4908,15 +4915,18 @@ static void ath10k_wmi_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_DEBUG_MESG_EVENTID :ath10k_wmi_event_debug_mesg (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_UPDATE_STATS_EVENTID :ath10k_wmi_event_update_stats (ar, skb);break ;case WMI_VDEV_START_RESP_EVENTID :ath10k_wmi_event_vdev_start_resp (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_VDEV_STOPPED_EVENTID :ath10k_wmi_event_vdev_stopped (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_PEER_STA_KICKOUT_EVENTID :ath10k_wmi_event_peer_sta_kickout (ar, skb);
@@ -4932,12 +4942,14 @@ static void ath10k_wmi_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_ROAM_EVENTID :ath10k_wmi_event_roam (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_PROFILE_MATCH :ath10k_wmi_event_profile_match (ar, skb);break ;case WMI_DEBUG_PRINT_EVENTID :ath10k_wmi_event_debug_print (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_PDEV_QVIT_EVENTID :ath10k_wmi_event_pdev_qvit (ar, skb);
@@ -4986,6 +4998,7 @@ static void ath10k_wmi_op_rx(struct ath10k *ar, struct sk_buff *skb)return ;case WMI_READY_EVENTID :ath10k_wmi_event_ready (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;default :ath10k_warn (ar,"Unknown eventid: %d\n" , id);
@@ -5029,6 +5042,7 @@ static void ath10k_wmi_10_1_op_rx(struct ath10k *ar, struct sk_buff *skb)return ;case WMI_10X_SCAN_EVENTID :ath10k_wmi_event_scan (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_CHAN_INFO_EVENTID :ath10k_wmi_event_chan_info (ar, skb);
@@ -5038,15 +5052,18 @@ static void ath10k_wmi_10_1_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10X_DEBUG_MESG_EVENTID :ath10k_wmi_event_debug_mesg (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_UPDATE_STATS_EVENTID :ath10k_wmi_event_update_stats (ar, skb);break ;case WMI_10X_VDEV_START_RESP_EVENTID :ath10k_wmi_event_vdev_start_resp (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_VDEV_STOPPED_EVENTID :ath10k_wmi_event_vdev_stopped (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_PEER_STA_KICKOUT_EVENTID :ath10k_wmi_event_peer_sta_kickout (ar, skb);
@@ -5062,12 +5079,14 @@ static void ath10k_wmi_10_1_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10X_ROAM_EVENTID :ath10k_wmi_event_roam (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_PROFILE_MATCH :ath10k_wmi_event_profile_match (ar, skb);break ;case WMI_10X_DEBUG_PRINT_EVENTID :ath10k_wmi_event_debug_print (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_PDEV_QVIT_EVENTID :ath10k_wmi_event_pdev_qvit (ar, skb);
@@ -5107,6 +5126,7 @@ static void ath10k_wmi_10_1_op_rx(struct ath10k *ar, struct sk_buff *skb)return ;case WMI_10X_READY_EVENTID :ath10k_wmi_event_ready (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10X_PDEV_UTF_EVENTID :/* ignore utf events */
@@ -5140,6 +5160,7 @@ static void ath10k_wmi_10_2_op_rx(struct ath10k *ar, struct sk_buff *skb)return ;case WMI_10_2_SCAN_EVENTID :ath10k_wmi_event_scan (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_CHAN_INFO_EVENTID :ath10k_wmi_event_chan_info (ar, skb);
@@ -5149,15 +5170,18 @@ static void ath10k_wmi_10_2_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_2_DEBUG_MESG_EVENTID :ath10k_wmi_event_debug_mesg (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_UPDATE_STATS_EVENTID :ath10k_wmi_event_update_stats (ar, skb);break ;case WMI_10_2_VDEV_START_RESP_EVENTID :ath10k_wmi_event_vdev_start_resp (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_VDEV_STOPPED_EVENTID :ath10k_wmi_event_vdev_stopped (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_PEER_STA_KICKOUT_EVENTID :ath10k_wmi_event_peer_sta_kickout (ar, skb);
@@ -5173,12 +5197,14 @@ static void ath10k_wmi_10_2_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_2_ROAM_EVENTID :ath10k_wmi_event_roam (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_PROFILE_MATCH :ath10k_wmi_event_profile_match (ar, skb);break ;case WMI_10_2_DEBUG_PRINT_EVENTID :ath10k_wmi_event_debug_print (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_PDEV_QVIT_EVENTID :ath10k_wmi_event_pdev_qvit (ar, skb);
@@ -5209,15 +5235,18 @@ static void ath10k_wmi_10_2_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_2_VDEV_STANDBY_REQ_EVENTID :ath10k_wmi_event_vdev_standby_req (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_VDEV_RESUME_REQ_EVENTID :ath10k_wmi_event_vdev_resume_req (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_SERVICE_READY_EVENTID :ath10k_wmi_event_service_ready (ar, skb);return ;case WMI_10_2_READY_EVENTID :ath10k_wmi_event_ready (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_2_PDEV_TEMPERATURE_EVENTID :ath10k_wmi_event_temperature (ar, skb);
@@ -5267,12 +5296,14 @@ static void ath10k_wmi_10_4_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_4_DEBUG_MESG_EVENTID :ath10k_wmi_event_debug_mesg (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_SERVICE_READY_EVENTID :ath10k_wmi_event_service_ready (ar, skb);return ;case WMI_10_4_SCAN_EVENTID :ath10k_wmi_event_scan (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_CHAN_INFO_EVENTID :ath10k_wmi_event_chan_info (ar, skb);
@@ -5282,12 +5313,14 @@ static void ath10k_wmi_10_4_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_4_READY_EVENTID :ath10k_wmi_event_ready (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_PEER_STA_KICKOUT_EVENTID :ath10k_wmi_event_peer_sta_kickout (ar, skb);break ;case WMI_10_4_ROAM_EVENTID :ath10k_wmi_event_roam (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_HOST_SWBA_EVENTID :ath10k_wmi_event_host_swba (ar, skb);
@@ -5297,12 +5330,15 @@ static void ath10k_wmi_10_4_op_rx(struct ath10k *ar, struct sk_buff *skb)break ;case WMI_10_4_DEBUG_PRINT_EVENTID :ath10k_wmi_event_debug_print (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_VDEV_START_RESP_EVENTID :ath10k_wmi_event_vdev_start_resp (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_VDEV_STOPPED_EVENTID :ath10k_wmi_event_vdev_stopped (ar, skb); +ath10k_wmi_queue_set_coverage_class_work (ar);break ;case WMI_10_4_WOW_WAKEUP_HOST_EVENTID :case WMI_10_4_PEER_RATECODE_LIST_EVENTID :
@@ -6017,6 +6053,7 @@ void ath10k_wmi_start_scan_init(struct ath10k *ar, | WMI_SCAN_EVENT_COMPLETED |WMI_SCAN_EVENT_BSS_CHANNEL |WMI_SCAN_EVENT_FOREIGN_CHANNEL + |WMI_SCAN_EVENT_FOREIGN_CHANNEL_EXIT |WMI_SCAN_EVENT_DEQUEUED ; arg->scan_ctrl_flags |=WMI_SCAN_CHAN_STAT_EVENT ; arg->n_bssids =1 ;
Signature · 7 lines
2.9.3 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 25 lines · Benjamin Berg
Unfortunately ath10k does not generally allow modifying the coverage class with the stock firmware and Qualcomm has so far refused to implement this feature so that it can be properly supported in ath10k. If we however know the registers that need to be modified for proper operation with a higher coverage class, then we can do these modifications from the driver.
This patch implements this hack for first generation cards which are based on a core that is similar to ath9k. The registers are modified in place and need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
drivers/net/wireless/ath/ath10k/wmi.c +0
-0
drivers/net/wireless/ath/ath10k/wmi.c exit: · line 4886
Quoted 8 lines
drivers/net/wireless/ath/ath10k/wmi.c +5
-0@@ -4879,6 +4879,12 @@ exit:return 0 ; } +static inline void ath10k_wmi_queue_set_coverage_class_work (struct ath10k *ar) +{ +if (ar->hw_params.hw_ops->set_coverage_class) +queue_work (ar->workqueue, &ar->set_coverage_class_work); +}
Maybe this should first check to see if the user has specified a coverage class before it attempts to do any work at all?
That way, if user does not set anything, then the behaviour does not change in any significant way?
Thanks,
Ben
Signature · 7 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 53 lines · Ben Greear
Quoted 40 lines · Benjamin Berg
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this
the register status is verified after certain WMI events from the firmware.The coverage class may not be modified temporarily right after the card
re-initializes the registers. This is for example the case during scanning.Thanks to Sebastian Gottschall <[email protected]> for initially
working on a userspace support for this. This patch wouldn't have been
possible without this documentation.drivers/net/wireless/ath/ath10k/wmi.c +0
-0drivers/net/wireless/ath/ath10k/wmi.c exit: · line 4888
Quoted 10 lines
drivers/net/wireless/ath/ath10k/wmi.c +5
-0@@ -4879,6 +4879,12 @@ exit: return 0; } +static inline void ath10k_wmi_queue_set_coverage_class_work (struct ath10k *ar) +{ +if (ar->hw_params.hw_ops->set_coverage_class) +queue_work (ar->workqueue, &ar- >set_coverage_class_work); +}
Quoted 7 lines
Maybe this should first check to see if the user has specified a coverage class
before it attempts to do any work at all?That way, if user does not set anything, then the behaviour does not change
in any significant way?
Hm, yes, adding a check there looks simple and I don't see any reason why it wouldn't work.
Benjamin
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Am 25.08.2016 um 16:33 schrieb Benjamin Berg:
Quoted 53 lines · Ben Greear
Quoted 52 lines · Benjamin Berg
Quoted 37 lines
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this
the register status is verified after certain WMI events from the firmware.The coverage class may not be modified temporarily right after the card
re-initializes the registers. This is for example the case during scanning.Thanks to Sebastian Gottschall <[email protected]> for initially
working on a userspace support for this. This patch wouldn't have been
possible without this documentation.drivers/net/wireless/ath/ath10k/wmi.c +0
-0drivers/net/wireless/ath/ath10k/wmi.c exit: · line 4888
Quoted 10 lines
drivers/net/wireless/ath/ath10k/wmi.c +5
-0@@ -4879,6 +4879,12 @@ exit:return 0 ; } +static inline void ath10k_wmi_queue_set_coverage_class_work (struct ath10k *ar) +{ +if (ar->hw_params.hw_ops->set_coverage_class) +queue_work (ar->workqueue, &ar- > set_coverage_class_work); +}Maybe this should first check to see if the user has specified a coverage class
before it attempts to do any work at all?
Quoted 5 lines
Quoted 3 lines
That way, if user does not set anything, then the behaviour does not change
in any significant way?Hm, yes, adding a check there looks simple and I don't see any reason why it wouldn't work.
consider that i already implemented this in my version of the patch i supplied to you. however. mine doesnt use queue handling but just checks if the hw is ready before setting anything
Quoted 2 lines
Benjamin
Signature · 17 lines
Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: [email protected] Tel.: +496251-582650 / Fax: +496251-5826565 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 11 lines · Benjamin Berg
Unfortunately ath10k does not generally allow modifying the coverage class with the stock firmware and Qualcomm has so far refused to implement this feature so that it can be properly supported in ath10k. If we however know the registers that need to be modified for proper operation with a higher coverage class, then we can do these modifications from the driver.
This patch implements this hack for first generation cards which are based on a core that is similar to ath9k. The registers are modified in place and need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.
Quoted 6 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be 0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 24 lines · Ben Greear
Quoted 14 lines · Benjamin Berg
Unfortunately ath10k does not generally allow modifying the coverage class with the stock firmware and Qualcomm has so far refused to implement this feature so that it can be properly supported in ath10k. If we however know the registers that need to be modified for proper operation with a higher coverage class, then we can do these modifications from the driver.
This patch implements this hack for first generation cards which are based on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Am 16.10.2017 um 19:59 schrieb Adrian Chadd:
Quoted 28 lines · Ben Greear
Quoted 22 lines · Benjamin Berg
Quoted 13 lines
Unfortunately ath10k does not generally allow modifying the coverage class with the stock firmware and Qualcomm has so far refused to implement this feature so that it can be properly supported in ath10k. If we however know the registers that need to be modified for proper operation with a higher coverage class, then we can do these modifications from the driver.
This patch implements this hack for first generation cards which are based on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).
Quoted 6 lines
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
if someone is interested i can provide a patch witch works as well for 998x and 9984 and usually other newer chipsets too.
but clock parameters need to be adjusted for these newer ones. the only problem is that its based on unoffical registers which arent documented and the patch for the 99xx chipsets is very different from 988x
Signature · 17 lines
Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: [email protected] Tel.: +496251-582650 / Fax: +496251-5826565 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
hiya,
I'd honestly rather see firmware changes for wave 2 chips, as I know there's a lot more MAC changes messing up this stuff ..
-adrian
Quoted 61 lines · Sebastian Gottschall
Am 16.10.2017 um 19:59 schrieb Adrian Chadd:
Quoted 38 lines · Ben Greear
Quoted 30 lines · Benjamin Berg
Quoted 19 lines
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).Quoted 6 lines
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
if someone is interested i can provide a patch witch works as well for 998x and 9984 and usually other newer chipsets too.
but clock parameters need to be adjusted for these newer ones. the only problem is that its based on unoffical registers which arent documented and the patch for the 99xx chipsets is very different from 988x
--
Mit freundlichen Grüssen / RegardsSebastian Gottschall / CTO
Quoted 9 lines
NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 BensheimRegistergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: [email protected]
Tel.: +496251-582650 / Fax: +496251-5826565
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 4 lines · Adrian Chadd
hiya,
I'd honestly rather see firmware changes for wave 2 chips, as I know there's a lot more MAC changes messing up this stuff ..
For wave-1, it appears to be quite simple to modify the firmware to set the ack-cts register to a specific value (and re-set it after scanning, etc).
Is the wave-2 stuff that much different? I've recently hooked in my CT firmware for wave-1 to support the driver's ack/cts calculations (but without needing all the manual register twiddling). I could probably do the same for 9984 if it mattered. But, that still doesn't help stock driver/firmware users.
Thanks,
Ben
Quoted 84 lines
-adrian
Quoted 61 lines · Sebastian Gottschall
Am 16.10.2017 um 19:59 schrieb Adrian Chadd:
Quoted 38 lines · Ben Greear
Quoted 30 lines · Benjamin Berg
Quoted 19 lines
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).Quoted 6 lines
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
if someone is interested i can provide a patch witch works as well for 998x and 9984 and usually other newer chipsets too.
but clock parameters need to be adjusted for these newer ones. the only problem is that its based on unoffical registers which arent documented and the patch for the 99xx chipsets is very different from 988x
--
Mit freundlichen Grüssen / RegardsSebastian Gottschall / CTO
Quoted 9 lines
NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 BensheimRegistergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: [email protected]
Tel.: +496251-582650 / Fax: +496251-5826565_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Am 16.10.2017 um 21:55 schrieb Ben Greear:
Quoted 10 lines · Adrian Chadd
Quoted 4 lines
hiya,
I'd honestly rather see firmware changes for wave 2 chips, as I know there's a lot more MAC changes messing up this stuff ..
For wave-1, it appears to be quite simple to modify the firmware to set the ack-cts register to a specific value (and re-set it after scanning, etc).
Quoted 5 lines
Is the wave-2 stuff that much different? I've recently hooked in my CT firmware for wave-1 to support the driver's ack/cts calculations (but without needing all the manual register twiddling). I could probably do the same for 9984 if it mattered. But, that still doesn't help stock driver/firmware users.
wave 2 has nothing todo with wave 1. the registers are different
Quoted 90 lines
Thanks,
BenQuoted 84 lines
-adrian
Quoted 47 lines · Sebastian Gottschall
Am 16.10.2017 um 19:59 schrieb Adrian Chadd:
Quoted 38 lines · Ben Greear
Quoted 30 lines · Benjamin Berg
Quoted 19 lines
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).Quoted 6 lines
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
Quoted 23 lines
if someone is interested i can provide a patch witch works as well for 998x and 9984 and usually other newer chipsets too.
but clock parameters need to be adjusted for these newer ones. the only problem is that its based on unoffical registers which arent documented and the patch for the 99xx chipsets is very different from 988x
Signature · 12 lines
Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: [email protected] Tel.: +496251-582650 / Fax: +496251-5826565_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Signature · 17 lines
Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: [email protected] Tel.: +496251-582650 / Fax: +496251-5826565 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Am 16.10.2017 um 21:12 schrieb Adrian Chadd:
Quoted 4 lines
hiya,
I'd honestly rather see firmware changes for wave 2 chips, as I know there's a lot more MAC changes messing up this stuff ..
i know. but i found out how to handle it.
Quoted 72 lines
-adrian
Quoted 64 lines · Sebastian Gottschall
Am 16.10.2017 um 19:59 schrieb Adrian Chadd:
Quoted 33 lines · Ben Greear
Quoted 27 lines · Benjamin Berg
Quoted 18 lines
Unfortunately ath10k does not generally allow modifying the coverage class
with the stock firmware and Qualcomm has so far refused to implement this
feature so that it can be properly supported in ath10k. If we however know
the registers that need to be modified for proper operation with a higher
coverage class, then we can do these modifications from the driver.This patch implements this hack for first generation cards which are based
on a core that is similar to ath9k. The registers are modified in place and
need to be re-written every time the firmware sets them. To achieve this the register status is verified after certain WMI events from the firmware.Quoted 7 lines
The coverage class may not be modified temporarily right after the card re-initializes the registers. This is for example the case during scanning.
Thanks to Sebastian Gottschall <[email protected]> for initially working on a userspace support for this. This patch wouldn't have been possible without this documentation.
Quoted 5 lines
Hello,
Do you happen to know the maximum distance that can work with this patch enabled? The register value maximum seems to be
0x3FFF, but I am not sure of the units (nor how exactly that applies to distance).Quoted 6 lines
It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs.
-adrian
if someone is interested i can provide a patch witch works as well for 998x and 9984 and usually other newer chipsets too.
but clock parameters need to be adjusted for these newer ones. the only problem is that its based on unoffical registers which arent documented and the patch for the 99xx chipsets is very different from 988x
--
Mit freundlichen Grüssen / RegardsSebastian Gottschall / CTO
NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 BensheimRegistergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: [email protected]
Tel.: +496251-582650 / Fax: +496251-5826565
Signature · 17 lines
Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: [email protected] Tel.: +496251-582650 / Fax: +496251-5826565 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k