linux-toradex.git/drivers/tty/cyclades.c, branch v4.7-rc2

tty: Replace ASYNC_INITIALIZED bit and update atomically

2016-04-30T16:26:55+00:00

Replace ASYNC_INITIALIZED bit in the tty_port::flags field with
TTY_PORT_INITIALIZED bit in the tty_port::iflags field. Introduce helpers
tty_port_set_initialized() and tty_port_initialized() to abstract
atomic bit ops.

Note: the transforms for test_and_set_bit() and test_and_clear_bit()
are unnecessary as the state transitions are already mutually exclusive;
the tty lock prevents concurrent open/close/hangup.

Signed-off-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

tty: Replace ASYNC_CHECK_CD and update atomically

2016-04-30T16:26:55+00:00

Replace ASYNC_CHECK_CD bit in the tty_port::flags field with
TTY_PORT_CHECK_CD bit in the tty_port::iflags field. Introduce helpers
tty_port_set_check_carrier() and tty_port_check_carrier() to abstract
the atomic bit ops.

Signed-off-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

tty: Replace ASYNC_CTS_FLOW bit and update atomically

2016-04-30T16:26:55+00:00

Replace ASYNC_CTS_FLOW bit in the tty_port::flags field with
TTY_PORT_CTS_FLOW bit in the tty_port::iflags field. Add
tty_port_set_cts_flow() helper to abstract the atomic bit ops.

Signed-off-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

tty: Use termios c_*flag macros

2016-01-28T22:13:44+00:00

Expressions of the form "tty->termios.c_*flag & FLAG"
are more clearly expressed with the termios flags macros,
I_FLAG(), C_FLAG(), O_FLAG(), and L_FLAG().

Convert treewide.

Signed-off-by: Peter Hurley 
Acked-by: Johan Hovold 
Signed-off-by: Greg Kroah-Hartman

tty: Remove chars_in_buffer() line discipline method

2016-01-27T23:01:44+00:00

The chars_in_buffer() line discipline method serves no functional
purpose, other than as a (dubious) debugging aid for mostly bit-rotting
drivers. Despite being documented as an optional method, every caller
is unconditionally executed (although conditionally compiled).
Furthermore, direct tty->ldisc access without an ldisc ref is unsafe.
Lastly, N_TTY's chars_in_buffer() has warned of removal since 3.12.

Signed-off-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

cyclades: Deinline cyz_is_loaded, save 240 bytes

2015-12-14T03:59:48+00:00

This function compiles to 58 bytes of machine code.

Signed-off-by: Denys Vlasenko 
CC: Jiri Slaby 
CC: linux-serial@vger.kernel.org
Reviewed-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

cyclades: Deinline serial_paranoia_check, save 304 bytes

2015-12-14T03:59:48+00:00

This function compiles to 52 bytes of machine code.

Signed-off-by: Denys Vlasenko 
CC: Jiri Slaby 
CC: linux-serial@vger.kernel.org
Reviewed-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

cyclades: Deinline cyy_writeb, save 880 bytes

2015-12-14T03:59:48+00:00

This function compiles to 35 bytes of machine code.

Signed-off-by: Denys Vlasenko 
CC: Jiri Slaby 
CC: linux-serial@vger.kernel.org
Reviewed-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

cyclades: Deinline cyy_readb, save 368 bytes

2015-12-14T03:59:48+00:00

This function compiles to 32 bytes of machine code.

Signed-off-by: Denys Vlasenko 
CC: Jiri Slaby 
CC: linux-serial@vger.kernel.org
Reviewed-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman

tty: Remove ASYNC_CLOSING checks in open()/hangup() methods

2015-10-18T04:11:29+00:00

Since at least before 2.6.30, tty drivers that do not drop the tty lock
while closing cannot observe ASYNC_CLOSING set while holding the
tty lock; this includes the tty driver's open() and hangup() methods,
since the tty core calls these methods holding the tty lock.

For these drivers, waiting for ASYNC_CLOSING to clear while opening
is not required, since this condition cannot occur. Similarly, even
when the open() method drops and reacquires the tty lock after
blocking, ASYNC_CLOSING cannot be set (again, for drivers that
do not drop the tty lock while closing).

Now that tty port drivers no longer drop the tty lock while closing
(since 'tty: Remove tty_wait_until_sent_from_close()'), the same
conditions apply: waiting for ASYNC_CLOSING to clear while opening
is not required, nor is re-checking ASYNC_CLOSING after dropping and
reacquiring the tty lock while blocking (eg., in *_block_til_ready()).

Note: The ASYNC_CLOSING flag state is still maintained since several
bitrotting drivers use it for (dubious) other purposes.

Signed-off-by: Peter Hurley 
Signed-off-by: Greg Kroah-Hartman