Skip to contentSkip to conversation

2.6.9: serial_core: uart_open

DISCUSSION karl malbrain 1 participant 1 message Jul 12, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 27 lines · karl malbrain
Quoted 16 lines

The uart_open code loops waiting for CD to be asserted (whenever CLOCAL is not set). The bottom of the loop contains the following code:

up(&state->sem);
schedule();
down(&state->sem);

if( signal_pending(current) )
break;

When I issue an open("/dev/ttyS1", O_RDWR) from a terminal session on the console, the system seems to come to a stop in this loop until the process is killed. I suspect that the scheduler is choosing this process to run again because of an elevated console priority of some sort.

Quoted 5 lines

Is there a kernel mechanism to put a process to sleep until awakened by an event to replace this looping behaviour?

Thanks, karl malbrain, malbrain-at-yahoo-dot-com

In the first place, you should perform an open(O_NDELAY), so the open returns immediately with anything that has potential "modem-control". Then you can set the device to blocking using fcntl(F_GETFL), F_SETFL.

Quoted 5 lines

Also, the task that is waiting for the open() is sleeping. That's what schedule() does.

Cheers,
Dick Johnson

I'm looking for the POSIX behaviour of delaying the open until CD is asserted by the modem. If schedule() doesn't select another process to run, no wonder the system is hung at this point, because the uart_open loop doesn't break until CD is asserted by the modem. This sounds like a serious bug.

karl_m