From: Kalle Valo <kvalo@kernel.org>
To: Rameshkumar Sundaram <quic_ramess@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: Allow driver initialization for WoW unsupported devices
Date: Wed, 26 Jun 2024 21:39:32 +0300 [thread overview]
Message-ID: <87r0cjh7kr.fsf@kernel.org> (raw)
In-Reply-To: <20240626024257.709460-1-quic_ramess@quicinc.com> (Rameshkumar Sundaram's message of "Wed, 26 Jun 2024 08:12:57 +0530")
Rameshkumar Sundaram <quic_ramess@quicinc.com> writes:
> Currently during driver initialization, mac registration is allowed
> only for devices that advertise WMI_TLV_SERVICE_WOW, but QCN9274
> doesn't support WoW and hence mac registration is aborted and driver
> is de-initialized.
I changed the title and this paragraph to describe more that we are
fixing a regression here.
> Allow mac registration to proceed without WoW Support for devices
> that don't advertise WMI_TLV_SERVICE_WOW.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
>
> Cc: stable@vger.kernel.org
> Fixes: 4a3c212eee0e ("wifi: ath12k: add basic WoW functionalities")
Luckily commit 4a3c212eee0e is only in ath-next, and not in any other
tree yet, so no need to cc stable. We need to cc stable when the bug is
in any of the official releases (v6.10 etc). So I dropped it.
Please check:
https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/commit/?h=pending&id=dbe2f0503e5fa9394e6b4e4f442adae89cec4cc7
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-06-26 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 2:42 [PATCH] wifi: ath12k: Allow driver initialization for WoW unsupported devices Rameshkumar Sundaram
2024-06-26 18:00 ` Jeff Johnson
2024-06-26 18:39 ` Kalle Valo [this message]
2024-06-26 18:44 ` Jeff Johnson
2024-06-27 5:00 ` Rameshkumar Sundaram
2024-06-27 16:22 ` 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=87r0cjh7kr.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_ramess@quicinc.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox