On 31 October 2016 at 23:05, Scott Branden <scott.branden@xxxxxxxxxxxx> wrote: > On 16-10-31 02:56 PM, Florian Fainelli wrote: >> - fixups the aborts in the kernel, look where they come from, by using >> some bit of magic, looking at PCIe registers and whatnot (provided that >> is even possible), not too hard, but can take a while, and is error prone > > Option 4 sounds like the proper solution - check the range the abort is due > to the PCI device enumeration and only ignore those aborts. This was already suggested by Arnd: http://lists.infradead.org/pipermail/linux-arm-kernel/2016-April/422873.html and Ray was checking some internal datasheets, but I'm afraid he never found info on checking if error was caused by PCIe controller. Maybe we could think about some BCM5301X API (extra symbol exported by arch code) for starting ignoring aborts and stopping that. We could ignore aborts during scanning only but honestly it sounds like a bit hacky solution to me. >> I can certainly advocate that option 3 is the one that gives a working >> device, and this is what matters from a distribution perspective like >> LEDE/OpenWrt. >> > Since I don't use BCM5301x option 3 is fine by me. So for it seems like the best solution to me, but I'm open for changes if someone points another that is clean & better one. -- Rafał -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
