From: Jason-JH.Lin <jason-jh.lin@mediatek.com> To: Jassi Brar <jassisinghbrar@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Chun-Kuang Hu <chunkuang.hu@kernel.org> Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-media@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org>, Jason-ch Chen <jason-ch.chen@mediatek.com>, Johnson Wang <johnson.wang@mediatek.com>, "Jason-JH . Lin" <jason-jh.lin@mediatek.com>, Singo Chang <singo.chang@mediatek.com>, Nancy Lin <nancy.lin@mediatek.com>, Shawn Sung <shawn.sung@mediatek.com>, <Project_Global_Chrome_Upstream_Group@mediatek.com> Subject: [PATCH v2 4/4] dt-bindings: soc: mediatek: Change mediatek,gce-events to refernece Date: Wed, 10 Jan 2024 14:35:32 +0800 [thread overview] Message-ID: <20240110063532.14124-5-jason-jh.lin@mediatek.com> (raw) In-Reply-To: <20240110063532.14124-1-jason-jh.lin@mediatek.com> Change mediatek,gce-events property to reference mediatek,gce-props.yaml instead of defining itself. Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com> --- .../bindings/soc/mediatek/mediatek,ccorr.yaml | 12 ++++-------- .../bindings/soc/mediatek/mediatek,mutex.yaml | 11 +++-------- .../bindings/soc/mediatek/mediatek,wdma.yaml | 12 ++++-------- 3 files changed, 11 insertions(+), 24 deletions(-) diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml index 4380b98b0dfe..9e03de3c721b 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml @@ -34,13 +34,6 @@ properties: 4 arguments defined in this property. Each GCE subsys id is mapping to a client defined in the header include/dt-bindings/gce/<chip>-gce.h. - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - clocks: minItems: 1 @@ -51,7 +44,10 @@ required: - mediatek,gce-events - clocks -additionalProperties: false +allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + +unevaluatedProperties: false examples: - | diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml index ba2014a8725c..6c3dafe7f9a5 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml @@ -53,13 +53,6 @@ properties: items: - description: MUTEX Clock - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - mediatek,gce-client-reg: $ref: /schemas/types.yaml#/definitions/phandle-array items: @@ -73,6 +66,8 @@ properties: a client defined in the header include/dt-bindings/gce/<chip>-gce.h. allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + - if: properties: compatible: @@ -97,7 +92,7 @@ required: - interrupts - power-domains -additionalProperties: false +unevaluatedProperties: false examples: - | diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml index 69afb329e5f4..a8d393784554 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml @@ -35,13 +35,6 @@ properties: 4 arguments defined in this property. Each GCE subsys id is mapping to a client defined in the header include/dt-bindings/gce/<chip>-gce.h. - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - power-domains: maxItems: 1 @@ -60,7 +53,10 @@ required: - clocks - iommus -additionalProperties: false +allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + +unevaluatedProperties: false examples: - | -- 2.18.0
WARNING: multiple messages have this Message-ID (diff)
From: Jason-JH.Lin <jason-jh.lin@mediatek.com> To: Jassi Brar <jassisinghbrar@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Chun-Kuang Hu <chunkuang.hu@kernel.org> Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-media@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org>, Jason-ch Chen <jason-ch.chen@mediatek.com>, Johnson Wang <johnson.wang@mediatek.com>, "Jason-JH . Lin" <jason-jh.lin@mediatek.com>, Singo Chang <singo.chang@mediatek.com>, Nancy Lin <nancy.lin@mediatek.com>, Shawn Sung <shawn.sung@mediatek.com>, <Project_Global_Chrome_Upstream_Group@mediatek.com> Subject: [PATCH v2 4/4] dt-bindings: soc: mediatek: Change mediatek,gce-events to refernece Date: Wed, 10 Jan 2024 14:35:32 +0800 [thread overview] Message-ID: <20240110063532.14124-5-jason-jh.lin@mediatek.com> (raw) In-Reply-To: <20240110063532.14124-1-jason-jh.lin@mediatek.com> Change mediatek,gce-events property to reference mediatek,gce-props.yaml instead of defining itself. Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com> --- .../bindings/soc/mediatek/mediatek,ccorr.yaml | 12 ++++-------- .../bindings/soc/mediatek/mediatek,mutex.yaml | 11 +++-------- .../bindings/soc/mediatek/mediatek,wdma.yaml | 12 ++++-------- 3 files changed, 11 insertions(+), 24 deletions(-) diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml index 4380b98b0dfe..9e03de3c721b 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml @@ -34,13 +34,6 @@ properties: 4 arguments defined in this property. Each GCE subsys id is mapping to a client defined in the header include/dt-bindings/gce/<chip>-gce.h. - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - clocks: minItems: 1 @@ -51,7 +44,10 @@ required: - mediatek,gce-events - clocks -additionalProperties: false +allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + +unevaluatedProperties: false examples: - | diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml index ba2014a8725c..6c3dafe7f9a5 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml @@ -53,13 +53,6 @@ properties: items: - description: MUTEX Clock - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - mediatek,gce-client-reg: $ref: /schemas/types.yaml#/definitions/phandle-array items: @@ -73,6 +66,8 @@ properties: a client defined in the header include/dt-bindings/gce/<chip>-gce.h. allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + - if: properties: compatible: @@ -97,7 +92,7 @@ required: - interrupts - power-domains -additionalProperties: false +unevaluatedProperties: false examples: - | diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml index 69afb329e5f4..a8d393784554 100644 --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml @@ -35,13 +35,6 @@ properties: 4 arguments defined in this property. Each GCE subsys id is mapping to a client defined in the header include/dt-bindings/gce/<chip>-gce.h. - mediatek,gce-events: - description: - The event id which is mapping to the specific hardware event signal - to gce. The event id is defined in the gce header - include/dt-bindings/gce/<chip>-gce.h of each chips. - $ref: /schemas/types.yaml#/definitions/uint32-array - power-domains: maxItems: 1 @@ -60,7 +53,10 @@ required: - clocks - iommus -additionalProperties: false +allOf: + - $ref: ../../mailbox/mediatek,gce-props.yaml# + +unevaluatedProperties: false examples: - | -- 2.18.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-10 6:35 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 6:35 [PATCH v2 0/4] Add mediatek,gce-props.yaml for other bindings reference mediatek,gce-events Jason-JH.Lin 2024-01-10 6:35 ` Jason-JH.Lin 2024-01-10 6:35 ` [PATCH v2 1/4] dt-bindings: mailbox: Add mediatek,gce-props.yaml Jason-JH.Lin 2024-01-10 6:35 ` Jason-JH.Lin 2024-01-12 7:20 ` Krzysztof Kozlowski 2024-01-12 7:20 ` Krzysztof Kozlowski 2024-01-12 8:09 ` Jason-JH Lin (林睿祥) 2024-01-12 8:09 ` Jason-JH Lin (林睿祥) 2024-01-10 6:35 ` [PATCH v2 2/4] dt-bindings: mailbox: mediatek: gce-mailbox: Add reference to gce-props.yaml Jason-JH.Lin 2024-01-10 6:35 ` Jason-JH.Lin 2024-01-10 10:36 ` Conor Dooley 2024-01-10 10:36 ` Conor Dooley 2024-01-10 16:36 ` Jason-JH Lin (林睿祥) 2024-01-10 16:36 ` Jason-JH Lin (林睿祥) 2024-01-11 17:31 ` Conor Dooley 2024-01-11 17:31 ` Conor Dooley 2024-01-12 7:44 ` Jason-JH Lin (林睿祥) 2024-01-12 7:44 ` Jason-JH Lin (林睿祥) 2024-01-15 17:23 ` Conor Dooley 2024-01-15 17:23 ` Conor Dooley 2024-01-16 8:21 ` Jason-JH Lin (林睿祥) 2024-01-16 8:21 ` Jason-JH Lin (林睿祥) 2024-01-16 17:22 ` Conor Dooley 2024-01-16 17:22 ` Conor Dooley 2024-01-17 2:24 ` Jason-JH Lin (林睿祥) 2024-01-17 2:24 ` Jason-JH Lin (林睿祥) 2024-01-10 6:35 ` [PATCH v2 3/4] dt-bindings: media: mediatek: mdp: Change mediatek,gce-events to reference Jason-JH.Lin 2024-01-10 6:35 ` Jason-JH.Lin 2024-01-12 7:22 ` Krzysztof Kozlowski 2024-01-12 7:22 ` Krzysztof Kozlowski 2024-01-12 7:53 ` Jason-JH Lin (林睿祥) 2024-01-12 7:53 ` Jason-JH Lin (林睿祥) 2024-01-10 6:35 ` Jason-JH.Lin [this message] 2024-01-10 6:35 ` [PATCH v2 4/4] dt-bindings: soc: mediatek: Change mediatek,gce-events to refernece Jason-JH.Lin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240110063532.14124-5-jason-jh.lin@mediatek.com \ --to=jason-jh.lin@mediatek.com \ --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=chunkuang.hu@kernel.org \ --cc=conor+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=jason-ch.chen@mediatek.com \ --cc=jassisinghbrar@gmail.com \ --cc=johnson.wang@mediatek.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=matthias.bgg@gmail.com \ --cc=nancy.lin@mediatek.com \ --cc=robh+dt@kernel.org \ --cc=shawn.sung@mediatek.com \ --cc=singo.chang@mediatek.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.