linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Andy Shevchenko <andy@black.fi.intel.com>,
	Serge Semin <Sergey.Semin@baikalelectronics.ru>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
	Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
	Maxime Ripard <mripard@kernel.org>, Will Deacon <will@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/4] serial: 8250: Add 8250 port clock update method
Date: Mon, 19 Feb 2024 17:08:54 +0200	[thread overview]
Message-ID: <ZdNvBtOlxo4FlLUH@smile.fi.intel.com> (raw)
In-Reply-To: <ow5mvkxa4g7mub3faiytsij4cyaaralcbzyn675jny5355han7@azw65mhkpwjz>

On Fri, Feb 16, 2024 at 08:19:37PM +0300, Serge Semin wrote:
> On Thu, Feb 15, 2024 at 09:39:12PM +0200, Andy Shevchenko wrote:

...

(thanks for the detailed explanation why you have done it that way)

> If what you suggest is to replace the serial8250_update_uartclk() body
> with a direct uart_port::set_termios() invocation then I don't find it
> being much clearer really. The serial8250_update_uartclk() is
> currently specialized on doing one thing: adjusting the divider in
> case of the UART-clock change. If instead the entire
> serial8250_set_termios() method is called then for a reader it won't
> be easy to understand what is really required for a 8250 serial port
> to perceive the ref-clock change. But from the maintainability point
> of view I guess that it might be safer to just call
> serial8250_set_termios() indeed, since among the other things the
> later method implies the divider update too. Thus the maintainer won't
> need to support the two clock divider update implementations.

> From that perspective I agree, directly calling serial8250_set_termios()
> might be more suitable despite of it' doing more than required.

Would it be possible for you to cook the patch (and test on your HW,
since it seems the only user of that)?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-02-19 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  0:33 [PATCH v9 0/4] serial: 8250_dw: Fix ref clock usage Serge Semin
2020-07-23  0:33 ` [PATCH v9 1/4] serial: 8250: Add 8250 port clock update method Serge Semin
2024-02-14 13:45   ` Andy Shevchenko
2024-02-15 19:32     ` Serge Semin
2024-02-15 19:39       ` Andy Shevchenko
2024-02-16 17:19         ` Serge Semin
2024-02-19 15:08           ` Andy Shevchenko [this message]
2024-02-22 14:55             ` Serge Semin
2020-07-23  0:33 ` [PATCH v9 2/4] serial: 8250_dw: Simplify the ref clock rate setting procedure Serge Semin
2020-07-23  0:33 ` [PATCH v9 3/4] serial: 8250_dw: Pass the same rate to the clk round and set rate methods Serge Semin
2020-07-23  0:33 ` [PATCH v9 4/4] 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=ZdNvBtOlxo4FlLUH@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Alexey.Malahov@baikalelectronics.ru \
    --cc=Pavel.Parkhomenko@baikalelectronics.ru \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=andy@black.fi.intel.com \
    --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-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mripard@kernel.org \
    --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).