From: Ilya K <me@0upti.me>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>, tiwai@suse.de
Cc: ath11k@lists.infradead.org, jeff.johnson@oss.qualcomm.com,
linux-wireless@vger.kernel.org, mpearson-lenovo@squebb.ca
Subject: Re: [PATCH] wifi: ath11k: Add quirk entry for Thinkpad T14s Gen3 AMD
Date: Thu, 5 Mar 2026 15:46:15 +0300 [thread overview]
Message-ID: <facd539e-916f-4511-bc25-61c79433aed7@0upti.me> (raw)
In-Reply-To: <c63b4cc0-3157-432c-a83b-c638e8c8d665@oss.qualcomm.com>
On 2026-01-12 05:37, Baochen Qiang wrote:
>
>
> On 1/12/2026 10:35 AM, Baochen Qiang wrote:
>>
>>
>> On 1/11/2026 6:47 PM, Ilya K wrote:
>>> Hey folks,
>>>
>>> Sorry for bumping an old-ish thread, but I've had the same issue on a T13 Gen3 machine as well (model 21CG), and there seems to be no better solution in sight.
>>>
>>> Also, here's another instance of what I'm pretty sure is the same issue: https://lore.kernel.org/ath11k/6268b094-5a40-40d8-8461-9c9b0f9e1ae3@oss.qualcomm.com/T/#t
>>>
>>> Can this get landed at least as a temporary workaround? Also, should I submit the 21CG quirk as a separate patch?
>>
>> I had an off list discussion with Takashi, and based on the logs collected I don't think
>> this is not a suspend/resume issue, or even this is not a STA side issue.
>
> my bad:
>
> s/this is not/this is/
>
>>
>> Before we conclude whether your issue is the same or not, can you please describe your
>> issue in detail? specifically is it an unexpected wakeup or is it reconnection failure
>> after a normal wakeup?
>>
>
I've had a bit of an off list conversation with Baochen about this a while ago, but I just saw https://lore.kernel.org/ath11k/20260214212452.782265-38-sashal@kernel.org/T/#u landed, and I still haven't had time to get more data on the affected machine, but it has been rock solid with the quirk added locally, across updated and different APs. Maybe it makes sense to add the quirk at least for the time being? I'll try to get some debug time in the coming weeks, but free time is hard to come by lately :(
prev parent reply other threads:[~2026-03-05 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 13:47 [PATCH] wifi: ath11k: Add quirk entry for Thinkpad T14s Gen3 AMD Takashi Iwai
2025-11-24 15:13 ` Mark Pearson
2025-11-24 15:32 ` Takashi Iwai
2025-11-24 15:52 ` Mark Pearson
2025-11-25 6:58 ` Takashi Iwai
2025-11-25 2:28 ` Baochen Qiang
2025-11-25 6:57 ` Takashi Iwai
2025-11-25 7:25 ` Baochen Qiang
2025-11-25 7:40 ` Takashi Iwai
2026-01-11 10:47 ` Ilya K
2026-01-12 2:35 ` Baochen Qiang
2026-01-12 2:37 ` Baochen Qiang
2026-03-05 12:46 ` Ilya K [this message]
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=facd539e-916f-4511-bc25-61c79433aed7@0upti.me \
--to=me@0upti.me \
--cc=ath11k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=tiwai@suse.de \
/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