[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200701211337.3027448-1-danielwinkler@google.com>
Date: Wed, 1 Jul 2020 14:13:36 -0700
From: Daniel Winkler <danielwinkler@...gle.com>
To: linux-serial@...r.kernel.org, linux-mediatek@...ts.infradead.org,
Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>
Cc: BlueZ <linux-bluetooth@...r.kernel.org>,
chromeos-bluetooth-upstreaming
<chromeos-bluetooth-upstreaming@...omium.org>,
stable@...r.kernel.org, abhishekpandit@...omium.org,
Daniel Winkler <danielwinkler@...gle.com>,
Aaron Sierra <asierra@...-inc.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, Lukas Wunner <lukas@...ner.de>,
Vignesh Raghavendra <vigneshr@...com>,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/1] Revert "serial: 8250: Fix max baud limit in generic
8250 port"
This change regresses the QCA6174A-3 bluetooth chip, preventing
firmware from being properly loaded. Without this change, the
chip works as intended.
The device is the Kukui Chromebook using the Mediatek chipset
and the 8250_mtk uart. Initial controller baudrate is 115200
and operating speed is 3000000. Our entire suite of bluetooth
tests now fail on this platform due to an apparent failure to
sync its firmware on initialization.
The driver is in the cros tree at drivers/bluetooth/hci_qca.c
and uses the serdev interface. Specifically, this is the
QCA_ROME chipset.
Daniel Winkler (1):
Revert "serial: 8250: Fix max baud limit in generic 8250 port"
drivers/tty/serial/8250/8250_port.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
2.27.0.212.ge8ba1cc988-goog
Powered by blists - more mailing lists