Re: trouble with PCI: Call pci_read_bridge_bases() from core instead of arch code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 14, 2015 at 9:28 AM, Lorenzo Pieralisi
<lorenzo.pieralisi@xxxxxxx> wrote:
> On Mon, Sep 14, 2015 at 05:05:50PM +0100, Yinghai Lu wrote:
>> We could just revert
>> dff22d2054b5 (" PCI: Call pci_read_bridge_bases() from core instead of
>> arch code")
>> instead.
>
> Sure, but still that does not explain why the old bridge aperture size
> matters while sizing the bridge aperture on first bridge scan, I
> still have no answer for that and I would like to get one.
>
> As far as I understand we could just rework:
>
> commit d65245c3297ac63abc51a976d9 ("PCI: don't shrink bridge resources")
>
> to make sure that old size is taken into account only when the core
> code tries to reallocate resources, I think that dff22d2054b5 unearthed
> a problem instead of creating one but I am open to suggestions.

if arch code called pci_read_bridge_bases() via pcibios_fixup_bus(),
then it need to have
to call pcibios_allocate_bus_resources() later.

but now arm (mips ?)  does not have calling pcibios_allocate_bus_resources().

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux