summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorJie Gan <jie.gan@oss.qualcomm.com>2026-11-10 09:21:17 +0800
committerSuzuki K Poulose <suzuki.poulose@arm.com>2026-11-10 10:34:26 +0000
commitf599d281541edd9d7ee64bcbe4e41d410c527a4a (patch)
treef9427021550991b739530db76961a6bd951e95f8 /scripts/Makefile.thinlto
parent50e7796ab751ad2b5e5501fcbd7fe8739c498a4f (diff)
downloadlinux-next-f599d281541edd9d7ee64bcbe4e41d410c527a4a.tar.gz
linux-next-f599d281541edd9d7ee64bcbe4e41d410c527a4a.zip
arm64: dts: qcom: sm8750: bind traceNoC on the platform bus
The traceNoC node used the "qcom,coresight-tnoc", "arm,primecell" compatible, which places the device on the AMBA bus. To bind an AMBA device, the bus reads the peripheral and component ID registers (PID/CID) at the top of the device's register block and matches them against the primecell ID. The traceNoC exposes the CID registers, but the Component ID value returned by the hardware is 0x00000000 instead of a valid AMBA Component ID, so the match never succeeds, the AMBA probe fails, and the device is left stuck in deferred probe indefinitely. Drop the "arm,primecell" entry and use the standalone "qcom,coresight-tnoc" compatible, which binds via the platform driver by compatible string and does not rely on the component ID register at all. This lets the device probe on hardware that does not return a valid CID, while remaining an Aggregator TNOC that retains ATID functionality. Fixes: ebd1eb365cae ("arm64: qcom: dts: sm8750: add coresight nodes") Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com> Link: https://lore.kernel.org/r/20261110-fix-trace-noc-probe-issue-v7-4-2f06905c77fe@oss.qualcomm.com
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions