Re: should RTS init in serial core be tied to CRTSCTS

[Robin Getz]

On Tue 6 Mar 2007 15:40, Krzysztof Halasa pondered:
> "Mike Frysinger" <vapier.adi@xxxxxxxxx> writes:
>  >ÂÂÂÂÂÂÂÂÂÂÂ /*
>  >ÂÂÂÂÂÂÂÂÂÂÂÂ * Setup the RTS and DTR signals once the
>  >ÂÂÂÂÂÂÂÂÂÂÂÂ * port is open and ready to respond.
>  >ÂÂÂÂÂÂÂÂÂÂÂÂ */
>  >ÂÂÂÂÂÂÂÂÂÂÂ if (info->tty->termios->c_cflag & CBAUD)
>  >ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ uart_set_mctrl(port, TIOCM_RTS | TIOCM_DTR);
>  > ...
>  >
>  > shouldnt TIOCM_RTS be passed down only when the 'r' is appended to the
>  > boot cmdline ?
>
>  How would it be useful?

It is useful on (broken) legacy serial equipment, where RTS should be 
completely under the applications control.

Glitches on RTS aren't acceptable, and confuse some devices.

>  CRTSCTS is for CTS only (i.e., the transmission is paused when CTS is
>  inactive), not for RTS. DTR and RTS should be active when the port is
>  open even without CRTSCTS (= without handshaking),

That depends on the equipment that you are attached to. Some very early 
(broken) systems actually invert the meaning of RTS, so while the kernel 
thinks it is "opening" the port, it actually closes it...

>  it's used for 
>  various purposes such as providing +12V to the device (and two pins
>  can supply more power than one - sure, it isn't the best idea).

I understand - the request wasn't to change the default operation - just add a 
method of controlling things, so those minority of people who want the 
control can have it.

-Robin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/