[PATCH] serial/core: Initialize the console pm state

Sudhir Sreedharan ssreedharan at mvista.com
Mon Oct 6 02:48:15 PDT 2014

Hi Geert,

On Fri, Oct 3, 2014 at 5:52 PM, Geert Uytterhoeven <geert at linux-m68k.org> wrote:
> On Wed, Oct 1, 2014 at 7:27 PM, Kevin Hilman <khilman at kernel.org> wrote:
>> On Sun, Sep 21, 2014 at 11:30 PM, Sudhir Sreedharan
>> <ssreedharan at mvista.com> wrote:
>>> For console devices having UART_CAP_SLEEP capability, the uart_pm_state has
>>> to be initialized to UART_PM_STATE_ON. Otherwise the LCR regiser values
>>> are reinitialized when uart_change_pm is called from uart_configure_port.
>>> Signed-off-by: Sudhir Sreedharan <ssreedharan at mvista.com>
>> Multiple boot failures on ARM[1] were bisected down to this patch.
>> How was this patch tested, and on which platforms?
>> Also, the changelog states that this should be done only for
>> UART_CAP_SLEEP, but the patch does it for every UART.
>> Greg, I suggest this patch be dropped from tty-next until it has been
>> better described and tested.
>> Kevin
>> [1] http://lists.linaro.org/pipermail/kernel-build-reports/2014-October/005550.html
> Perhaps it should call "uart_change_pm(state, UART_PM_STATE_ON)"
> instead, so the driver's .pm() method is called?

If  "uart_change_pm(state, UART_PM_STATE_ON);" is called, it will
reinitialize the LCR register, thus changing the configuration of
console port. This will throw garbage characters from the point where
the serial driver initializes till startup is called from userland.


More information about the linux-arm-kernel mailing list