Hi Jie,

On Fri, Mar 20, 2026 at 04:44:54PM +0800, Jie Gan wrote:

[...]

It's about the coresight_find_device_by_fwnode() returns NULL, resulting in -EPROBE_DEFER. So the probe process will re-start after several seconds, but always failed because we have a "disabled" device node in DT(we can see this device in DT, but it never becomes available). It's ok if the device only has one remote device, but has issue with more than one remote devices.

Consider below situation:

  device0

| | device1 device2(status = "disabled")

The probe of device0 succeeds only when device1 and device2 are available at probe time. But I think it's ok to probe the device0 only with device1 available.

Thanks a lot for details. We might need to report warning or error if all remote endpoints fail (e.g., device1/device2 both are disabled), this is a rare case so would be low priority.

For this patch:

Reviewed-by: Leo Yan leo.yan@arm.com