diff options
author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2006-04-30 11:15:58 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2006-04-30 11:15:58 +0100 |
commit | 85835f442e5bbf9d3b8f6e574751da8db77016d2 (patch) | |
tree | 28bc3bd2734daf51474dcfb255100a0050ffc29c /drivers/serial/8250.c | |
parent | 68ac64cd3fd89fdaa091701f6ab98a9065e9b1b5 (diff) | |
download | op-kernel-dev-85835f442e5bbf9d3b8f6e574751da8db77016d2.zip op-kernel-dev-85835f442e5bbf9d3b8f6e574751da8db77016d2.tar.gz |
[SERIAL] AMD Alchemy UART: claim memory range
I've noticed that the 8250/Au1x00 driver (drivers/serial/8250_au1x00.c)
doesn't claim UART memory ranges and uses wrong (KSEG1-based) UART
addresses instead of the physical ones.
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers/serial/8250.c')
-rw-r--r-- | drivers/serial/8250.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c index 674b15c..d641ac4 100644 --- a/drivers/serial/8250.c +++ b/drivers/serial/8250.c @@ -1906,6 +1906,9 @@ static int serial8250_request_std_resource(struct uart_8250_port *up) int ret = 0; switch (up->port.iotype) { + case UPIO_AU: + size = 0x100000; + /* fall thru */ case UPIO_MEM: if (!up->port.mapbase) break; @@ -1938,6 +1941,9 @@ static void serial8250_release_std_resource(struct uart_8250_port *up) unsigned int size = 8 << up->port.regshift; switch (up->port.iotype) { + case UPIO_AU: + size = 0x100000; + /* fall thru */ case UPIO_MEM: if (!up->port.mapbase) break; |