From: Johan Hovold <johan+linaro@kernel.org>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Matthias Kaehlcke <mka@chromium.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH RESEND 0/2] Bluetooth: fix bdaddr quirks
Date: Wed, 31 May 2023 11:04:22 +0200 [thread overview]
Message-ID: <20230531090424.3187-1-johan+linaro@kernel.org> (raw)
These patches fix a couple of issues with the two bdaddr quirks:
The first one allows HCI_QUIRK_INVALID_BDADDR to be used with
HCI_QUIRK_NON_PERSISTENT_SETUP.
The second patch restores the original semantics of the
HCI_QUIRK_USE_BDADDR_PROPERTY so that the controller is marked as
unconfigured when no device address is specified in the devicetree (as
the quirk is documented to work).
This specifically makes sure that Qualcomm HCI controllers such as
wcn6855 found on the Lenovo X13s are marked as unconfigured until user
space has provided a valid address.
Long term, the HCI_QUIRK_USE_BDADDR_PROPERTY should probably be dropped
in favour of HCI_QUIRK_INVALID_BDADDR and always checking the devicetree
property.
Johan
Johan Hovold (2):
Bluetooth: fix invalid-bdaddr quirk for non-persistent setup
Bluetooth: fix use-bdaddr-property quirk
net/bluetooth/hci_sync.c | 30 +++++++++++-------------------
1 file changed, 11 insertions(+), 19 deletions(-)
--
2.39.3
next reply other threads:[~2023-05-31 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:04 Johan Hovold [this message]
2023-05-31 9:04 ` [PATCH RESEND 1/2] Bluetooth: fix invalid-bdaddr quirk for non-persistent setup Johan Hovold
2023-05-31 9:04 ` [PATCH RESEND 2/2] Bluetooth: fix use-bdaddr-property quirk Johan Hovold
[not found] ` <CGME20230601220156eucas1p21caabcf02509fce7eb26f973704980f9@eucas1p2.samsung.com>
2023-06-01 22:01 ` Marek Szyprowski
2023-06-01 23:43 ` Luiz Augusto von Dentz
2023-06-02 8:21 ` Johan Hovold
2023-07-07 9:41 ` Amit Pundir
2023-07-07 11:08 ` Johan Hovold
2023-07-07 13:42 ` Amit Pundir
2023-07-10 11:44 ` Johan Hovold
2023-07-10 12:22 ` Amit Pundir
2023-07-25 9:41 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-25 14:24 ` Amit Pundir
2023-07-08 14:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20230531090424.3187-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).