aboutsummaryrefslogtreecommitdiff
path: root/drivers/ram/stm32mp1/stm32mp1_tuning.c
diff options
context:
space:
mode:
authorPali Rohár <pali@kernel.org>2021-11-11 16:35:42 +0100
committerStefan Roese <sr@denx.de>2021-12-21 07:40:26 +0100
commit4a1a593d1783e5292cd48ea66d0b13977aa16d86 (patch)
treeb564acc8642d27956b1030e6a4f821b19b9db82b /drivers/ram/stm32mp1/stm32mp1_tuning.c
parent4afab30caea3211032710c4298a8839d3254e7f7 (diff)
pci: pci_mvebu: Move setup for BAR[0] where other BARs are setup
Function mvebu_pcie_setup_wins() sets up all other BARs, so move setup of BAR[0] to this function to have common code at one place. In the past, commit 193a1e9f196b ("pci: pci_mvebu: set BAR0 after memory space is set") moved setup of BAR[0] to another location, due to ath10k not working in kernel, but the reason why was unknown, but it seems to work now, and we think the issue then was cause by the PCIe Root Port presenting itself as a Memory Controller and therefore U-Boot's code have overwritten the BAR. Since the driver now ignores any write operations to PCIe Root Port BARs, this should not be an issue anymore. Signed-off-by: Pali Rohár <pali@kernel.org> Signed-off-by: Marek Behún <marek.behun@nic.cz> Reviewed-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'drivers/ram/stm32mp1/stm32mp1_tuning.c')
0 files changed, 0 insertions, 0 deletions