Hi, On Mon, Oct 6, 2014 at 2:57 PM, Sudhir Sreedharan <ssreedharan@xxxxxxxxxx> wrote: >> >> Multiple boot failures on ARM[1] were bisected down to this patch. >> >> How was this patch tested, and on which platforms? > > > > This patch was tested on x86-64(haswell) board, which uses ST16650V2 > uart(which has UART_CAP_SLEEP). > While serial driver gets initialized, console port LCR register is > getting reinitalized to 0. > Then boot logs will be seen as garbage characters. > > I will re-check why this failed on the boards/archs you mentioned. The issue is, in the boot logs, once the serial driver gets initialized, it throws garbage in the console. The serial device being used is ST16550V2 which is having SLEEP functionality. So when uart_configure_port is called, it calls the serial8250_set_sleep and set the LCR register to 0. The previous patch got failed because those are not based on 8250 and the do_pm functionality is different. Eg. for arndale board, in s3c24xx_serial_pm it uses the clock enable and disable functionality. I have created a new patch which will be confined only to 8250 based serial devices. I have tested it on x86-64 based haswell board, ARM64 based, P5040 powerpc which all uses 8250 based serial device. > > Thanks, > Sudhir -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
