diff options
author | Anton Vorontsov <avorontsov@ru.mvista.com> | 2009-09-19 13:13:20 -0700 |
---|---|---|
committer | Live-CD User <linux@linux.site> | 2009-09-19 13:13:20 -0700 |
commit | 24d481ecae1614cf02e638c8dce9b6e8bf230603 (patch) | |
tree | c41353bc639c778886ac969c884702851a745854 /fs/readdir.c | |
parent | 1c2f04937b3e397a5695953c6b82aa4c77d21eb8 (diff) | |
download | linux-3.10-24d481ecae1614cf02e638c8dce9b6e8bf230603.tar.gz linux-3.10-24d481ecae1614cf02e638c8dce9b6e8bf230603.tar.bz2 linux-3.10-24d481ecae1614cf02e638c8dce9b6e8bf230603.zip |
8250: Now honours baud rate lower bounds
A platform clock drives 8250 ports in most SOC systems, the clock
might run at high frequencies, and so it's not always possible to
downscale uart clock to a desired value.
Currently the 8250 uart driver accepts not supported baud rates, and
what is worse, it is doing this silently, and then passes not accepted
values to a new termios, so userspace has no chance to catch this kind
of errors (userspace verifies that settings were accepted by reading
back and comparing the settings).
This patch fixes the issue by passing minimum baud rate to the
uart_get_baud_rate() call, the call should take care of all bounds,
so userspace should now report:
# stty -F /dev/ttyS0 speed 300
115200
stty: /dev/ttyS0: unable to perform all requested operations
p.s. uart_get_baud_rate() falls back to 9600, which still might be too
low for some 10 GHz platforms, but that's a separate issue, and
we can wait with fixing this till we find such a platform.
Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/readdir.c')
0 files changed, 0 insertions, 0 deletions