Received: by 2002:a05:7412:2a8c:b0:e2:908c:2ebd with SMTP id u12csp1503425rdh; Mon, 25 Sep 2023 15:08:39 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGq5UTLXvmoGUaqm02Kc32c5dZdyydN+W46iPEy6MqvhdDDLZ8XDA0wzOIlyEwSL0FaTHQX X-Received: by 2002:a05:6e02:1946:b0:34b:ae9b:d039 with SMTP id x6-20020a056e02194600b0034bae9bd039mr10302337ilu.18.1695679719596; Mon, 25 Sep 2023 15:08:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695679719; cv=none; d=google.com; s=arc-20160816; b=I1SYyE/xpscmwDTiSFuDDuHd1OBFo70wQ5oIfZTUwO5Q9lwLSKVF5t9PTtDaVJAdTQ mUcoAaiezemSRNrDUAhapGIbMRHb/5tfX6c5uKNu+CVr7r5DZ56uXLEr3+yGIE/eE+d+ y0sOM+9YV8RLxnEm8w3CBFQDO2Sd0PUXjfkmNbpF3HTVONxDQwW0fE3AYAWcCO3ZpfvU hqF20QFjKkozxRIcCaIV8uEtzRmJkELElrEBw9taua032GEYVRRyDFwTpNKXxKRUjzFJ y8+SY7T9NfwOjNgU6ryXQGoQDtCmAie9AnXEZUHgPutoyWIASJRMQ8gikl3CPhRyTt+s xKpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=8Lpi4L35EpEcFkFdbaQw2NZqBHY2yxUr7rmNsNfyJbI=; fh=QJHwarUSeo+o/bO7iovvCkMYfaqQAw3RHX8SlU1RgZI=; b=BiJvuLFJxzRfvUmCmiIpiDA4dMTI8XkrqQysnP9pv5w2Ym+ygvPx1ZcaFCWONIuSxh /59oqghi+OR8gmYZZ+4ay/8uD62HKrt/zaCRcViO1uhxXOgoDF2lAoYHf/cs6xJRxwtd 7OHDkT+HKOLCWEZurahMB4W92uq0RS4rV4ys/7QXpZ7S7pQF2FikSouzmmnPzRVucDsF qtAjyKen3S0PIDKR5xdvf1xYQRF1ynrm8lnnDg62cdZ3mqK0uEFZBVzsxdnxOe336na8 QergaZMFGn4CDN+7oVD4oVdfpPqn39MyJzTwFfW+Y16+X0pjqV3pKwRvLQ3JewhltfjN AaYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=c4+YavJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from groat.vger.email (groat.vger.email. [23.128.96.35]) by mx.google.com with ESMTPS id k64-20020a638443000000b0056ad77ddd4csi11307619pgd.438.2023.09.25.15.08.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Sep 2023 15:08:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=c4+YavJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 78D29801BF66; Mon, 25 Sep 2023 15:05:39 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230132AbjIYWFl (ORCPT + 99 others); Mon, 25 Sep 2023 18:05:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53918 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229921AbjIYWFj (ORCPT ); Mon, 25 Sep 2023 18:05:39 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 056E7180 for ; Mon, 25 Sep 2023 15:05:33 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1A5D5C433C8; Mon, 25 Sep 2023 22:05:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1695679532; bh=FmZZfIJ7IjqsgMWeiyIf/YJBP5eLlOuuOdfPlbttg+A=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=c4+YavJePbk5XQhufDOKssIq1IW9tGV2SLanMeov18NhO3LjgeJSUdunp+PCdUPid cv6cNmJubZL8ILBF8xH3B9XfYk3Epuj212eYufl9Z3GBSGCaWPJ2Y924Ftlif9vhST JFp6ozAm1b+YgUOl5QeIamrwJ2spycsWUBPhLIQTP2IJE9iRqY1KR+DiviCyZyOW7i GvlMAIMvxBNT7LGNXXu+MrY9uKnrq+6zNLdGHwCWem90eIqJ/ew9VaKt8x6V8kNh+D ivOOj6JOuYTIrtAiCV8UZusUZLTFS0iyvQZOgirkJt7JF+yUXTFLYmaiFmhG2vXIoc qJv/N3jqi16gA== Received: (nullmailer pid 2027056 invoked by uid 1000); Mon, 25 Sep 2023 22:05:30 -0000 From: Rob Herring To: Suzuki K Poulose , Mike Leach , James Clark , Leo Yan , Krzysztof Kozlowski , Conor Dooley Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 2/2] dt-bindings: arm,coresight-cti: Add missing additionalProperties on child nodes Date: Mon, 25 Sep 2023 17:05:06 -0500 Message-Id: <20230925220511.2026514-2-robh@kernel.org> X-Mailer: git-send-email 2.40.1 In-Reply-To: <20230925220511.2026514-1-robh@kernel.org> References: <20230925220511.2026514-1-robh@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Mon, 25 Sep 2023 15:05:39 -0700 (PDT) Just as unevaluatedProperties or additionalProperties are required at the top level of schemas, they should (and will) also be required for child node schemas. That ensures only documented properties are present for any node. Adding additionalProperties constraint on 'trig-conns' nodes results in warnings that 'cpu' and 'arm,cs-dev-assoc' are not allowed. These are already defined for the parent node, but need to be duplicated for the child node. Drop the free form description that the properties also apply to the child nodes. Signed-off-by: Rob Herring --- .../bindings/arm/arm,coresight-cti.yaml | 33 ++++++++++++++----- 1 file changed, 24 insertions(+), 9 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml index b9bdfc8969cd..2d5545a2b49c 100644 --- a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml +++ b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml @@ -93,9 +93,7 @@ properties: cpu: description: - Handle to cpu this device is associated with. This must appear in the - base cti node if compatible string arm,coresight-cti-v8-arch is used, - or may appear in a trig-conns child node when appropriate. + Handle to cpu this CTI is associated with. power-domains: maxItems: 1 @@ -112,12 +110,12 @@ properties: description: defines a phandle reference to an associated CoreSight trace device. When the associated trace device is enabled, then the respective CTI - will be enabled. Use in a trig-conns node, or in CTI base node when - compatible string arm,coresight-cti-v8-arch used. If the associated - device has not been registered then the node name will be stored as - the connection name for later resolution. If the associated device is - not a CoreSight device or not registered then the node name will remain - the connection name and automatic enabling will not occur. + will be enabled. Use in CTI base node when compatible string + arm,coresight-cti-v8-arch used. If the associated device has not been + registered then the node name will be stored as the connection name for + later resolution. If the associated device is not a CoreSight device or + not registered then the node name will remain the connection name and + automatic enabling will not occur. # size cells and address cells required if trig-conns node present. "#size-cells": @@ -129,6 +127,8 @@ properties: patternProperties: '^trig-conns@([0-9]+)$': type: object + additionalProperties: false + description: A trigger connections child node which describes the trigger signals between this CTI and another hardware device. This device may be a CPU, @@ -140,6 +140,21 @@ patternProperties: reg: maxItems: 1 + cpu: + description: + Handle to cpu this trigger connection is associated with. + + arm,cs-dev-assoc: + $ref: /schemas/types.yaml#/definitions/phandle + description: + defines a phandle reference to an associated CoreSight trace device. + When the associated trace device is enabled, then the respective CTI + will be enabled. If the associated device has not been registered + then the node name will be stored as the connection name for later + resolution. If the associated device is not a CoreSight device or + not registered then the node name will remain the connection name + and automatic enabling will not occur. + arm,trig-in-sigs: $ref: /schemas/types.yaml#/definitions/uint32-array minItems: 1 -- 2.40.1