From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Doug Berger <opendmb@gmail.com>, Al Cooper <alcooperx@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: bcm-kernel-feedback-list@broadcom.com,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] serial: 8250_bcm7271: use default_mux_rate if possible
Date: Wed, 24 Apr 2024 15:51:12 -0700 [thread overview]
Message-ID: <62cf51b8-0597-4e42-bdc2-54f01ecb91e1@broadcom.com> (raw)
In-Reply-To: <20240424222559.1844045-1-opendmb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On 4/24/24 15:25, Doug Berger wrote:
> There is a scenario when resuming from some power saving states
> with no_console_suspend where console output can be generated
> before the 8250_bcm7271 driver gets the opportunity to restore
> the baud_mux_clk frequency. Since the baud_mux_clk is at its
> default frequency at this time the output can be garbled until
> the driver gets the opportunity to resume.
>
> Since this is only an issue with console use of the serial port
> during that window and the console isn't likely to use baud
> rates that require alternate baud_mux_clk frequencies, allow the
> driver to select the default_mux_rate if it is accurate enough.
>
> Fixes: 41a469482de2 ("serial: 8250: Add new 8250-core based Broadcom STB driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Doug Berger <opendmb@gmail.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
Thanks!
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2024-04-24 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 22:25 [PATCH v2] serial: 8250_bcm7271: use default_mux_rate if possible Doug Berger
2024-04-24 22:51 ` Florian Fainelli [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=62cf51b8-0597-4e42-bdc2-54f01ecb91e1@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=stable@vger.kernel.org \
/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).