All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@kernel.org>, P Praneesh <quic_ppranees@quicinc.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ath11k: add LDPC FEC type in 802.11 radiotap header
Date: Mon, 20 Dec 2021 20:59:09 +0100	[thread overview]
Message-ID: <534d1f71596289581e9229c3087e2ac2f7528ebe.camel@sipsolutions.net> (raw)
In-Reply-To: <164002780766.16553.11348226804666046524.kvalo@kernel.org>

On Mon, 2021-12-20 at 19:16 +0000, Kalle Valo wrote:
> P Praneesh <quic_ppranees@quicinc.com> wrote:
> 
> > LDPC is one the FEC type advertised in msdu_start info2 for HT packet
> > type. Hence, add hardware specific callback for fetching LDPC
> > support from msdu start and enable RX_ENC_FLAG_LDPC flag while passing
> > rx status to mac80211.
> > 
> > Tested-on: IPQ8074 WLAN.HK.2.4.0.1-01467-QCAHKSWPL_SILICONZ-1
> > 
> > Signed-off-by: P Praneesh <quic_ppranees@quicinc.com>
> 
> Depends on:
> 
> 57553c3a6cfe ("mac80211: fix FEC flag in radio tap header")
> 

Technically, you could apply it, it just won't be very useful until you
have both together.

johannes

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@kernel.org>, P Praneesh <quic_ppranees@quicinc.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ath11k: add LDPC FEC type in 802.11 radiotap header
Date: Mon, 20 Dec 2021 20:59:09 +0100	[thread overview]
Message-ID: <534d1f71596289581e9229c3087e2ac2f7528ebe.camel@sipsolutions.net> (raw)
In-Reply-To: <164002780766.16553.11348226804666046524.kvalo@kernel.org>

On Mon, 2021-12-20 at 19:16 +0000, Kalle Valo wrote:
> P Praneesh <quic_ppranees@quicinc.com> wrote:
> 
> > LDPC is one the FEC type advertised in msdu_start info2 for HT packet
> > type. Hence, add hardware specific callback for fetching LDPC
> > support from msdu start and enable RX_ENC_FLAG_LDPC flag while passing
> > rx status to mac80211.
> > 
> > Tested-on: IPQ8074 WLAN.HK.2.4.0.1-01467-QCAHKSWPL_SILICONZ-1
> > 
> > Signed-off-by: P Praneesh <quic_ppranees@quicinc.com>
> 
> Depends on:
> 
> 57553c3a6cfe ("mac80211: fix FEC flag in radio tap header")
> 

Technically, you could apply it, it just won't be very useful until you
have both together.

johannes

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

  reply	other threads:[~2021-12-20 19:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 17:50 [PATCH 0/2] mac80211/ath11k: add FEC type in radiotap header P Praneesh
2021-11-30 17:50 ` P Praneesh
2021-11-30 17:50 ` [PATCH 1/2] mac80211: fix FEC flag in radio tap header P Praneesh
2021-11-30 17:50   ` P Praneesh
2021-11-30 17:50 ` [PATCH 2/2] ath11k: add LDPC FEC type in 802.11 radiotap header P Praneesh
2021-11-30 17:50   ` P Praneesh
2021-12-20 19:16   ` Kalle Valo
2021-12-20 19:16     ` Kalle Valo
2021-12-20 19:59     ` Johannes Berg [this message]
2021-12-20 19:59       ` Johannes Berg
2021-12-21  9:57       ` Kalle Valo
2021-12-21  9:57         ` Kalle Valo
2022-01-12  8:06   ` Kalle Valo
2022-01-12  8:06     ` 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=534d1f71596289581e9229c3087e2ac2f7528ebe.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_ppranees@quicinc.com \
    /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.