On 11 April 2016 at 10:57, Mark Rutland <mark.rutland@xxxxxxx> wrote: > Please Cc the device tree mailing list (devicetree@xxxxxxxxxxxxxxx) when > sending device tree patches. Sorry, I'll remember to do that in future. > On Sat, Apr 09, 2016 at 11:50:23PM +0200, Rafał Miłecki wrote: >> Some devices (e.g. Northstar ones) may have bridges that forward >> harmless errors to the ARM core. In such case we need an option to >> add a handler ignoring them. >> >> Signed-off-by: Rafał Miłecki <zajec5@xxxxxxxxx> >> --- >> .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 6 ++++++ >> drivers/pci/host/pcie-iproc-platform.c | 2 ++ >> drivers/pci/host/pcie-iproc.c | 17 +++++++++++++++++ >> drivers/pci/host/pcie-iproc.h | 1 + >> 4 files changed, 26 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt >> index 01b88f4..c91b20a 100644 >> --- a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt >> +++ b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt >> @@ -22,6 +22,12 @@ Optional properties: >> >> - brcm,pcie-ob: Some iProc SoCs do not have the outbound address mapping done >> by the ASIC after power on reset. In this case, SW needs to configure it >> +- brcm,pcie-hook-abort-handler: During PCI bus probing (device enumeration) >> + there can be errors that are expected and harmless. Unfortunately some bridges >> + can't be configured to ignore them and they forward them to the ARM core >> + triggering die(). >> + This property should be set in such case, it will make driver add its own >> + handler ignoring such errors. > > Rather than describing what the kernel should do, this should describe > the property of the hardware (e.g. this should be named something like > brcm,spurious-probing-abort). Florian pointed it to me too, I'll use a better property name if we decide to go this way. Thanks for your comment. -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
