diff options
author | Marek BehĂșn <marek.behun@nic.cz> | 2019-08-07 15:01:56 +0200 |
---|---|---|
committer | Stefan Roese <sr@denx.de> | 2019-08-12 13:59:31 +0200 |
commit | 193a1e9f196b7fb7e913a70936c8a49060a1859c (patch) | |
tree | 1dbaaee4259272ba2b244c07320c8c91ac6c6552 /board/keymile/km83xx/km83xx.c | |
parent | 6de5a717c7a19cedbb2867a39af1daca06f3b434 (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 <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>
Diffstat (limited to 'board/keymile/km83xx/km83xx.c')
0 files changed, 0 insertions, 0 deletions