[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <520BFA0C.5070001@wwwdotorg.org>
Date: Wed, 14 Aug 2013 15:43:40 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Thierry Reding <thierry.reding@...il.com>
CC: Russell King <linux@....linux.org.uk>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Jason Cooper <jason@...edaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
Thierry Reding <treding@...dia.com>
Subject: Re: [RFC 3/3] PCI: tegra: Support driver unbinding
On 08/13/2013 05:12 AM, Thierry Reding wrote:
> Implement the platform driver's .remove() callback to free all resources
> allocated during driver setup and call pci_common_exit() to cleanup ARM
> specific datastructures. Unmap the fixed PCI I/O mapping by calling the
> new pci_iounmap_io() function in the new .teardown() callback.
>
> Finally, no longer set the .suppress_bind_attrs field to true to allow
> the driver to unbind from a device.
> +static int tegra_pcie_remove(struct platform_device *pdev)
> +{
> + struct tegra_pcie *pcie = platform_get_drvdata(pdev);
> + struct tegra_pcie_bus *bus, *tmp;
> + int err;
> +
> + pci_common_exit(&pcie->sys);
> +
> + list_for_each_entry_safe(bus, tmp, &pcie->busses, list) {
> + vunmap(bus->area->addr);
> + kfree(bus);
> + }
> +
> + if (IS_ENABLED(CONFIG_PCI_MSI)) {
> + err = tegra_pcie_disable_msi(pcie);
> + if (err < 0)
> + return err;
> + }
Wouldn't it make sense to do that as early as possible in the function,
to make sure that no MSI accidentally fires after some of the cleanup
has already happened?
> +
> + err = tegra_pcie_put_resources(pcie);
> + if (err < 0)
> + return err;
> +
> + return 0;
> +}
--
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