diff options
| author | Lennart Sorensen <[email protected]> | 2011-06-01 14:38:41 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2011-06-07 09:25:34 -0700 |
| commit | af99d6f0037d970084b03d9690f50e34d6f70dae (patch) | |
| tree | 4f2480b9be4f29e55f62c6d343c905dea5dc643a /net/lapb/lapb_timer.c | |
| parent | 163baa33552bb1c08b6bf109319505570658a8f3 (diff) | |
serial: ioremap warning fix for jsm driver.
I saw a warning about ioremap from the jsm driver on a system which
looked like this:
resource map sanity check conflict: 0xe0200800 0xe02017ff 0xe0200800 0xe0200fff 0000:01:08.0
Turns out the warning is valid. The jsm driver has been asking to ioremap
0x1000 forever, but in fact only 8 port chips have 0x1000 bytes of memory.
4 port chips have 0x800 and 2 port chips have 0x400 according to the
data sheet. It makes more sense to map the size of the region rather
than a hard coded value. If you happen to have the region legitimately
mapped to a base address that is not 4K aligned, ioremap complains
otherwise.
Signed-off-by: Len Sorensen <[email protected]>
Acked-by: Alan Cox <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions