On Fri, May 15, 2020 at 05:10:46PM +0300, Andy Shevchenko wrote: > On Thu, May 07, 2020 at 02:31:35AM +0300, Serge Semin wrote: > > The race condition may happen if the UART reference clock is shared with > > some other device (on Baikal-T1 SoC it's another DW UART port). In this > > case if that device changes the clock rate while serial console is using > > it the DW 8250 UART port might not only end up with an invalid uartclk > > value saved, but may also experience a distorted output data since > > baud-clock could have been changed. In order to fix this lets at least > > try to adjust the 8250 port setting like UART clock rate in case if the > > reference clock rate change is discovered. The driver will call the new > > method to update 8250 UART port clock rate settings. It's done by means of > > the clock event notifier registered at the port startup and unregistered > > in the shutdown callback method. > > I'm wondering if clock framework itself can provide such a notifier? > > > Note 1. In order to avoid deadlocks we had to execute the UART port update > > method in a dedicated deferred work. This is due to (in my opinion > > redundant) the clock update implemented in the dw8250_set_termios() > > method. > > So, and how you propose to update the clock when ->set_termios() is called?
First of all If you are worried about the current implementation, please don't, it still updates the clock in set_termios (please see the set_termios code). The method hasn't changed much and does the updating the same way it did before. Secondly, 8250 driver should be using the same reference clock as it is pre-defined by the platform with no change. The baud rate updates are supposed to be performed by the divider embedded into the 8250 controller, otherwise the divisor functionality is left completely unused. If a platform engineer needs to speed the uart up, the ref clock rate can be tuned by for instance the "assigned-clock-rates" property. > > > Note 2. Before the ref clock is manually changed by the custom > > set_termios() function we swap the port uartclk value with new rate > > adjusted to be suitable for the requested baud. It is necessary in > > order to effectively disable a functionality of the ref clock events > > handler for the current UART port, since uartclk update will be done > > a bit further in the generic serial8250_do_set_termios() function. > > ... > > > + struct notifier_block clk_notifier; > > + struct work_struct clk_work; > > Oh, this seems too much. > Perhaps, the compatible based quirk with your initial approach is much better > for time being. It's already in 8250_dw, useful not for a single platform and won't hurt any other one. So I'll leave it here and wait for the Greg feedback. -Sergey > > -- > With Best Regards, > Andy Shevchenko > >
