<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/bluetooth, branch v5.4</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.4</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.4'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2019-09-15T12:17:27Z</updated>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net</title>
<updated>2019-09-15T12:17:27Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2019-09-15T12:17:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=aa2eaa8c272a3211dec07ce9c6c863a7e355c10e'/>
<id>urn:sha1:aa2eaa8c272a3211dec07ce9c6c863a7e355c10e</id>
<content type='text'>
Minor overlapping changes in the btusb and ixgbe drivers.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btusb: Use cmd_timeout to reset Realtek device</title>
<updated>2019-09-05T15:32:28Z</updated>
<author>
<name>Alex Lu</name>
<email>alex_lu@realsil.com.cn</email>
</author>
<published>2019-09-05T02:36:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d7ef0d1e39685b38c97b30daa6de0d50df004839'/>
<id>urn:sha1:d7ef0d1e39685b38c97b30daa6de0d50df004839</id>
<content type='text'>
Realtek Bluetooth controller provides a BT_DIS reset pin for hardware
reset of it. The cmd_timeout is helpful on Realtek bluetooth controller
where the firmware gets stuck.

Signed-off-by: Alex Lu &lt;alex_lu@realsil.com.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btrtl: Fix an issue that failing to download the FW which size is over 32K bytes</title>
<updated>2019-09-05T15:27:32Z</updated>
<author>
<name>Max Chou</name>
<email>max.chou@realtek.com</email>
</author>
<published>2019-09-05T05:21:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cf0d9a705d81a0f581865cefe0880f29589dd06f'/>
<id>urn:sha1:cf0d9a705d81a0f581865cefe0880f29589dd06f</id>
<content type='text'>
Fix the issue that when the FW size is 32K+, it will fail for the download
process because of the incorrect index.

When firmware patch length is over 32K, "dl_cmd-&gt;index" may &gt;= 0x80. It
will be thought as "data end" that download process will not complete.
However, driver should recount the index from 1.

Signed-off-by: Max Chou &lt;max.chou@realtek.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btrtl: Remove trailing newline from calls to rtl_dev macros</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Alex Lu</name>
<email>alex_lu@realsil.com.cn</email>
</author>
<published>2019-08-31T08:46:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f1300c0340872d7d02617f439433d70c6f47700f'/>
<id>urn:sha1:f1300c0340872d7d02617f439433d70c6f47700f</id>
<content type='text'>
These printing macros already add a trailing newline, so drop these
unnecessary additional newlines.

Signed-off-by: Alex Lu &lt;alex_lu@realsil.com.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btrtl: Remove redundant prefix from calls to rtl_dev macros</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Alex Lu</name>
<email>alex_lu@realsil.com.cn</email>
</author>
<published>2019-08-31T08:41:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d182215d2fb9e58a7637efc937fa11dc15cf7a84'/>
<id>urn:sha1:d182215d2fb9e58a7637efc937fa11dc15cf7a84</id>
<content type='text'>
the rtl: or RTL: prefix in the string is pointless. The rtl_dev_* macros
already does that.

Signed-off-by: Alex Lu &lt;alex_lu@realsil.com.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btrtl: Add firmware version print</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Alex Lu</name>
<email>alex_lu@realsil.com.cn</email>
</author>
<published>2019-08-31T08:36:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=240b64a83165dde816664b50900aa12f1db92359'/>
<id>urn:sha1:240b64a83165dde816664b50900aa12f1db92359</id>
<content type='text'>
This patch is used to print fw version for debug convenience

Signed-off-by: Alex Lu &lt;alex_lu@realsil.com.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: btrtl: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Alex Lu</name>
<email>alex_lu@realsil.com.cn</email>
</author>
<published>2019-08-30T12:02:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=65251e2e0ad379d89f5784626b8c40ff62220d8b'/>
<id>urn:sha1:65251e2e0ad379d89f5784626b8c40ff62220d8b</id>
<content type='text'>
Realtek Bluetooth controllers can do both LE scan and BR/EDR inquiry
at once, need to set HCI_QUIRK_SIMULTANEOUS_DISCOVERY quirk.

Signed-off-by: Alex Lu &lt;alex_lu@realsil.com.cn&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth: hci_qca: wait for Pre shutdown complete event before sending the Power off pulse</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Harish Bandi</name>
<email>c-hbandi@codeaurora.org</email>
</author>
<published>2019-08-30T12:28:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=010376ab7fd788a0eddb86b6de5869b3045b97e3'/>
<id>urn:sha1:010376ab7fd788a0eddb86b6de5869b3045b97e3</id>
<content type='text'>
When SoC receives pre shut down command, it share the same
with other COEX shared clients. So SoC needs a short time
after sending VS pre shutdown command before turning off
the regulators and sending the power off pulse. Along with
short delay, needs to wait for command complete event for
Pre shutdown VS command

Signed-off-by: Harish Bandi &lt;c-hbandi@codeaurora.org&gt;
Reviewed-by: Balakrishna Godavarthi &lt;bgodavar@codeaurora.org&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>bluetooth: hci_bcm: Give more time to come out of reset</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Ondrej Jirman</name>
<email>megous@megous.com</email>
</author>
<published>2019-08-23T10:31:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=16946de5905fff243c1e4415c4565803945e8c47'/>
<id>urn:sha1:16946de5905fff243c1e4415c4565803945e8c47</id>
<content type='text'>
Some supported devices need more time to come out of reset (eg.
BCM4345C5 in AP6256).

I don't have/found a datasheet, so the value was arrive at
experimentally with the Oprange Pi 3 board. Without increased delay,
I got intermittent failures during probe. This is a Bluetooth 5.0
device, so maybe that's why it takes longer to initialize than the
others.

Signed-off-by: Ondrej Jirman &lt;megous@megous.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>bluetooth: bcm: Add support for loading firmware for BCM4345C5</title>
<updated>2019-09-05T15:27:22Z</updated>
<author>
<name>Ondrej Jirman</name>
<email>megous@megous.com</email>
</author>
<published>2019-08-23T10:31:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=52c8c7a766ecc49ff2e4c1db30b0a24a019e31d4'/>
<id>urn:sha1:52c8c7a766ecc49ff2e4c1db30b0a24a019e31d4</id>
<content type='text'>
Detect BCM4345C5 and load a corresponding firmware file.

Signed-off-by: Ondrej Jirman &lt;megous@megous.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
</feed>
