dmesg -a | grep dpaa2_mcp27
dpaa2_mcp27: <DPAA2 MC portal> iomem 0x80c010000-0x80c01003f at dpmcp (id=1) on dpaa2_rc0
dpaa2_mcp27: dpaa2_mcp_attach: failed to reset DPMCP: id=1, error=6
device_attach: dpaa2_mcp27 attach returned 6
dpaa2_mcp27: <DPAA2 MC portal> iomem 0x80c010000-0x80c01003f at dpmcp (id=1) on dpaa2_rc0
dpaa2_rc0: resource entry 0 type 3 for child dpaa2_mcp27 is busy
dpaa2_mcp27: dpaa2_mcp_attach: failed to allocate resources
device_attach: dpaa2_mcp27 attach returned 6
dpaa2_mcp27: <DPAA2 MC portal> iomem 0x80c010000-0x80c01003f at dpmcp (id=1) on dpaa2_rc0
dpaa2_rc0: resource entry 0 type 3 for child dpaa2_mcp27 is busy
dpaa2_mcp27: dpaa2_mcp_attach: failed to allocate resources
device_attach: dpaa2_mcp27 attach returned 6
Seen this on the LS1088/FDT but never on the LX2160/ACPI before (not sure if FDT/ACPI are relevant).
Opening to keep pan eye on it and debug and not forget.
dmesg -a | grep dpaa2_mcp27Seen this on the LS1088/FDT but never on the LX2160/ACPI before (not sure if FDT/ACPI are relevant).
Opening to keep pan eye on it and debug and not forget.