to be triggered and cause cascading
failures. To mitigate this, initiate a get bss call in
cfg80211_connect_done itself and hold it to ensure that the BSS
instance does not get expired.
Signed-off-by: Abhishek Kumar
---
net/wireless/sme.c | 21 +
1 file changed, 13 insertions
This patch seems to address the comments on v2. Overall this patch LGTM.
Reviewed-by: Abhishek Kumar
On Tue, Feb 23, 2021 at 6:29 AM Youghandhar Chintala
wrote:
>
> Currently in the shutdown callback we wait for recovery to complete
> before freeing up the resources. This results in a
LGTM! If no one has any objections, I would be happy to see this
considered for upstream.
Reviewed-by: Abhishek Kumar
Thanks
Abhishek
On Tue, Dec 15, 2020 at 9:30 AM Youghandhar Chintala
wrote:
>
> Many wifi drivers (e.g. ath10k using qualcomm wifi chipsets)
> support silent target
ws are, or atleast what are
the challenges. As you said the task is much bigger with so many
firmware branches. As long as you feel it is scalable for coming
years, we should be good.
As far as the patch is concerned, it LGTM.
Reviewed-by: Abhishek Kumar
Thanks
Abhishek
Since using DELBA frame to APs to re-establish BA session has a
dependency on APs and also some APs may not honour the DELBA frame. I
am fine with having the disconnect/reconnect solution. The change
looks good to me.
Reviewed-by: Abhishek Kumar
Thanks
Abhishek
On Thu, Jan 28, 2021 at 12:08 AM
On Tue, Dec 15, 2020 at 9:24 AM Youghandhar Chintala
wrote:
>
> From: Rakesh Pillai
>
> Currently after the hardware restart triggered from the driver,
> the station interface connection remains intact, since a disconnect
> trigger is not sent to userspace. This can lead to a problem in
> hardwar
d=320'
Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.3.2.2-00696-QCAHLSWMTPL-1
Tested-on: QCA6174 HW3.2 WLAN.RM.4.4.1-00157-QCARMSWPZ-1
Signed-off-by: Abhishek Kumar
---
Changes in v3:
- Resurreted Patch V1 because as per discussion we do need two
fallback board names and
Hi,
> > (no changes since v1)
>
> I think you need to work on the method you're using to generate your
> patches. There are most definitely changes since v1. You described
> them in your cover letter (which you don't really need for a singleton
> patch) instead of here.
I agree, this was not int
Hi,
The patch LGTM there is small nit, though.
> +++ b/drivers/net/wireless/ath/ath10k/wmi.c
> @@ -5751,8 +5751,13 @@ void ath10k_wmi_event_service_available(struct ath10k
> *ar, struct sk_buff *skb)
> ret);
> }
>
> - ath10k_wmi_map_svc_ext(ar, arg.servic
Hi All,
The V2 patch now has good comments and probably spinning off a new V3
might be a good idea. Here are a few comments to the discussion.
In response to Doug's comment
> case WMI_TLV_TAG_FIRST_ARRAY_ENUM:
> arg->service_map_ext_len = 0;
> arg->service_map_ext = NULL;
> return 0;
Since
This patch extends ath10k_core_create_board_name function to support chip id
based BDF selection and not add provision for fallback_boardname2, thus
introducing lesser lines of code.
(no changes since v1)
Abhishek Kumar (1):
ath10k: add option for chip-id based BDF selection
drivers/net
d=320'
Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.3.2.2-00696-QCAHLSWMTPL-1
Tested-on: QCA6174 HW3.2 WLAN.RM.4.4.1-00157-QCARMSWPZ-1
Signed-off-by: Abhishek Kumar
---
(no changes since v1)
drivers/net/wireless/ath/ath10k/core.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
Apologies for the delay, was busy so could not work on V2 . I have
started working on V2 patch. Will upload by today/tomorrow.
Abhishek
On Thu, Nov 5, 2020 at 11:11 PM Kalle Valo wrote:
>
> Abhishek Kumar wrote:
>
> > In some devices difference in chip-id should be enough
Additionally tested on ath10k based non-QMI platform
Tested-on: QCA6174 HW3.2 WLAN.RM.4.4.1-00157-QCARMSWPZ-1
Tested-by: Abhishek Kumar
-Abhishek
d=320'
Signed-off-by: Abhishek Kumar
---
drivers/net/wireless/ath/ath10k/core.c | 45 +++---
1 file changed, 34 insertions(+), 11 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/core.c
b/drivers/net/wireless/ath/ath10k/core.c
index a3f15cc89a10..767bb9d6a
15 matches
Mail list logo