From: marex@denx.de (Marek Vasut) Date: Fri, 1 Nov 2013 13:18:44 +0100 Subject: [PATCH] PCI: imx6: fix imprecise abort handler In-Reply-To: <0E83723C55F66F43A6041464FE31119D418299@039-SN2MPN1-011.039d.mgd.msft.net> References: <1382056042-7299-1-git-send-email-tharvey@gateworks.com> <201310301555.02807.marex@denx.de> <0E83723C55F66F43A6041464FE31119D418299@039-SN2MPN1-011.039d.mgd.msft.net> Message-ID: <201311011318.44453.marex@denx.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Richard, [...] > > > I'm sort of dubious about imx6q_pcie_abort_handler() to begin with -- > > > it seems like it assumes that imprecise aborts are either enabled or > > > disabled. Isn't there some way it can *check* whether that's the > > > case, so it won't break if those aborts are enabled at a different > > > point in the future? > > > > The best way here would be to find a way to prevent the DWC controller > > from generating data abort on missing device _at_all_ and just make the > > read from that portion of config space be 0xffffffff or zeroes . I > > didn't find any configuration bit that would be able to do it though :( > > Richard, can you maybe check with FSL if such an option exists on the > > controller? > > [Richard] Unfortunately, discussed with IC guys, there is no such kind of > mechanism. Do you know or can you please check if there's at least some mechanism to detect whether the data abort was generated by the DWC PCIe or something else ? Best regards, Marek Vasut