On Mon, Dec 25, 2023 at 09:26:05PM +0100, Paul Menzel wrote:
> Thank you very much for the patch. I am adding Johan to Cc field.
Thanks for the report. Guess I could use a break from the proverbial
eggnog.
> Am 25.12.23 um 21:01 schrieb Felix Zhang:
> > Starting v6.5, Bluetooth does not work at all on my T2 MacBookAir9,1
> >
> > with the BCM4377 chip. When I boot up the computer, go into
>
> Somehow a blank line snug in above.
>
> > bluetoothctl, and then try to run commands like scan on, show, list,
> > it returns "No default controller available." I have tried reloading
> > the
>
> It’d be great if you reflowed for 75 characters per line (also below).
>
> > kernel module, in which the log outputs "{Added,Removed} hci0
> > (unconfigured)." With this patch, I am able to use Bluetooth as
> > normal
> > without any errors regarding hci0 being unconfigured. However, an
> > issue is still present where sometimes hci_bcm4377 will have to be
> > reloaded in order to get bluetooth to work. I believe this was still
> > present before the previously mentioned commit.
> >
> > Due to the bit HCI_QUIRK_USE_BDADDR_PROPERTY being always set in
> > drivers/bluetooth/hci_bcm4377.c (line 2371), the chip would be left
> > unconfigured on kernels compiled after commit 6945795bc81a
> > ("Bluetooth:
> > fix use-bdaddr-property quirk") due to a change in its logic. On the
> > M1 Macs, the device would be configured in the devicetree. However,
> > that is not the case on T2 Macs. Because the bluetooth adapter is
> > left
> > unconfigured, it is not usable in the operating system. In order to
> > circumvent this issue, a flag is added to prevent the bit from being
> > set on the BCM4377, while setting it on the other devices.
The commit you tracked this down to restored the original semantics for
HCI_QUIRK_USE_BDADDR_PROPERTY, which means that it should only be set
for devices with an invalid address.
The Broadcom BCM4377 driver has so far been setting this flag
unconditionally which now potentially results in also valid addresses
being marked as invalid.
I've just sent a patch that makes sure to only mark invalid addresses as
invalid:
https://lore.kernel.org/lkml/20231227101003.10534-1-johan+linaro@xxxxxxxxxx/
Note however that the flag still needs to be set in case your device
lacks storage for a unique device address so you cannot simply drop it
for some device classes as you do below (unless you are certain that
these devices will always have a valid address).
Devices without a valid address starts in an unconfigured state and
cannot be used until userspace has provided an address (e.g. using
btmgmt):
btmgmt --index 0 public-addr 00:11:22:33:44:55
> > Fixes: 6945795bc81a ("Bluetooth: fix use-bdaddr-property quirk")
> > Signed-off-by: Felix Zhang <mrman@xxxxxxxxxxxxx>
> > @@ -2368,7 +2369,8 @@ static int bcm4377_probe(struct pci_dev *pdev,
> > const struct pci_device_id *id)
> > hdev->set_bdaddr = bcm4377_hci_set_bdaddr;
> > hdev->setup = bcm4377_hci_setup;
> >
> > - set_bit(HCI_QUIRK_USE_BDADDR_PROPERTY, &hdev->quirks);
> > + if (bcm4377->hw->use_bdaddr_property)
> > + set_bit(HCI_QUIRK_USE_BDADDR_PROPERTY, &hdev->quirks);
> > if (bcm4377->hw->broken_mws_transport_config)
> > set_bit(HCI_QUIRK_BROKEN_MWS_TRANSPORT_CONFIG, &hdev-
> >> quirks);
> > if (bcm4377->hw->broken_ext_scan)
> > @@ -2465,6 +2467,7 @@ static const struct bcm4377_hw
> > bcm4377_hw_variants[] = {
> > .has_bar0_core2_window2 = true,
> > .broken_mws_transport_config = true,
> > .broken_le_coded = true,
> > + .use_bdaddr_property = true,
> > .send_calibration = bcm4378_send_calibration,
> > .send_ptb = bcm4378_send_ptb,
> > },
> > @@ -2479,6 +2482,7 @@ static const struct bcm4377_hw
> > bcm4377_hw_variants[] = {
> > .clear_pciecfg_subsystem_ctrl_bit19 = true,
> > .broken_mws_transport_config = true,
> > .broken_le_coded = true,
> > + .use_bdaddr_property = true,
> > .send_calibration = bcm4387_send_calibration,
> > .send_ptb = bcm4378_send_ptb,
> > },
Back to the eggnog.
Johan
