aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorThomas Pfaff <tpfaff@pcs.com>2014-04-23 12:33:22 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-04-24 15:38:22 -0700
commit7deb39ed8d9494ea541bcaa69b56036a94f79dc2 (patch)
tree8f7f242c45c98cd06200846e23142b363594cb5a /include
parentserial: samsung: Change barrier() to cpu_relax() in console output (diff)
downloadlinux-dev-7deb39ed8d9494ea541bcaa69b56036a94f79dc2.tar.xz
linux-dev-7deb39ed8d9494ea541bcaa69b56036a94f79dc2.zip
serial_core: fix uart PORT_UNKNOWN handling
While porting a RS485 driver from 2.6.29 to 3.14, i noticed that the serial tty driver could break it by using uart ports that it does not own : 1. uart_change_pm ist called during uart_open and calls the uart pm function without checking for PORT_UNKNOWN. The fix is to move uart_change_pm from uart_open to uart_port_startup. 2. The return code from the uart request_port call in uart_set_info is not handled properly, leading to the situation that the serial driver also thinks it owns the uart ports. This can triggered by doing following actions : setserial /dev/ttyS0 uart none # release the uart ports modprobe lirc-serial # or any other device that uses the uart setserial /dev/ttyS0 uart 16550 # gives no error and the uart tty driver # can use the ports as well Signed-off-by: Thomas Pfaff <tpfaff@pcs.com> Reviewed-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions