[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <38ffc6dffee2ccc70db07efcd04acdeb5b73ebc1.camel@nxp.com>
Date: Tue, 26 Feb 2019 13:26:43 +0000
From: Leonard Crestez <leonard.crestez@....com>
To: "stefan@...er.ch" <stefan@...er.ch>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jingoohan1@...il.com" <jingoohan1@...il.com>,
"lorenzo.pieralisi@....com" <lorenzo.pieralisi@....com>,
"gustavo.pimentel@...opsys.com" <gustavo.pimentel@...opsys.com>,
"tpiepho@...inj.com" <tpiepho@...inj.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"l.stach@...gutronix.de" <l.stach@...gutronix.de>
Subject: Re: [PATCH v8] PCI: imx6: limit DBI register length
On Tue, 2019-02-26 at 14:06 +0100, Stefan Agner wrote:
> Define the length of the DBI registers and limit config space to its
> length. This makes sure that the kernel does not access registers
> beyond that point, avoiding the following abort on a i.MX 6Quad:
>
> +static void imx6_pcie_quirk(struct pci_dev *dev)
> +{
> + struct pci_bus *bus = dev->bus;
> + struct pcie_port *pp = bus->sysdata;
> +
> + /* Bus parent is the PCI bridge, its parent is this platform driver */
> + if (!bus->dev.parent || !bus->dev.parent->parent)
> + return;
> +
> + /* Make sure we only quirk devices associated with this driver */
> + if (bus->dev.parent->parent->driver != &imx6_pcie_driver.driver)
> + return;
This looks like it would be enough to prevent interfering with other
dwc-based pci drivers.
Reviewed-by: Leonard Crestez <leonard.crestez@....com>
Powered by blists - more mailing lists