summaryrefslogtreecommitdiff
path: root/include/linux/stringify.h
diff options
context:
space:
mode:
authorMarek BehĂșn <[email protected]>2019-08-07 15:01:56 +0200
committerStefan Roese <[email protected]>2019-08-12 13:59:31 +0200
commit193a1e9f196b7fb7e913a70936c8a49060a1859c (patch)
tree1dbaaee4259272ba2b244c07320c8c91ac6c6552 /include/linux/stringify.h
parent6de5a717c7a19cedbb2867a39af1daca06f3b434 (diff)
pci: pci_mvebu: set BAR0 after memory space is set
The non-DM version of this driver used to set BAR0 register after the calls to pci_set_region. I found out that for some strange reason the ath10k driver in kernel fails to work if this is done the other way around. I know that Linux's driver should not depend on how U-Boot does things, but for some strange reason it does and this seems to be the simplest solution. Fix it since it caused regressions on Omnia. Signed-off-by: Marek BehĂșn <[email protected]> Cc: Stefan Roese <[email protected]> Cc: Dirk Eibach <[email protected]> Cc: Mario Six <[email protected]> Cc: Chris Packham <[email protected]> Cc: Phil Sutter <[email protected]> Cc: VlaoMao <[email protected]> Tested-by: Chris Packham <[email protected]> Reviewed-by: Stefan Roese <[email protected]> Signed-off-by: Stefan Roese <[email protected]>
Diffstat (limited to 'include/linux/stringify.h')
0 files changed, 0 insertions, 0 deletions