Re: AM5749: tty serial 8250 omap driver crash

[Tony Lindgren <tony@atomide.com>]

* Romain Naour <romain.naour@smile.fr> [220211 10:10]:
> Le 10/02/2022 à 13:05, Tony Lindgren a écrit :
> > Could be that too, but maybe it's as simple as the patch below. Care to
> > give it a try?
> 
> The serial console stop working during the kernel boot with this patch applied.

Yeah and we already have the serdev taking case of PM runtime here.

> >> Are you able to reproduce it ?
> >> Maybe on a IDK574 or a Beaglebone-AI board ?
> > 
> > Not sure why I'm not seeing this one with my test systems.. Have not tried
> > with the RT patches for a while though.
> 
> The RT patches really makes a difference here.

Looks like the following script to just toggle the module state locks
up things for me on beagle-x15 very fast. So yeah now I'm able to
reproduce the issue. Seems like the module is not ready right after
enabling it live we've seen for dra7 iva for example.

Regards,

Tony

8< ------
#!/bin/sh

# Test rebind for serial console uart3 ttyS2, run from an ssh session
module="48020050.target-module"
driver="/sys/bus/platform/drivers/ti-sysc"

# Detach all kernel serial consoles
consoles=$(find /sys/bus/platform/devices/4*.serial/ -name console)
for console in ${consoles}; do
        echo -n N > ${console}
done

# Configure PM runtime autosuspend for all uarts
uarts=$(find /sys/bus/platform/devices/4*.serial/power/ -type d)
for uart in $uarts; do
        echo -n 3000 > $uart/autosuspend_delay_ms
        echo -n enabled > $uart/wakeup
        echo -n auto > $uart/control
done

# Configure wake-up from suspend for all uarts
uarts=$(find /sys/class/tty/tty[SO]*/power/ -type d 2>/dev/null)
for uart in $uarts; do
        echo -n enabled > $uart/wakeup
done

# Keep rebinding uart3 in a loop
while true; do
        echo ${module} > ${driver}/bind
        echo ${module} > ${driver}/unbind
done