Re: [PATCH] ARM: add PCI hotplug support

From: Bjorn Helgaas
Date: Fri Mar 20 2015 - 19:22:32 EST


On Tue, Mar 17, 2015 at 12:22:32PM +0000, Ben Dooks wrote:
> Hotplug on PCIe should work with ARM, however the necessary
> PCIe hotplug is not availale as the menu items for PCI hotplug

"available"

> have not been included.
>
> Add the include of PCI hotplug support to the ARM main Kconfig
> so that it can be selected.
>
> The only issue that was found during this is that the PCI code
> did not assign interrupts properly to newly probed devices. This
> will need to be fixed for any interrupt capable devices.

Yep, this is a known PCI problem, at least if you're referring to
the fact that pci_fixup_irqs() only happens for devices present at
boot-time. I would love for somebody to fix that generically.

I would also like to squash together the PCI, PCIe, and PCI hotplug Kconfig
options so arches would only have to include drivers/pci/Kconfig.

> This has been tested on a Marvell 88F6281 with a TI XIO3130
> PCIe bridge (with hotplug enabled) and fixes for IRQ assignment
> added.
>
> Signed-off-by: Ben Dooks <ben.dooks@xxxxxxxxxxxxxxx>

I assume this will be handled via an ARM tree, but if you want it:

Acked-by: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>

> --
> CC: Linux ARM Kernel list <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>
> CC: Russell King <linux@xxxxxxxxxxxxxxxx>
> CC: Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
> CC: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
> CC: Linux PCI List <linux-pci@xxxxxxxxxxxxxxx>
> ---
> arch/arm/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 9f1f09a..4574ab4 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1302,6 +1302,7 @@ config PCI_HOST_ITE8152
> select DMABOUNCE
>
> source "drivers/pci/Kconfig"
> +source "drivers/pci/hotplug/Kconfig"
> source "drivers/pci/pcie/Kconfig"
>
> source "drivers/pcmcia/Kconfig"
> --
> 2.1.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/