pci: pci_mvebu: set BAR0 after memory space is set
authorMarek Behún <marek.behun@nic.cz>
Wed, 7 Aug 2019 13:01:56 +0000 (15:01 +0200)
committerStefan Roese <sr@denx.de>
Mon, 12 Aug 2019 11:59:31 +0000 (13:59 +0200)
commit193a1e9f196b7fb7e913a70936c8a49060a1859c
tree1dbaaee4259272ba2b244c07320c8c91ac6c6552
parent6de5a717c7a19cedbb2867a39af1daca06f3b434
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 <marek.behun@nic.cz>
Cc: Stefan Roese <sr@denx.de>
Cc: Dirk Eibach <dirk.eibach@gdsys.cc>
Cc: Mario Six <mario.six@gdsys.cc>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Phil Sutter <phil@nwl.cc>
Cc: VlaoMao <vlaomao@gmail.com>
Tested-by: Chris Packham <judge.packham@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Signed-off-by: Stefan Roese <sr@denx.de>
drivers/pci/pci_mvebu.c