From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
Peter Collingbourne <pcc@google.com>
Subject: Re: [Bug] staging: rtl8723bs: Bluetooth stops working after patch: serial: 8250_dw: Do not reclock if already at correct rate
Date: Tue, 14 May 2024 15:55:41 +0300 [thread overview]
Message-ID: <ZkNfTRv0Lk8-_M1s@smile.fi.intel.com> (raw)
In-Reply-To: <8fe72cec-adba-42dd-9185-15e777714a81@gmail.com>
On Tue, May 14, 2024 at 06:32:37AM +0200, Philipp Hortmann wrote:
> Hi,
>
> I have a ODYS Trendbook next 14 with the wlan/bluetooth module rtl8723bs.
>
> Bluetooth stops working with the following commit:
> commit e5d6bd25f93d6ae158bb4cd04956cb497a85b8ef (HEAD)
> Author: Peter Collingbourne <pcc@google.com>
> Date: Thu Feb 22 11:26:34 2024 -0800
> serial: 8250_dw: Do not reclock if already at correct rate
>
> Please find dmesg below. Module has issues to load firmware.
>
> To enshure that this is the function breaking commit I applied the commit
> reversed on top of the latest kernel from the staging tree. Then bluetooth
> is working again.
>
> I can support with further tests. I do not have a good proposal for a fix as
> I expect a lot of side effects. Please send me proposals for a fix.
The revert is in the tree IIRC.
7dfae6cbadc1 ("serial: 8250_dw: Revert: Do not reclock if already at correct rate")
First appeared in v6.9-rc5.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-05-14 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 4:32 [Bug] staging: rtl8723bs: Bluetooth stops working after patch: serial: 8250_dw: Do not reclock if already at correct rate Philipp Hortmann
2024-05-14 12:55 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZkNfTRv0Lk8-_M1s@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=pcc@google.com \
--cc=philipp.g.hortmann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).