From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Lingbo Kong <quic_lingbok@quicinc.com>, <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/4] wifi: ath12k: Add Support for enabling or disabling specific features based on ACPI bitflag
Date: Wed, 17 Jul 2024 09:52:49 -0700 [thread overview]
Message-ID: <cf9e8dee-092a-4212-8d64-2a8689be6fa2@quicinc.com> (raw)
In-Reply-To: <20240717111023.78798-3-quic_lingbok@quicinc.com>
On 7/17/2024 4:10 AM, Lingbo Kong wrote:
> Currently, ath12k does not support enable or disable specific features by
> ACPI bitflag.
>
> To address this issue, obtain the ACPI bitflag value and use it to
> selectively enable or disable specific features.
>
> This patch will not affect QCN9274, because only WCN7850 supports ACPI.
>
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
>
> Signed-off-by: Lingbo Kong <quic_lingbok@quicinc.com>
Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
next prev parent reply other threads:[~2024-07-17 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 11:10 [PATCH 0/4] wifi: ath12k: Add new features to ACPI Lingbo Kong
2024-07-17 11:10 ` [PATCH 1/4] wifi: ath12k: Add support for obtaining the buffer type ACPI function bitmap Lingbo Kong
2024-07-17 16:52 ` Jeff Johnson
2024-07-17 11:10 ` [PATCH 2/4] wifi: ath12k: Add Support for enabling or disabling specific features based on ACPI bitflag Lingbo Kong
2024-07-17 16:52 ` Jeff Johnson [this message]
2024-07-17 20:36 ` kernel test robot
2024-07-17 21:44 ` Jeff Johnson
2024-07-18 2:22 ` Lingbo Kong
2024-07-18 2:31 ` Jeff Johnson
2024-07-17 22:23 ` kernel test robot
2024-07-17 11:10 ` [PATCH 3/4] wifi: ath12k: Adjust the timing to access ACPI table Lingbo Kong
2024-07-17 16:52 ` Jeff Johnson
2024-07-17 11:10 ` [PATCH 4/4] wifi: ath12k: Add support for reading variant from ACPI to download board data file Lingbo Kong
2024-07-17 16:52 ` Jeff Johnson
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=cf9e8dee-092a-4212-8d64-2a8689be6fa2@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_lingbok@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox