The option exposing CoreSight CTI integration registers is
CONFIG_CORESIGHT_CTI_INTEGRATION_REGS, not
CONFIG_CORESIGHT_CTI_INTEGRATION_TEST.

Fixes: b39b46fb9c6a ("dt-bindings: arm: Adds CoreSight CTI hardware definitions")
Assisted-by: Codex:gpt-5.6-sol
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
 Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
index 949444aba1f8b..345e93ca39f96 100644
--- a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
+++ b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
@@ -43,7 +43,7 @@ description: |
   connection. Any user / client application will require additional information
   on the connections between the CTI and other components for correct operation.
   This information might be found by enabling the Integration Test registers in
-  the driver (set CONFIG_CORESIGHT_CTI_INTEGRATION_TEST in Kernel
+  the driver (set CONFIG_CORESIGHT_CTI_INTEGRATION_REGS in Kernel
   configuration). These registers may be used to explore the trigger connections
   between CTI and other CoreSight components.
 
-- 
2.53.0

On Sat, Aug 22, 2026 at 10:19:12AM +0200, Karl Mehltretter wrote:
> The option exposing CoreSight CTI integration registers is
> CONFIG_CORESIGHT_CTI_INTEGRATION_REGS, not
> CONFIG_CORESIGHT_CTI_INTEGRATION_TEST.

DT bindings should not be referring to kernel kconfig symbols (or 
anything else in the kernel) in the first place.

Rob

On 9/16/26 20:57, Rob Herring wrote:
> On Sat, Aug 22, 2026 at 10:19:12AM +0200, Karl Mehltretter wrote:
>> The option exposing CoreSight CTI integration registers is
>> CONFIG_CORESIGHT_CTI_INTEGRATION_REGS, not
>> CONFIG_CORESIGHT_CTI_INTEGRATION_TEST.
> 
> DT bindings should not be referring to kernel kconfig symbols (or
> anything else in the kernel) in the first place.
> 

Agreed - the comment in general is correct but the last sentence in the 
paragraph should drop the config reference. e.g.

"This information might be found by using the CTI Integration Test 
registers to explore the trigger connections between CTI and other 
CoreSight components."

The coresight/KConfig file itself adequately documents adding this 
support and the perils therein.

Mike


> Rob