ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: set HE phymodes at vdev start by default
Date: Wed, 26 Jun 2019 07:54:32 +0000 (UTC)	[thread overview]
Message-ID: <20190626075432.CA4E0608CE@smtp.codeaurora.org> (raw)
In-Reply-To: <1561418955-9119-1-git-send-email-pradeepc@codeaurora.org>

Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> wrote:

> phymode cannot be classified at vdev_start as driver wont be aware of
> operating mode (11n/11ac/11ax) at this point. So setting HE phymodes
> by default corresponding to bandwidth at vdev start will prevent FW
> assert when phymode configured for the connecting peer is greater
> than the phymode configured for the VDEV. phymode for each peer is
> configured appropriately at the time of peer association.
> 
> Tested on IPQ8074.
> 
> Suggested-by: Rajkumar Manoharan <rmanohar@codeaurora.org>
> Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath11k-bringup branch of ath.git, thanks.

f9dbe2e2a22f ath11k: set HE phymodes at vdev start by default

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

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


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

      reply	other threads:[~2019-06-26  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 23:29 [PATCH] ath11k: set HE phymodes at vdev start by default Pradeep Kumar Chitrapu
2019-06-26  7:54 ` 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=20190626075432.CA4E0608CE@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=pradeepc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox