From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yu-Chun Lin <eleanor.lin@realtek.com>,
afaerber@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, lee@kernel.org, james.tai@realtek.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-realtek-soc@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cy.huang@realtek.com, stanley_chang@realtek.com
Subject: Re: [PATCH 2/3] dt-bindings: mfd: Add Realtek ISO system controller
Date: Wed, 5 Nov 2025 11:58:21 +0100 [thread overview]
Message-ID: <88d90e44-88d9-4b5c-ba76-1e27dd28f78b@kernel.org> (raw)
In-Reply-To: <20251105104452.6336-3-eleanor.lin@realtek.com>
On 05/11/2025 11:44, Yu-Chun Lin wrote:
> Add DT binding schema for Realtek system controller.
>
> Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
> ---
> .../bindings/mfd/realtek,iso-system.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/realtek,iso-system.yaml
>
> diff --git a/Documentation/devicetree/bindings/mfd/realtek,iso-system.yaml b/Documentation/devicetree/bindings/mfd/realtek,iso-system.yaml
> new file mode 100644
> index 000000000000..6fbdedd3ee5b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/realtek,iso-system.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/realtek,iso-system.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Realtek ISO System Controller
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + The Realtek ISO System Controller is a register area that contains
> + miscellaneous system registers for the SoC and serves as a parent node
> + for other functions.
> +
> +maintainers:
> + - James Tai <james.tai@realtek.com>
> + - Yu-Chun Lin <eleanor.lin@realtek.com>
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - realtek,iso-system
No clue what is "iso system", neither commit msg, nor title nor
description explain me that. Please add first bindings for the iso soc
or if this is not soc, then use only soc-specific compatibles (see
writing bindings doc).
> + - const: syscon
> + - const: simple-mfd
> +
> + reg:
> + maxItems: 1
> +
> + ranges:
> + maxItems: 1
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 1
> +
> + reg-io-width:
> + const: 4
> +
> +patternProperties:
> + "^.*@[0-9a-f]+$":
> + type: object
> + description: Catch-all for other sub-devices in the ISO area.
Nope, sorry. Define exact children. All of them.
> +
> +required:
> + - compatible
> + - reg
> + - ranges
> + - '#address-cells'
> + - '#size-cells'
> + - reg-io-width
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + iso: syscon@7000 {
Drop label.
> + compatible = "realtek,iso-system", "syscon", "simple-mfd";
> + reg = <0x7000 0x1000>;
> + ranges = <0x0 0x7000 0x1000>;
> + reg-io-width = <4>;
> + #address-cells = <1>;
> + #size-cells = <1>;
No children here, so drop simple-mfd and all these fake child stuff.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-05 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 10:44 [PATCH 0/3] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2025-11-05 10:44 ` [PATCH 1/3] dt-bindings: arm: realtek: Add Kent Soc family compatibles Yu-Chun Lin
2025-11-05 10:44 ` [PATCH 2/3] dt-bindings: mfd: Add Realtek ISO system controller Yu-Chun Lin
2025-11-05 10:58 ` Krzysztof Kozlowski [this message]
2025-11-11 12:19 ` Eleanor Lin [林祐君]
2025-11-13 19:41 ` Krzysztof Kozlowski
2025-11-05 12:30 ` Rob Herring (Arm)
2025-11-11 12:29 ` Eleanor Lin [林祐君]
2025-11-05 10:44 ` [PATCH 3/3] arm64: dts: realtek: Add Kent SoC and EVB device trees Yu-Chun Lin
2025-11-05 11:04 ` Krzysztof Kozlowski
2025-11-11 12:25 ` Eleanor Lin [林祐君]
2025-11-13 19:40 ` Krzysztof Kozlowski
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=88d90e44-88d9-4b5c-ba76-1e27dd28f78b@kernel.org \
--to=krzk@kernel.org \
--cc=afaerber@suse.de \
--cc=conor+dt@kernel.org \
--cc=cy.huang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stanley_chang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox