[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAErSpo50x1_iww5EmGXKUxbXUY2NLUxn6_yqF_3ABAjDSeFxog@mail.gmail.com>
Date: Tue, 4 Mar 2014 13:53:44 -0700
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] PCI: Use default pcibios_enable_device()
On Wed, Feb 26, 2014 at 4:41 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> Several architectures implement a simple pcibios_enable_device() that looks
> like this:
>
> int pcibios_enable_device(struct pci_dev *dev, int mask)
> {
> return pci_enable_resources(dev, mask);
> }
>
> This puts a weak version of that in the PCI core and removes the
> corresponding implementations from the architectures.
>
> s390 is slightly less trivial but the same general idea.
>
> I'd like to do the same for all the other architectures, but some (arm,
> cris, m68k, mips, unicore32, xtensa, and parts of sparc and tile) don't
> seem to use pci_claim_resource(), so BAR resource r->parent pointers
> probably aren't set, so I can't change them yet.
>
> ---
>
> Bjorn Helgaas (7):
> PCI: Add "weak" generic pcibios_enable_device() implementation
> alpha/PCI: Use default pcibios_enable_device()
> microblaze/PCI: Use default pcibios_enable_device()
> sh/PCI: Use default pcibios_enable_device()
> sparc/PCI: Use default pcibios_enable_device() (Leon only)
> tile PCI RC: Use default pcibios_enable_device()
> s390/PCI: Use generic pci_enable_resources()
>
>
> arch/alpha/kernel/pci.c | 6 ------
> arch/microblaze/pci/pci-common.c | 5 -----
> arch/s390/pci/pci.c | 13 +------------
> arch/sh/drivers/pci/pci.c | 5 -----
> arch/sparc/kernel/leon_pci.c | 5 -----
> arch/tile/kernel/pci_gx.c | 12 ------------
> drivers/pci/pci.c | 5 +++++
> 7 files changed, 6 insertions(+), 45 deletions(-)
I applied these to pci/resource for v3.15.
--
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