[PATCH] PCI: mvebu: Take control of mbus windows setup by the firmware
thomas.petazzoni at free-electrons.com
Thu Nov 10 00:30:37 PST 2016
On Wed, 26 Oct 2016 11:44:40 -0600, Jason Gunthorpe wrote:
> The firmware may setup the mbus to access PCI-E and indicate this
> has happened with a ranges mapping for the PCI-E ID. If this happens
> then the mbus setup and the pci dynamic setup conflict, creating
> Have PCI-E assume control of the firmware specified default mapping by
> setting the value of the bridge window to match the firmware mapping.
> Signed-off-by: Jason Gunthorpe <jgunthorpe at obsidianresearch.com>
Sorry for the late feedback. I am not sure to fully understand what you
are trying to do here.
However, one thing that confuses me specifically is how can the kernel
get any MBus mapping set up by the firmware? Indeed, when the
mvebu-mbus driver initializes, it destroys all existing MBus windows
that might have been left by the firmware/bootloader:
static int __init mvebu_mbus_common_init(struct mvebu_mbus_state *mbus,
for (win = 0; win < mbus->soc->num_wins; win++)
Why does Linux needs to rely on what the firmware has setup in terms of
MBus windows? Why can't Linux just find out the right BAR base/size
like it is doing for all other devices?
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
More information about the linux-arm-kernel