Bluetooth: fix invalid-bdaddr quirk for non-persistent setup
authorJohan Hovold <johan+linaro@kernel.org>
Wed, 31 May 2023 09:04:23 +0000 (11:04 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 19 Jul 2023 14:22:02 +0000 (16:22 +0200)
commit018b12ff1661f5542133091daf740b1408337bf3
tree1257440d5a0489e2af15bbd89e9c1fe214465987
parent102f3555cebe11a145a3ee4468142aeb178501e7
Bluetooth: fix invalid-bdaddr quirk for non-persistent setup

[ Upstream commit 0cb7365850bacb8c2a9975cae672d65714d8daa1 ]

Devices that lack persistent storage for the device address can indicate
this by setting the HCI_QUIRK_INVALID_BDADDR which causes the controller
to be marked as unconfigured until user space has set a valid address.

Once configured, the device address must be set on every setup for
controllers with HCI_QUIRK_NON_PERSISTENT_SETUP to avoid marking the
controller as unconfigured and requiring the address to be set again.

Fixes: 740011cfe948 ("Bluetooth: Add new quirk for non-persistent setup settings")
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
net/bluetooth/hci_sync.c