<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lwn.git/drivers/bluetooth/hci_bcm.c, branch alabaster</title>
<subtitle>Linux kernel documentation tree maintained by Jonathan Corbet</subtitle>
<id>http://mirrors.hust.edu.cn/git/lwn.git/atom?h=alabaster</id>
<link rel='self' href='http://mirrors.hust.edu.cn/git/lwn.git/atom?h=alabaster'/>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/'/>
<updated>2022-07-22T00:12:22+00:00</updated>
<entry>
<title>Bluetooth: hci_bcm: Increase host baudrate for CYW55572 in autobaud mode</title>
<updated>2022-07-22T00:12:22+00:00</updated>
<author>
<name>Hakan Jansson</name>
<email>hakan.jansson@infineon.com</email>
</author>
<published>2022-06-30T12:53:45+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=46459cb6d4e63066e227a496ae8af35ba8c0b23b'/>
<id>urn:sha1:46459cb6d4e63066e227a496ae8af35ba8c0b23b</id>
<content type='text'>
Add device specific data for max baudrate in autobaud mode. This allows the
host to use a baudrate higher than "init speed" when loading FW in autobaud
mode.

The device specific max baudrate in autobaud mode for CYW55572 is set to
921600 bps. Devices without device specific max baudrate in autobaud mode
will use init speed as before. If no device specific init speed has been
specified, it will default to the bcm_proto default 115200 bps.

The increased baud rate improves FW load time. The exact load time will
depend on the specific system and FW being used. As a rough indication,
the FW load time dropped from ~9s @ 115.2kbps to ~1.7s @ 921.6kbps in one
test.

Signed-off-by: Hakan Jansson &lt;hakan.jansson@infineon.com&gt;
Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Prevent early baudrate setting in autobaud mode</title>
<updated>2022-07-22T00:12:09+00:00</updated>
<author>
<name>Hakan Jansson</name>
<email>hakan.jansson@infineon.com</email>
</author>
<published>2022-06-30T12:45:23+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=9baee415460e602686500d825a86436daa27ac8a'/>
<id>urn:sha1:9baee415460e602686500d825a86436daa27ac8a</id>
<content type='text'>
Always prevent trying to set device baudrate before calling setup() when
using autobaud mode.

This was previously happening for devices which had device specific data
with member no_early_set_baudrate set to 0.

Signed-off-by: Hakan Jansson &lt;hakan.jansson@infineon.com&gt;
Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Add DT compatible for CYW55572</title>
<updated>2022-07-22T00:11:56+00:00</updated>
<author>
<name>Hakan Jansson</name>
<email>hakan.jansson@infineon.com</email>
</author>
<published>2022-06-30T12:45:22+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=f8cad62002a7699fd05a23b558b980b5a77defe0'/>
<id>urn:sha1:f8cad62002a7699fd05a23b558b980b5a77defe0</id>
<content type='text'>
CYW55572 is a Wi-Fi + Bluetooth combo device from Infineon.

Signed-off-by: Hakan Jansson &lt;hakan.jansson@infineon.com&gt;
Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Add BCM4349B1 variant</title>
<updated>2022-07-22T00:06:36+00:00</updated>
<author>
<name>Ahmad Fatoum</name>
<email>a.fatoum@pengutronix.de</email>
</author>
<published>2022-05-24T05:56:41+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=4f17c2b6694d0c4098f33b07ee3a696976940aa5'/>
<id>urn:sha1:4f17c2b6694d0c4098f33b07ee3a696976940aa5</id>
<content type='text'>
The BCM4349B1, aka CYW/BCM89359, is a WiFi+BT chip and its Bluetooth
portion can be controlled over serial.

Two subversions are added for the chip, because ROM firmware reports
002.002.013 (at least for the chips I have here), while depending on
patchram firmware revision, either 002.002.013 or 002.002.014 is
reported.

Signed-off-by: Ahmad Fatoum &lt;a.fatoum@pengutronix.de&gt;
Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Add support for FW loading in autobaud mode</title>
<updated>2022-07-22T00:04:38+00:00</updated>
<author>
<name>Hakan Jansson</name>
<email>hakan.jansson@infineon.com</email>
</author>
<published>2022-05-30T15:02:18+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=af35e28f0fea877832fa27802bc862b2a912f32a'/>
<id>urn:sha1:af35e28f0fea877832fa27802bc862b2a912f32a</id>
<content type='text'>
Use the presence of a DT property, "brcm,requires-autobaud-mode", to enable
startup in autobaud mode. If the property is present, the device is started
in autobaud mode by asserting RTS (BT_UART_CTS_N) prior to powering on the
device.

Also prevent the use of unsupported commands for devices started in
autobaud mode. Only a limited subset of HCI commands are supported in
autobaud mode.

Some devices (e.g. CYW5557x) require autobaud mode to enable FW loading.
Autobaud mode can also be required on some boards where the controller
device is using a non-standard baud rate in normal mode when first powered
on.

Signed-off-by: Hakan Jansson &lt;hakan.jansson@infineon.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Add the Asus TF103C to the bcm_broken_irq_dmi_table</title>
<updated>2022-03-18T16:12:08+00:00</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-02-28T11:38:41+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=27e8527e006f1f4281adc335cf7aa744f649f398'/>
<id>urn:sha1:27e8527e006f1f4281adc335cf7aa744f649f398</id>
<content type='text'>
The DSDT for the Asus TF103C specifies a IOAPIC IRQ for the HCI -&gt; host IRQ
but this is not correct. Unlike the previous entries in the table, this
time the correct GPIO to use instead is known; and the TF103C is battery
powered making runtime-pm support more important.

Extend the bcm_broken_irq_dmi_table mechanism to allow specifying the right
GPIO instead of just always disabling runtime-pm and add an entry to it for
the Asus TF103C.

Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: add BCM43430A0 &amp; BCM43430A1</title>
<updated>2022-03-04T15:57:13+00:00</updated>
<author>
<name>Luca Weiss</name>
<email>luca@z3ntu.xyz</email>
</author>
<published>2022-02-25T20:41:38+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=01da346c1802f046496845cccd7c871ca35f24a7'/>
<id>urn:sha1:01da346c1802f046496845cccd7c871ca35f24a7</id>
<content type='text'>
Add the compatible for BCM43430A0 bluetooth used in lg-lenok and
BCM43430A1 used in asus-sparrow.

Signed-off-by: Luca Weiss &lt;luca@z3ntu.xyz&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Check for error irq</title>
<updated>2022-01-06T13:52:11+00:00</updated>
<author>
<name>Jiasheng Jiang</name>
<email>jiasheng@iscas.ac.cn</email>
</author>
<published>2021-12-24T02:53:18+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=b38cd3b42fba66cc538edb9cf77e07881f43f8e2'/>
<id>urn:sha1:b38cd3b42fba66cc538edb9cf77e07881f43f8e2</id>
<content type='text'>
For the possible failure of the platform_get_irq(), the returned irq
could be error number and will finally cause the failure of the
request_irq().
Consider that platform_get_irq() can now in certain cases return
-EPROBE_DEFER, and the consequences of letting request_irq() effectively
convert that into -EINVAL, even at probe time rather than later on.
So it might be better to check just now.

Fixes: 0395ffc1ee05 ("Bluetooth: hci_bcm: Add PM for BCM devices")
Signed-off-by: Jiasheng Jiang &lt;jiasheng@iscas.ac.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Remove duplicated entry in OF table</title>
<updated>2021-10-25T13:07:13+00:00</updated>
<author>
<name>Paul Cercueil</name>
<email>paul@crapouillou.net</email>
</author>
<published>2021-10-23T10:10:27+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=2d6d4089ea894cf8eb481b10769160a35c181360'/>
<id>urn:sha1:2d6d4089ea894cf8eb481b10769160a35c181360</id>
<content type='text'>
The entry "brcm,bcm4330-bt" was listed twice in the table.

Signed-off-by: Paul Cercueil &lt;paul@crapouillou.net&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_bcm: Fix kernel doc comments</title>
<updated>2021-08-04T14:37:12+00:00</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2021-08-04T14:28:37+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=67cbdd74c4cba378a715003923fc418a10349fae'/>
<id>urn:sha1:67cbdd74c4cba378a715003923fc418a10349fae</id>
<content type='text'>
Kernel doc validator complains about few missed parameter descriptions.
Fill the gap by describing them.

Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
</feed>
