From: Rob Herring <robh@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Bao Cheng Su <baocheng.su@siemens.com>,
Diogo Ivo <diogo.ivo@siemens.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
Date: Fri, 28 Jun 2024 15:45:14 -0600 [thread overview]
Message-ID: <20240628214514.GA258254-robh@kernel.org> (raw)
In-Reply-To: <1ac6bf9ef2d77dfc606a825d768bd4d23853052a.1719376928.git.jan.kiszka@siemens.com>
On Wed, Jun 26, 2024 at 06:42:07AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Expand bindings to cover both the MCU and the main usage of the AM654
> system controller.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .../soc/ti/ti,am654-system-controller.yaml | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> index e79803e586ca..a03e13cf2677 100644
> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
> @@ -34,6 +34,31 @@ patternProperties:
> type: object
> $ref: /schemas/phy/ti,phy-gmii-sel.yaml#
>
> + "^mux-controller$":
That's not a pattern, but fixed string. Move to 'properties'. I thought
the tools check this. Maybe it didn't apply to rc1 for the bot and you
didn't test either?
> + type: object
> + ref: /schemas/mux/reg-mux.yaml#
> + description:
> + This is the SERDES lane control mux.
> +
> + "^clock@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/soc/ti/ti,am654-serdes-ctrl.yaml#
> +
> + "^dss-oldi-io-ctrl@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/mfd/syscon.yaml#
> + properties:
> + compatible:
> + items:
> + - const: ti,am654-dss-oldi-io-ctrl
> + - const: syscon
> +
> + "^clock-controller@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
> + description:
> + Clock provider for TI EHRPWM nodes.
> +
> required:
> - compatible
> - reg
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-06-28 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 4:42 [PATCH v2 0/4] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-06-26 4:42 ` [PATCH v2 1/4] arm64: dts: ti: k3-j72xx-mcu-wakeup: add dedicated wakeup controller compatible Jan Kiszka
2024-06-26 4:42 ` [PATCH v2 2/4] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
2024-06-26 4:42 ` [PATCH v2 3/4] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
2024-06-28 21:45 ` Rob Herring [this message]
2024-06-26 4:42 ` [PATCH v2 4/4] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
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=20240628214514.GA258254-robh@kernel.org \
--to=robh@kernel.org \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=vigneshr@ti.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: link
Be 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.