From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath10k: fix beamformee VHT STS capability
Date: Wed, 9 Sep 2015 12:42:58 +0300 [thread overview]
Message-ID: <87twr47wt9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1441192820-8403-1-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Wed, 2 Sep 2015 13:20:19 +0200")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> The VHT STS CAP shall be reported by firmware to host, like in case of
> QCA99x0. For QCA6174 hw family this isn't set for some reason.
> So for this particular chips, let's assume it has the ability to
> support VHT NDP in up to 4 STSs (which is true by the way).
>
> Change the published beamformee STS cap accordingly to 3 or to what
> the firmware reports.
>
> Assumption so far, it suppose to be the num_rf_chains-1, was
> completely wrong.
>
> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
Thanks, both patches applied.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] ath10k: fix beamformee VHT STS capability
Date: Wed, 9 Sep 2015 12:42:58 +0300 [thread overview]
Message-ID: <87twr47wt9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1441192820-8403-1-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Wed, 2 Sep 2015 13:20:19 +0200")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> The VHT STS CAP shall be reported by firmware to host, like in case of
> QCA99x0. For QCA6174 hw family this isn't set for some reason.
> So for this particular chips, let's assume it has the ability to
> support VHT NDP in up to 4 STSs (which is true by the way).
>
> Change the published beamformee STS cap accordingly to 3 or to what
> the firmware reports.
>
> Assumption so far, it suppose to be the num_rf_chains-1, was
> completely wrong.
>
> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
Thanks, both patches applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-09-09 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 11:20 [PATCH 1/2] ath10k: fix beamformee VHT STS capability Bartosz Markowski
2015-09-02 11:20 ` Bartosz Markowski
2015-09-02 11:20 ` [PATCH 2/2] ath10k: fix beamformer VHT sounding dimensions capability Bartosz Markowski
2015-09-02 11:20 ` Bartosz Markowski
2015-09-09 9:42 ` Kalle Valo [this message]
2015-09-09 9:42 ` [PATCH 1/2] ath10k: fix beamformee VHT STS capability Kalle Valo
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=87twr47wt9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=bartosz.markowski@tieto.com \
--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.