Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kalle Valo <kvalo@kernel.org>
To:     Bagas Sanjaya <bagasdotme@gmail.com>
Cc:     Jeff Johnson <quic_jjohnson@quicinc.com>,
        =?utf-8?Q?Fran=C3=A7ois?= Armand <fanf42@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux ath11k <ath11k@lists.infradead.org>,
        Linux Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed
 to send headers (or body or access otp area)
References: <a669d2d5-fee8-5841-eb5f-b7d047d3cdb2@gmail.com>
Date:   Mon, 21 Aug 2023 08:02:18 +0300
In-Reply-To: <a669d2d5-fee8-5841-eb5f-b7d047d3cdb2@gmail.com> (Bagas Sanjaya's
        message of "Fri, 18 Aug 2023 17:16:17 +0700")
Message-ID: <87il99j8dh.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Hi,
>
> I notice a bug report on Bugzilla [1]. Quoting from it:
>
>> Hello,
>> 
>> (Sorry by advance if it's not the correct place to discuss that, but
>> I tried other place like my distro kernel forum
>> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive
>> chat, etc and nobody was able to help).
>> 
>> [1] == Short summary ==
>> 
>> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card
>> (which is actually reported by lspci as QCNFA765) and bluetooth
>> never worked on it, failing to load the rampatch with "failed to
>> send header" or "failed to send body" or "Failed to access otp area
>> (-71)".
>> 
>> Other people reports bluetooth as working
>> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3)
>> and a work friend has a T16 AMD gen1 which seems to have exactly the
>> same chipset and work flowlessly. So perhaps it's an hardware issue,
>> but I don't know how to qualify it if so.
>> 
>> => How can this be further qualified/debuged/workarounded?
>> 
>> Any help, even RTFM pointing to corresponding manuals would be very
>> much appreciated.

This looks like a bluetooth bug so not related to ath11k (which is a
Wi-Fi driver).

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches