From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mips@vger.kernel.org, Serge Semin <fancer.lancer@gmail.com>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Maxime Ripard <mripard@kernel.org>,
linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/3] serial: 8250_dw: Simplify the ref clock rate setting procedure
Date: Sat, 20 Jun 2020 09:12:01 +0100 [thread overview]
Message-ID: <20200620081201.GQ1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200619200251.9066-3-Sergey.Semin@baikalelectronics.ru>
On Fri, Jun 19, 2020 at 11:02:50PM +0300, Serge Semin wrote:
> Really instead of twice checking the clk_round_rate() return value
> we could do it once, and if it isn't error the clock rate can be changed.
> By doing so we decrease a number of ret-value tests and remove a weird
> goto-based construction implemented in the dw8250_set_termios() method.
This doesn't look right to me - neither the before code nor the after
code.
> clk_disable_unprepare(d->clk);
> rate = clk_round_rate(d->clk, baud * 16);
> - if (rate < 0)
> - ret = rate;
> - else if (rate == 0)
> - ret = -ENOENT;
> - else
> + if (rate > 0) {
> ret = clk_set_rate(d->clk, rate);
> + if (!ret)
> + p->uartclk = rate;
> + }
> clk_prepare_enable(d->clk);
>
> - if (ret)
> - goto out;
> -
> - p->uartclk = rate;
newrate = baud * 16;
clk_disable_unprepare(d->clk);
rate = clk_round_rate(newrate);
ret = clk_set_rate(d->clk, newrate);
if (!ret)
p->uartclk = rate;
ret = elk_prepare_enable(d->clk);
/* check ret for failure, means the clock is no longer running */
is all that should be necessary: note that clk_round_rate() is required
to return the rate that a successful call to clk_set_rate() would result
in for that clock. It is equivalent to:
ret = clk_set_rate(d->clk, newrate);
if (ret == 0)
p->uartclk = clk_get_rate(d->clk);
The other commonly misunderstood thing about the clk API is that the
rate you pass in to clk_round_rate() to discover the actual clock rate
and the value passed in to clk_set_rate() _should_ be the same value.
You should _not_ do clk_set_rate(clk, clk_round_rate(clk, newrate));
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-20 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 20:02 [PATCH v7 0/3] serial: 8250_dw: Fix ref clock usage Serge Semin
2020-06-19 20:02 ` [PATCH v7 1/3] serial: 8250: Add 8250 port clock update method Serge Semin
2020-06-19 20:02 ` [PATCH v7 2/3] serial: 8250_dw: Simplify the ref clock rate setting procedure Serge Semin
2020-06-20 8:12 ` Russell King - ARM Linux admin [this message]
2020-06-19 20:02 ` [PATCH v7 3/3] serial: 8250_dw: Fix common clocks usage race condition Serge Semin
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=20200620081201.GQ1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=will@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 NNTP newsgroup(s).