From: Greg KH <gregkh@linuxfoundation.org>
To: "Nuno Gonçalves" <nunojpg@gmail.com>
Cc: ed.blake@sondrel.com, linux-kernel@vger.kernel.org
Subject: Re: 8250_dw bug
Date: Thu, 11 Jan 2018 14:19:47 +0100 [thread overview]
Message-ID: <20180111131947.GA16628@kroah.com> (raw)
In-Reply-To: <CAEXMXLR=wuxgPJHGmn0bTUC5_8kZ-mc1u3FmAGyAs9HmV_FNig@mail.gmail.com>
On Thu, Jan 11, 2018 at 01:47:31PM +0100, Nuno Gonçalves wrote:
> Dear Ed and Greg,
>
> There is a small bug on de9e33bdfa22e607a88494ff21e9196d00bf4550, at
> least on 32bit devices.
>
> Line 274 if (rate >= i * min_rate && rate <= i * max_rate)
>
> This will overflow when min_rate/max_rate is large and can not be
> achieved in the hardware.
>
> Eg.
>
> stty -F /dev/ttyS2 raw 3500000 (not achievable on my board).
>
> target_rate=56000000 (for 3500000baud)
> min_rate=55125000
> max_rate=56875000
> rate=24000000 (clk_round_rate for my board)
>
> Since my board can only do 1500000baud, this loop will keep
> incrementing i until i=77*56875000 will overflow, and there are
> unexpected results.
>
> I suggest this patch:
>
> --- a/drivers/tty/serial/8250/8250_dw.c
> +++ b/drivers/tty/serial/8250/8250_dw.c
> @@ -267,7 +267,13 @@ static void dw8250_set_termios(struct uart_port
> *p, struct ktermios *termios,
>
> for (i = 1; i <= UART_DIV_MAX; i++) {
> rate = clk_round_rate(d->clk, i * target_rate);
> - if (rate >= i * min_rate && rate <= i * max_rate)
> +
> + if (rate < i * min_rate) {
> + i = UART_DIV_MAX;
> + break;
> + }
> +
> + if (rate <= i * max_rate)
> break;
> }
> if (i <= UART_DIV_MAX) {
>
>
> Let me know if you want me to submit the formal patch.
Why wouldn't you submit a "formal patch", that way we could apply it if
it is correct :)
also cc: the linux-serial mailing list when you do so, thanks.
greg k-h
prev parent reply other threads:[~2018-01-11 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 12:47 8250_dw bug Nuno Gonçalves
2018-01-11 13:19 ` Greg KH [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=20180111131947.GA16628@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ed.blake@sondrel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nunojpg@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