From: Johan Hovold <johan@kernel.org>
To: Steev Klimaszewski <steev@kali.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Sven Peter <sven@svenpeter.dev>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org,
Mark Pearson <markpearson@lenovo.com>,
Tim Jiang <quic_tjiang@quicinc.com>
Subject: Re: [PATCH v5 2/4] Bluetooth: hci_qca: Add support for QTI Bluetooth chip wcn6855
Date: Tue, 14 Mar 2023 14:16:00 +0100 [thread overview]
Message-ID: <ZBBzkMd0hHYOz8Vd@hovoldconsulting.com> (raw)
In-Reply-To: <ZBBP/S8OM0t6p57E@hovoldconsulting.com>
On Tue, Mar 14, 2023 at 11:44:14AM +0100, Johan Hovold wrote:
> On Sun, Mar 12, 2023 at 10:18:48PM -0500, Steev Klimaszewski wrote:
> > Works, but, not quite well, and with the nvm bits from Tim's patch, we
> > end up getting closer? I think that is the best way to put it. With
> > what we currently have, we end up loading hpnv21.bin for our nvm patch
> > file, however, we actually want (at least on my Thinkpad X13s) the
> > .b8c file from the Windows partition for our nvm patch; With the b8c
> > file symlinked to .bin with just my patch set, I am able to connect a
> > pair of Air Pods Gen1 to the ThinkPad and play back audio, as well as
> > use them for input. With the .bin file that comes from
> > linux-firmware, they will still connect, however, they will randomly
> > disconnect, as well as the audio output is all garbled.
>
> Hmm. Ok, but then we need to ask Lenovo and Qualcomm to release the
> firmware files we need for the X13s. Until then using your patch and
> "hpnv21.bin" at least works to some extent.
>
> I could connect to one bluetooth speaker without noticing any problems,
> but I did indeed get some garbled output when connecting to another. I
> have not tried the .b8c file yet though, so this could possibly be some
> other incompatibility issue.
I just tried with the hpnv21.b8c from the (somewhat old) windows
installation on my x13s, but the bluetooth speaker that produced garbled
output with the firmware from linux-firmware still does so with the
windows file.
Johan
next prev parent reply other threads:[~2023-03-14 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 2:09 [PATCH v5 0/4] Add WCN6855 Bluetooth support Steev Klimaszewski
2023-02-09 2:09 ` [PATCH v5 1/4] dt-bindings: net: Add WCN6855 Bluetooth Steev Klimaszewski
2023-02-09 2:09 ` [PATCH v5 2/4] Bluetooth: hci_qca: Add support for QTI Bluetooth chip wcn6855 Steev Klimaszewski
2023-02-10 17:05 ` Bjorn Andersson
2023-02-22 8:03 ` Johan Hovold
2023-03-09 17:09 ` Johan Hovold
2023-03-09 20:24 ` Steev Klimaszewski
2023-03-10 7:27 ` Johan Hovold
2023-03-13 3:18 ` Steev Klimaszewski
2023-03-14 10:44 ` Johan Hovold
2023-03-14 13:16 ` Johan Hovold [this message]
2023-02-09 2:09 ` [PATCH v5 3/4] arm64: dts: qcom: sc8280xp: Define uart2 Steev Klimaszewski
2023-03-09 17:12 ` Johan Hovold
2023-02-09 2:09 ` [PATCH v5 4/4] arm64: dts: qcom: thinkpad-x13s: Add bluetooth Steev Klimaszewski
2023-03-09 17:25 ` Johan Hovold
2023-03-09 20:07 ` Steev Klimaszewski
2023-03-10 7:09 ` Johan Hovold
2023-02-10 17:09 ` [PATCH v5 0/4] Add WCN6855 Bluetooth support Bjorn Andersson
2023-04-05 4:09 ` Bjorn Andersson
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=ZBBzkMd0hHYOz8Vd@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=markpearson@lenovo.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_tjiang@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=steev@kali.org \
--cc=sven@svenpeter.dev \
/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