bcma: don't map/unmap a subset of the PCI config space
authorNathan Hintz <nlhintz@hotmail.com>
Sat, 12 Jan 2013 10:46:15 +0000 (02:46 -0800)
committerJohn W. Linville <linville@tuxdriver.com>
Mon, 14 Jan 2013 20:10:41 +0000 (15:10 -0500)
commit447d7e25be462329268f279bef2f6faa986a5185
tree4692b6b4cda88685486d2a7054220edf0fc39262
parenta35ab937cb27ec8c00b6f13cade93dc10e22b670
bcma: don't map/unmap a subset of the PCI config space

For PCI config space access offsets < 256 for device '0',
bcma_extpci_write_config performs an 'ioremap_nocache' on a 4 byte
section of the PCI config space (an area that has already
previously been mapped), and then subsequently unmaps that 4 byte
section.  This can't be a good thing for future read access from
that now unmapped location.  Modify the config space writes to use
the existing access functions (similar to how it is done for the reads).

Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/bcma/driver_pci_host.c