<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>794b5e7727de1ebaa07366ae346a139870874c2d - bluetooth: remove all PCMCIA drivers</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#794b5e7727de1ebaa07366ae346a139870874c2d</link>
        <description>bluetooth: remove all PCMCIA driversPCMCIA is almost completely obsolete (the last computers supporting itnatively were from ~2009), and the general consensus [1] seems to bethat support for it should be gradually removed from the kernel.In 2023, an initial step of removing all the PCMCIA char drivers wastaken in commit 9b12f050c76f (&quot;char: pcmcia: remove all the drivers&quot;),and that has not been reverted, so it seems logical to continue thisprocess by removing more low-hanging fruit.These three Bluetooth drivers have had no meaningful changes sincetheir status was discussed in 2022 [2], and are unlikely to have anyremaining users. The latest functional change to any of them was apatch to bluecard_cs to fix LED blinking behavior in 2017. The othertwo drivers have not had any meaningful changes made since 2007. Removethem.Note that even with these drivers removed, it is still possible to useother PCMCIA Bluetooth cards that present themselves as a standardserial port via serial_cs and hciattach while the serial_cs driver isstill present.[1] https://lore.kernel.org/all/c5b39544-a4fb-4796-a046-0b9be9853787@app.fastmail.com/[2] https://lore.kernel.org/all/Y07d7rMvd5++85BJ@owl.dominikbrodowski.net/Signed-off-by: Ethan Nelson-Moore &lt;enelsonmoore@gmail.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Sun, 03 May 2026 05:31:21 +0200</pubDate>
        <dc:creator>Ethan Nelson-Moore &lt;enelsonmoore@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2d00975c841fa2e52921353392ce9780843bfee7 - Bluetooth: btintel_pcie: Support Product level reset</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#2d00975c841fa2e52921353392ce9780843bfee7</link>
        <description>Bluetooth: btintel_pcie: Support Product level resetWhen driver encounters a TOP exception, ACPI methods will be calledfor Product level reset since Wifi and BT share the same TOP. BT driverwill first reprobe the wifi driver and then reprobe BT.Signed-off-by: Chandrashekar Devegowda &lt;chandrashekar.devegowda@intel.com&gt;Signed-off-by: Venkat Rao Bagalkote &lt;venkat88@linux.ibm.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Mon, 13 Apr 2026 06:20:40 +0200</pubDate>
        <dc:creator>Chandrashekar Devegowda &lt;chandrashekar.devegowda@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>97fdb2ea06efdde784480934d1ff60eb21e88b58 - Bluetooth: hci_h5: implement CRC data integrity</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#97fdb2ea06efdde784480934d1ff60eb21e88b58</link>
        <description>Bluetooth: hci_h5: implement CRC data integrityThe UART-based H5 protocol supports CRC data integrity checks forreliable packets. The host sets bit 5 in the configuration field of theCONFIG link control message to indicate that CRC is supported. Thecontroller sets the same bit in the CONFIG RESPONSE message to indicatethat CRC may be used from then on.Tested on a MangoPi MQ-Pro with a Realtek RTL8723DS Bluetooth controllerusing the tip of the bluetooth-next tree.Signed-off-by: Javier Nieto &lt;jgnieto@cs.stanford.edu&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Tue, 30 Sep 2025 00:59:21 +0200</pubDate>
        <dc:creator>Javier Nieto &lt;jgnieto@cs.stanford.edu&gt;</dc:creator>
    </item>
<item>
        <title>1c5091a9b4c990a6fcf8de7d0e97dba4cf878f17 - Bluetooth: Fix build after header cleanup</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#1c5091a9b4c990a6fcf8de7d0e97dba4cf878f17</link>
        <description>Bluetooth: Fix build after header cleanupSome Kconfig dependencies are needed after my recent cleanup, sincethe core code has its own option.Since btmtksdio does not actually call h4_recv_buf(), move thedefinitions it uses outside the BT_HCIUART_H4 gate in hci_uart.h toavoid adding a dependency for btmtksdio.The rest I touched (bpa10x, btmtkuart, and btnxpuart) do really callh4_recv_buf(), so the dependency is required, add it for them.Fixes: 0e272fc7e17d (&quot;Bluetooth: remove duplicate h4_recv_buf() in header&quot;)Reported-by: kernel test robot &lt;lkp@intel.com&gt;Closes: https://lore.kernel.org/oe-kbuild-all/202508300413.OnIedvRh-lkp@intel.com/Signed-off-by: Calvin Owens &lt;calvin@wbinvd.org&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Tue, 02 Sep 2025 17:43:44 +0200</pubDate>
        <dc:creator>Calvin Owens &lt;calvin@wbinvd.org&gt;</dc:creator>
    </item>
<item>
        <title>f330734a6315ab3360a524946ea624675b246956 - Revert &quot;Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL&quot;</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#f330734a6315ab3360a524946ea624675b246956</link>
        <description>Revert &quot;Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL&quot;This reverts commit 75ddcd5ad40ecd9fbc9f5a7a2ed0e1e74921db3c.This patch doesn&apos;t work quite well - It&apos;s observed that with this patchHFP is flaky on most of the existing USB Bluetooth controllers: Intelchips sometimes send out no packet for Transparent codec; MTK chips maygenerate SCO data with a wrong handle for CVSD codec; RTK could splitthe data with a wrong packet size for Transparent codec; ... etc.Cc: chromeos-bluetooth-upstreaming@chromium.orgSigned-off-by: Hsin-chen Chuang &lt;chharry@chromium.org&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Wed, 16 Apr 2025 11:53:37 +0200</pubDate>
        <dc:creator>Hsin-chen Chuang &lt;chharry@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>75ddcd5ad40ecd9fbc9f5a7a2ed0e1e74921db3c - Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#75ddcd5ad40ecd9fbc9f5a7a2ed0e1e74921db3c</link>
        <description>Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNELAutomatically configure the altsetting for HCI_USER_CHANNEL when a SCOis connected.The motivation is to enable the HCI_USER_CHANNEL user to send out SCOdata through USB Bluetooth chips, which is mainly used for bidirectionalaudio transfer (voice call). This was not capable because:- Per Bluetooth Core Spec v5, Vol 4, Part B, 2.1, the corresponding  alternate setting should be set based on the air mode in order to  transfer SCO data, but- The Linux Bluetooth HCI_USER_CHANNEL exposes the Bluetooth Host  Controller Interface to the user space, which is something above the  USB layer. The user space is not able to configure the USB alt while  keeping the channel open.This patch intercepts the HCI_EV_SYNC_CONN_COMPLETE packets in btusb,extracts the air mode, and configures the alt setting in btusb.This patch is tested on ChromeOS devices. The USB Bluetooth models(CVSD, TRANS alt3 and alt6) could work without a customized kernel.Fixes: b16b327edb4d (&quot;Bluetooth: btusb: add sysfs attribute to control USB alt setting&quot;)Signed-off-by: Hsin-chen Chuang &lt;chharry@chromium.org&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Thu, 27 Feb 2025 18:14:10 +0100</pubDate>
        <dc:creator>Hsin-chen Chuang &lt;chharry@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>f062b6ecc798664ec4ad4a5f484c8456d2667059 - Bluetooth: add HAS_IOPORT dependencies</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#f062b6ecc798664ec4ad4a5f484c8456d2667059</link>
        <description>Bluetooth: add HAS_IOPORT dependenciesIn a future patch HAS_IOPORT=n will disable inb()/outb() and friends atcompile time. We thus need to add HAS_IOPORT as dependency for thosedrivers using them.Co-developed-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Signed-off-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Signed-off-by: Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;Acked-by: Lucas De Marchi &lt;lucas.demarchi@intel.com&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Thu, 24 Oct 2024 19:54:41 +0200</pubDate>
        <dc:creator>Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>37bac77e4649e8158698a60addc22ec4faf5649a - Bluetooth: hci_uart: Add support for Amlogic HCI UART</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#37bac77e4649e8158698a60addc22ec4faf5649a</link>
        <description>Bluetooth: hci_uart: Add support for Amlogic HCI UARTAdd a new HCI protocol HCI_UART_AML for the Amlogic Bluetoothcontroller. It works on the standard H4 protocol via a 4-wire UARTinterface, with baud rates up to 4 Mbps.The controller supports two types of commands: the TCI commands and thevendor command. The former is for initial setup including setting baudrates, downloading fw, starting chip and etc, while the latter is fordumping firmware versions and setting public address after firmwareupdates and normal startup.It was verified on board of T602 (S905X4 + W265S2).dmesg:..[    5.313450] Bluetooth: HCI UART protocol AML registered[    6.506052] Bluetooth: hci0: fw_version: date = 42.28, number = 0xb2fd...Co-developed-by: Ye He &lt;ye.he@amlogic.com&gt;Signed-off-by: Ye He &lt;ye.he@amlogic.com&gt;Signed-off-by: Yang Li &lt;yang.li@amlogic.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Fri, 09 Aug 2024 07:42:25 +0200</pubDate>
        <dc:creator>Yang Li &lt;yang.li@amlogic.com&gt;</dc:creator>
    </item>
<item>
        <title>61f7a8f975456d7be21100ee0936389142b95a81 - Bluetooth: btmtk: Fix btmtk.c undefined reference build error harder</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#61f7a8f975456d7be21100ee0936389142b95a81</link>
        <description>Bluetooth: btmtk: Fix btmtk.c undefined reference build error harderThe previous fix was incomplete as the link failure still persistswith CONFIG_USB=m when the sdio or serial wrappers for btmtk.care build-in:btmtk.c:(.text+0x468): undefined reference to `usb_alloc_urb&apos;btmtk.c:(.text+0x488): undefined reference to `usb_free_urb&apos;btmtk.c:(.text+0x500): undefined reference to `usb_anchor_urb&apos;btmtk.c:(.text+0x50a): undefined reference to `usb_submit_urb&apos;btmtk.c:(.text+0x92c): undefined reference to `usb_control_msg&apos;btmtk.c:(.text+0xa92): undefined reference to `usb_unanchor_urb&apos;btmtk.c:(.text+0x11e4): undefined reference to `usb_set_interface&apos;btmtk.c:(.text+0x120a): undefined reference to `usb_kill_anchored_urbs&apos;Disallow this configuration.Fixes: f0c83a23fcbb (&quot;Bluetooth: btmtk: Fix btmtk.c undefined reference build error&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Mon, 22 Jul 2024 11:27:05 +0200</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>b96bac9607b285d4316e74fbf469df084c4f8adb - Bluetooth: hci: fix build when POWER_SEQUENCING=m</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#b96bac9607b285d4316e74fbf469df084c4f8adb</link>
        <description>Bluetooth: hci: fix build when POWER_SEQUENCING=mBT_HCIUART_QCA, which is a bool and an HCI UART component, uses nowpower sequencing, so we need to be sure BT_HCIUART_QCA=y andPOWER_SEQUENCING=m cannot happen:  /usr/bin/aarch64-linux-gnu-ld: drivers/bluetooth/hci_qca.o: in function `qca_serdev_probe&apos;:  drivers/bluetooth/hci_qca.c:2401:(.text+0xc48): undefined reference to `devm_pwrseq_get&apos;  /usr/bin/aarch64-linux-gnu-ld: drivers/bluetooth/hci_qca.o: in function `qca_power_shutdown&apos;:  drivers/bluetooth/hci_qca.c:2192:(.text+0x29e8): undefined reference to `pwrseq_power_off&apos;  /usr/bin/aarch64-linux-gnu-ld: drivers/bluetooth/hci_qca.o: in function `qca_power_on&apos;:  drivers/bluetooth/hci_qca.c:1808:(.text+0x3390): undefined reference to `pwrseq_power_on&apos;Fixes: 9a15ce685706 (&quot;Bluetooth: qca: use the power sequencer for QCA6390&quot;)Signed-off-by: Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;Reviewed-by: Bartosz Golaszewski &lt;bartosz.golaszewski@linaro.org&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Sun, 23 Jun 2024 19:13:52 +0200</pubDate>
        <dc:creator>Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>08c22b52262041164990eef4b0e076bce173a3b2 - Bluetooth: hci_bcm4377: Add BCM4388 support</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#08c22b52262041164990eef4b0e076bce173a3b2</link>
        <description>Bluetooth: hci_bcm4377: Add BCM4388 supportThis new variant needs a different core2_window1 and always usesbeamforming.The BAR2 also has an offset (RAM start, presumably), so add that.Signed-off-by: Hector Martin &lt;marcan@marcan.st&gt;Reviewed-by: Sven Peter &lt;sven@svenpeter.dev&gt;[sven: rebased, updated some comments, mentioned 4388 in Kconfig]Signed-off-by: Sven Peter &lt;sven@svenpeter.dev&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Sun, 02 Jun 2024 11:57:05 +0200</pubDate>
        <dc:creator>Hector Martin &lt;marcan@marcan.st&gt;</dc:creator>
    </item>
<item>
        <title>c2b636b3f788d10486a6691ad6dd3ec4c93bd78e - Bluetooth: btintel_pcie: Add support for PCIe transport</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#c2b636b3f788d10486a6691ad6dd3ec4c93bd78e</link>
        <description>Bluetooth: btintel_pcie: Add support for PCIe transportAdd initial code to support Intel bluetooth devices based on PCIetransport. Allocate memory for TX &amp; RX buffers, internal structures,initialize interrupts for TX &amp; RX and PCIe device.Signed-off-by: Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;Suggested-by: Bjorn Helgaas &lt;helgaas@kernel.org&gt;Suggested-by: Paul Menzel &lt;pmenzel@molgen.mpg.de&gt;Signed-off-by: Kiran K &lt;kiran.k@intel.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Tue, 07 May 2024 17:56:57 +0200</pubDate>
        <dc:creator>Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ab4e4380d4e158486e595013a2635190e07e28ce - Bluetooth: Add vhci devcoredump support</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#ab4e4380d4e158486e595013a2635190e07e28ce</link>
        <description>Bluetooth: Add vhci devcoredump supportAdd devcoredump support for vhci that creates forcce_devcoredump debugfsentry. This is used for mgmt-tester tests.Signed-off-by: Manish Mandlik &lt;mmandlik@google.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Thu, 30 Mar 2023 18:58:24 +0200</pubDate>
        <dc:creator>Manish Mandlik &lt;mmandlik@google.com&gt;</dc:creator>
    </item>
<item>
        <title>11e29b4a3fda975f4427800285b7e4544f4e9152 - Bluetooth: NXP: select CONFIG_CRC8</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#11e29b4a3fda975f4427800285b7e4544f4e9152</link>
        <description>Bluetooth: NXP: select CONFIG_CRC8The driver needs both CRC32 and CRC8 to link correctly:ld: drivers/bluetooth/btnxpuart.o: in function `nxp_serdev_probe&apos;:drivers/bluetooth/btnxpuart.c:1214: undefined reference to`crc8_populate_msb&apos;ld: drivers/bluetooth/btnxpuart.o: in function `nxp_send_ack&apos;:drivers/bluetooth/btnxpuart.c:559: undefined reference to `crc8&apos;ld: drivers/bluetooth/btnxpuart.c:559: undefined reference to `crc8&apos;Fixes: 3e662aa4453a (&quot;Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Wed, 22 Mar 2023 12:16:27 +0100</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>689ca16e523278470c38832a3010645a78c544d8 - Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#689ca16e523278470c38832a3010645a78c544d8</link>
        <description>Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsetsThis adds a driver based on serdev driver for the NXP BT serial protocolbased on running H:4, which can enable the built-in Bluetooth deviceinside an NXP BT chip.This driver has Power Save feature that will put the chip into sleep statewhenever there is no activity for 2000ms, and will be woken up when anyactivity is to be initiated over UART.This driver enables the power save feature by default by sending the vendorspecific commands to the chip during setup.During setup, the driver checks if a FW is already running on the chipby waiting for the bootloader signature, and downloads device specific FWfile into the chip over UART if bootloader signature is received..Signed-off-by: Neeraj Sanjay Kale &lt;neeraj.sanjaykale@nxp.com&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Thu, 16 Mar 2023 18:22:14 +0100</pubDate>
        <dc:creator>Neeraj Sanjay Kale &lt;neeraj.sanjaykale@nxp.com&gt;</dc:creator>
    </item>
<item>
        <title>8a06127602de70541e751a8c64a06995ee281f22 - Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCIe boards</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#8a06127602de70541e751a8c64a06995ee281f22</link>
        <description>Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCIe boardsBroadcom BCM4377/4378/4387 are dual WiFi/Bluetooth boards found in Applemachines. This driver adds support for the Bluetooth function whichexposes a shared memory IPC protocol over PCIe to tunnel HCI traffic.Signed-off-by: Sven Peter &lt;sven@svenpeter.dev&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Fri, 04 Nov 2022 22:13:03 +0100</pubDate>
        <dc:creator>Sven Peter &lt;sven@svenpeter.dev&gt;</dc:creator>
    </item>
<item>
        <title>db11223571d489d1aab575a4ac4b7352d2d54e2f - Bluetooth: btusb: Default CONFIG_BT_HCIBTUSB_POLL_SYNC=y</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#db11223571d489d1aab575a4ac4b7352d2d54e2f</link>
        <description>Bluetooth: btusb: Default CONFIG_BT_HCIBTUSB_POLL_SYNC=ypoll_sync has been proven to fix races of USB data and event endpointsso this enables it by default.Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;Tested-by: Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Tue, 25 Oct 2022 23:12:58 +0200</pubDate>
        <dc:creator>Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>bb1afb2955212d30177b122b13ae636a69abf883 - Bluetooth: btusb: Add CONFIG_BT_HCIBTUSB_POLL_SYNC</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#bb1afb2955212d30177b122b13ae636a69abf883</link>
        <description>Bluetooth: btusb: Add CONFIG_BT_HCIBTUSB_POLL_SYNCThis adds CONFIG_BT_HCIBTUSB_POLL_SYNC which can be used to set thedefault behavior of Bluetooth USB controller with respect to pollsynchronization of its endpoits.Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;Tested-by: Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Tue, 25 Oct 2022 23:12:57 +0200</pubDate>
        <dc:creator>Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f5c3f98946e37a1f7ca07a6c6ab33b1223661aec - Bluetooth: btmtkuart: rely on BT_MTK module</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#f5c3f98946e37a1f7ca07a6c6ab33b1223661aec</link>
        <description>Bluetooth: btmtkuart: rely on BT_MTK moduleRely on btmtk module to reduce duplicated codeSigned-off-by: Sean Wang &lt;sean.wang@mediatek.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Wed, 09 Mar 2022 01:03:52 +0100</pubDate>
        <dc:creator>Sean Wang &lt;sean.wang@mediatek.com&gt;</dc:creator>
    </item>
<item>
        <title>3a722044aacf7f8524226951515dbc0390e030e0 - Bluetooth: btmtksido: rely on BT_MTK module</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/bluetooth/Kconfig#3a722044aacf7f8524226951515dbc0390e030e0</link>
        <description>Bluetooth: btmtksido: rely on BT_MTK moduleRely on btmtk module to reduce duplicated codeSigned-off-by: Sean Wang &lt;sean.wang@mediatek.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux/drivers/bluetooth/Kconfig</description>
        <pubDate>Mon, 18 Oct 2021 23:30:13 +0200</pubDate>
        <dc:creator>Sean Wang &lt;sean.wang@mediatek.com&gt;</dc:creator>
    </item>
</channel>
</rss>
