All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Surabhi Vishnoi <svishnoi@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Add a condtion to fill the LDPC capability correctly
Date: Mon, 04 Feb 2019 17:32:56 +0200	[thread overview]
Message-ID: <877eefefh3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1548999262-25353-1-git-send-email-svishnoi@codeaurora.org> (Surabhi Vishnoi's message of "Fri, 1 Feb 2019 11:04:22 +0530")

Surabhi Vishnoi <svishnoi@codeaurora.org> writes:

> The firmware advertises the LDPC support information for HT in
> HT capability info in the wmi service ready event. To provide
> granularity, firmware now advertises WMI_HT_CAP_RX_LDPC and
> WMI_HT_CAP_TX_LDPC separately. To support LDPC, host should
> also check for WMI_HT_CAP_RX_LDPC and WMI_HT_CAP_TX_LDPC in HT
> capabilities.
>
> Add a condition to existing logic in host to know whether firmware
> supports LDPC or not.
>
> Tested HW: WCN3990
> Tested SW: WLAN.HL.2.0

Can you give exact firmware version you tested, please? I'll add it to
the commit log.

I'll also fix the typo "condtion" in the title.

-- 
Kalle Valo

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

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Surabhi Vishnoi <svishnoi@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: Add a condtion to fill the LDPC capability correctly
Date: Mon, 04 Feb 2019 17:32:56 +0200	[thread overview]
Message-ID: <877eefefh3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1548999262-25353-1-git-send-email-svishnoi@codeaurora.org> (Surabhi Vishnoi's message of "Fri, 1 Feb 2019 11:04:22 +0530")

Surabhi Vishnoi <svishnoi@codeaurora.org> writes:

> The firmware advertises the LDPC support information for HT in
> HT capability info in the wmi service ready event. To provide
> granularity, firmware now advertises WMI_HT_CAP_RX_LDPC and
> WMI_HT_CAP_TX_LDPC separately. To support LDPC, host should
> also check for WMI_HT_CAP_RX_LDPC and WMI_HT_CAP_TX_LDPC in HT
> capabilities.
>
> Add a condition to existing logic in host to know whether firmware
> supports LDPC or not.
>
> Tested HW: WCN3990
> Tested SW: WLAN.HL.2.0

Can you give exact firmware version you tested, please? I'll add it to
the commit log.

I'll also fix the typo "condtion" in the title.

-- 
Kalle Valo

  reply	other threads:[~2019-02-04 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  5:34 [PATCH] ath10k: Add a condtion to fill the LDPC capability correctly Surabhi Vishnoi
2019-02-01  5:34 ` Surabhi Vishnoi
2019-02-04 15:32 ` Kalle Valo [this message]
2019-02-04 15:32   ` Kalle Valo
     [not found]   ` <b14e2139c794201664a49d36cc28ab48@codeaurora.org>
2019-02-07  9:10     ` Kalle Valo
2019-02-07  9:10       ` Kalle Valo
2019-02-07 14:57 ` Kalle Valo
2019-02-07 14:57 ` 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=877eefefh3.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=svishnoi@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.