All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware
Date: Mon, 16 Nov 2020 13:37:57 +0530	[thread overview]
Message-ID: <07d18b4fbf313ab8524dc89e3a791629@codeaurora.org> (raw)
In-Reply-To: <1605166980-29115-1-git-send-email-mkenna@codeaurora.org>

On 2020-11-12 13:12, Maharaja Kennadyrajan wrote:

Hi Kalle,

Kindly ignore this patchset as I didn't mention the version number
in the subject name of the patches in the patchlist.
I will correct this and send v3 patchset.

Regret for the inconvenience caused.


Regards,
Maha


> When add an interface immediately after removing the interface,
> vdev deletion in firmware might not have been completed.
> add vdev_delete_resp_event and wait_event_timeout to synchronize
> with firmware.
> 
> Peer creation in firmware fails if last peer deletion is still in
> progress, add wait for the event after deleting every peer from host
> driver to synchronize with firmware.
> 
> 1) add vdev delete resp event and wait event to get ack from firmware
> 2) add wait event timeout for peer delete to get ack from firmware
> 3) code clean up and replace the api 
> 'ath11k_mac_get_ar_vdev_stop_status'
>    with 'ath11k_mac_get_ar_by_vdev_id'
> 
> V2: Rebased on latest ath.git TOT - Addressed Kalle's comment.
> 
> Ritesh Singh (3):
>   ath11k: vdev delete synchronization with firmware
>   ath11k: peer delete synchronization with firmware
>   ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references
> 
>  drivers/net/wireless/ath/ath11k/core.c |  2 +
>  drivers/net/wireless/ath/ath11k/core.h |  9 ++--
>  drivers/net/wireless/ath/ath11k/mac.c  | 82 
> ++++++++++++++++------------------
>  drivers/net/wireless/ath/ath11k/mac.h  |  2 -
>  drivers/net/wireless/ath/ath11k/peer.c | 44 ++++++++++++++++--
>  drivers/net/wireless/ath/ath11k/peer.h |  2 +
>  drivers/net/wireless/ath/ath11k/wmi.c  | 81 
> ++++++++++++++++++++++++++++++---
>  drivers/net/wireless/ath/ath11k/wmi.h  |  4 ++
>  8 files changed, 166 insertions(+), 60 deletions(-)

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware
Date: Mon, 16 Nov 2020 13:37:57 +0530	[thread overview]
Message-ID: <07d18b4fbf313ab8524dc89e3a791629@codeaurora.org> (raw)
In-Reply-To: <1605166980-29115-1-git-send-email-mkenna@codeaurora.org>

On 2020-11-12 13:12, Maharaja Kennadyrajan wrote:

Hi Kalle,

Kindly ignore this patchset as I didn't mention the version number
in the subject name of the patches in the patchlist.
I will correct this and send v3 patchset.

Regret for the inconvenience caused.


Regards,
Maha


> When add an interface immediately after removing the interface,
> vdev deletion in firmware might not have been completed.
> add vdev_delete_resp_event and wait_event_timeout to synchronize
> with firmware.
> 
> Peer creation in firmware fails if last peer deletion is still in
> progress, add wait for the event after deleting every peer from host
> driver to synchronize with firmware.
> 
> 1) add vdev delete resp event and wait event to get ack from firmware
> 2) add wait event timeout for peer delete to get ack from firmware
> 3) code clean up and replace the api 
> 'ath11k_mac_get_ar_vdev_stop_status'
>    with 'ath11k_mac_get_ar_by_vdev_id'
> 
> V2: Rebased on latest ath.git TOT - Addressed Kalle's comment.
> 
> Ritesh Singh (3):
>   ath11k: vdev delete synchronization with firmware
>   ath11k: peer delete synchronization with firmware
>   ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references
> 
>  drivers/net/wireless/ath/ath11k/core.c |  2 +
>  drivers/net/wireless/ath/ath11k/core.h |  9 ++--
>  drivers/net/wireless/ath/ath11k/mac.c  | 82 
> ++++++++++++++++------------------
>  drivers/net/wireless/ath/ath11k/mac.h  |  2 -
>  drivers/net/wireless/ath/ath11k/peer.c | 44 ++++++++++++++++--
>  drivers/net/wireless/ath/ath11k/peer.h |  2 +
>  drivers/net/wireless/ath/ath11k/wmi.c  | 81 
> ++++++++++++++++++++++++++++++---
>  drivers/net/wireless/ath/ath11k/wmi.h  |  4 ++
>  8 files changed, 166 insertions(+), 60 deletions(-)

  parent reply	other threads:[~2020-11-16  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  7:42 [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware Maharaja Kennadyrajan
2020-11-12  7:42 ` Maharaja Kennadyrajan
2020-11-12  7:42 ` [PATCH 1/3] ath11k: vdev " Maharaja Kennadyrajan
2020-11-12  7:42   ` Maharaja Kennadyrajan
2020-11-12  7:42 ` [PATCH 2/3] ath11k: peer " Maharaja Kennadyrajan
2020-11-12  7:42   ` Maharaja Kennadyrajan
2020-11-12  7:43 ` [PATCH 3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references Maharaja Kennadyrajan
2020-11-12  7:43   ` Maharaja Kennadyrajan
2020-11-16  8:07 ` Maharaja Kennadyrajan [this message]
2020-11-16  8:07   ` [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware Maharaja Kennadyrajan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07d18b4fbf313ab8524dc89e3a791629@codeaurora.org \
    --to=mkenna@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.