Re: [PATCH RESEND v6 0/3] serial: 8250_dw: Fix ref clock usage

On Thu, Jun 18, 2020 at 11:31:44AM +0300, Andy Shevchenko wrote: > On Thu, Jun 18, 2020 at 11:17 AM Andy Shevchenko > wrote: > > On Thu, Jun 18, 2020 at 1:52 AM Serge Semin > > wrote: > > > I'm wondering how this will collaborate with runtime PM. > > Forgot to mention the WIP repository [1] fo

Re: [PATCH RESEND v6 0/3] serial: 8250_dw: Fix ref clock usage

On Thu, Jun 18, 2020 at 11:17:47AM +0300, Andy Shevchenko wrote: > On Thu, Jun 18, 2020 at 1:52 AM Serge Semin > wrote: > > > > Greg, Jiri. We've missed the last merge window. It would be pity to miss > > the next one. Please review/merge in the series. > > > > Regarding the patchset. It might be

Re: [PATCH RESEND v6 0/3] serial: 8250_dw: Fix ref clock usage

On Thu, Jun 18, 2020 at 11:17 AM Andy Shevchenko wrote: > On Thu, Jun 18, 2020 at 1:52 AM Serge Semin > wrote: > I'm wondering how this will collaborate with runtime PM. Forgot to mention the WIP repository [1] for runtime PM rework (it doesn't mean my comment against patch 3 is not valid). To

Re: [PATCH RESEND v6 0/3] serial: 8250_dw: Fix ref clock usage

On Thu, Jun 18, 2020 at 1:52 AM Serge Semin wrote: > > Greg, Jiri. We've missed the last merge window. It would be pity to miss > the next one. Please review/merge in the series. > > Regarding the patchset. It might be dangerous if an UART port reference > clock rate is suddenly changed. In partic