[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAErSpo5A0At+U4gZ6s6ER2vzBzRiV9iJVkZtGH+gnAWeT+N=Ag@mail.gmail.com>
Date: Mon, 1 Aug 2011 09:21:11 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Deng-Cheng Zhu <dengcheng.zhu@...il.com>
Cc: Ralf Baechle <ralf@...ux-mips.org>, jbarnes@...tuousgeek.org,
torvalds@...ux-foundation.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
eyal@...s.com, zenon@...s.com
Subject: Re: [PATCH 1/2] PCI: make pci_claim_resource() work with conflict
resources as appropriate
On Mon, Aug 1, 2011 at 4:13 AM, Deng-Cheng Zhu <dengcheng.zhu@...il.com> wrote:
> It was found that PCI quirks claim resources (by calling pci_claim_resource())
> *BEFORE* pcibios_fixup_bus() is called. In pcibios_fixup_bus(),
> pci_bus->resource[0] for the root bus DOES point to msc_io_resource. If PCI
> quirks do the resource claim after the arch-defined pcibios_fixup_bus() being
> called, then the problem with Malta goes away.
Oh, I see. pcibios_fixup_bus() copies the hose resources to the root
bus pci_bus structure. I think that's bogus because we have the
interval between mips_pcibios_init() and pcibios_fixup_bus() where the
root bus resources are incorrect.
I think it would be better to set up the resources correctly right
away, as we do on x86. In fact, I'm dubious about pci_create_bus()
filling in ioport_resource and iomem_resource as defaults -- that's
never what we really want there, and we have to rely on the arch
coming back later to fix it up.
I'd like to see some sort of restructuring there so we could pass in a
list of resources at the time we create the bus.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists