All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Tamizh Chelvam <tamizhr@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Govindaraj Saminathan <gsamin@codeaurora.org>,
	Tamizh Chelvam <tamizhr@codeaurora.org>
Subject: Re: [PATCH] ath11k: config reorder queue for all tids during peer setup
Date: Wed, 11 Mar 2020 16:44:39 +0000 (UTC)	[thread overview]
Message-ID: <20200311164439.ABB36C43636@smtp.codeaurora.org> (raw)
In-Reply-To: <1581646724-23098-1-git-send-email-tamizhr@codeaurora.org>

Tamizh Chelvam <tamizhr@codeaurora.org> wrote:

> Currently rx tid setup is happening for TID 0 and TID 16
> during peer setup. And if other TID packets received for
> the peer it will be redirected to rx error ring and not through
> reo ring. And this rx tid configuration cannot be done
> in the rx error ring path since it is a atomic context.
> So moving the rx tid setup for all tids during the peer setup.
> This is required to enable PN offload functionality to route
> all packets through reo ring.
> 
> Co-developed-by: Tamizh Chelvam <tamizhr@codeaurora.org>
> Signed-off-by: Tamizh Chelvam <tamizhr@codeaurora.org>
> Signed-off-by: Govindaraj Saminathan <gsamin@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath-next branch of ath.git, thanks.

a36adf54cbc8 ath11k: config reorder queue for all tids during peer setup

-- 
https://patchwork.kernel.org/patch/11381557/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2020-03-11 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14  2:18 [PATCH] ath11k: config reorder queue for all tids during peer setup Tamizh Chelvam
2020-02-14  2:18 ` Tamizh Chelvam
2020-03-11 16:44 ` Kalle Valo
2020-03-11 16:44 ` Kalle Valo [this message]

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=20200311164439.ABB36C43636@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=gsamin@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tamizhr@codeaurora.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.