From: "Yu-Chun Lin [林祐君]" <eleanor.lin@realtek.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "tglx@kernel.org" <tglx@kernel.org>,
"radu@rendec.net" <radu@rendec.net>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"lee@kernel.org" <lee@kernel.org>,
"afaerber@suse.com" <afaerber@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mfd@lists.linux.dev" <mfd@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>,
"James Tai [戴志峰]" <james.tai@realtek.com>,
"CY_Huang[黃鉦晏]" <cy.huang@realtek.com>,
"Stanley Chang[昌育德]" <stanley_chang@realtek.com>
Subject: RE: [PATCH v5 3/8] dt-bindings: mfd: realtek,rtd1xxx: Add interrupt controller child node
Date: Mon, 19 Oct 2026 11:19:17 +0000 [thread overview]
Message-ID: <b12ff328ebca405f96a9b25decdb7c81@realtek.com> (raw)
In-Reply-To: <20261019-prophetic-moth-of-youth-40dbd6@quoll>
Hi Krzysztof,
> On Mon, Oct 19, 2026 at 12:06:48AM +0800, Yu-Chun Lin wrote:
> > Allow an interrupt controller as a child node by referencing the
> > rtd1319-intc-iso schema, update additionalProperties to
> > unevaluatedProperties, and append a usage example.
>
> I do not see that "update".
>
Sorry about this. I updated the diff but missed updating the commit
message. Will fix.
> >
> > Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
> > ---
> > .../bindings/mfd/realtek,rtd1xxx.yaml | 28
> +++++++++++++++++++
> > 1 file changed, 28 insertions(+)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/mfd/realtek,rtd1xxx.yaml
> > b/Documentation/devicetree/bindings/mfd/realtek,rtd1xxx.yaml
> > index 717e29c37b36..b21e14df2879 100644
> > --- a/Documentation/devicetree/bindings/mfd/realtek,rtd1xxx.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/realtek,rtd1xxx.yaml
> > @@ -65,6 +65,10 @@ properties:
> > const: 1
> >
> > patternProperties:
> > + "^interrupt-controller":
> > + $ref: /schemas/interrupt-controller/realtek,rtd1319-intc-iso.yaml
> > + unevaluatedProperties: false
> > +
> > '@[0-9a-f]+$':
> > type: object
>
> What is this for then? Should it be removed?
>
The original syscon compatible has other child nodes that do have 'reg'
properties and unit addresses, so this pattern is still needed for them.
> >
> > @@ -76,3 +80,27 @@ required:
> > - reg
> >
> > additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > +
> > + syscon@7000 {
> > + compatible = "realtek,rtd1625-iso", "syscon", "simple-mfd";
> > + reg = <0x7000 0x1000>;
> > + ranges = <0x0 0x7000 0x1000>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
>
> Why do you have cells it your child has no addressing?
>
> > +
> > + interrupt-controller {
>
> So the binding requires children with unit address, yes?
>
The interrupt-controller does not need a unit address because it accesses
the registers via the parent's regmap.
Will update the example to remove the unnecessary properties from the
parent as follows:
syscon@7000 {
compatible = "realtek,rtd1625-iso", "syscon", "simple-mfd";
reg = <0x7000 0x1000>;
interrupt-controller {
compatible = "realtek,rtd1625-intc-iso";
interrupt-controller;
interrupt-parent = <&gic>;
interrupts = <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 57 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>;
#address-cells = <0>;
#interrupt-cells = <1>;
};
};
Best regards,
Yu-Chun
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-10-19 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 16:06 [PATCH v5 0/8] Initial support for the Realtek interrupt controller Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 1/8] dt-bindings: interrupt-controller: Add support for Realtek DHC SoCs Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 2/8] dt-bindings: mfd: realtek,rtd1xxx: Add new SoCs Yu-Chun Lin
2026-10-19 9:11 ` Krzysztof Kozlowski
2026-10-18 16:06 ` [PATCH v5 3/8] dt-bindings: mfd: realtek,rtd1xxx: Add interrupt controller child node Yu-Chun Lin
2026-10-19 9:13 ` Krzysztof Kozlowski
2026-10-19 11:19 ` Yu-Chun Lin [林祐君] [this message]
2026-10-18 16:06 ` [PATCH v5 4/8] irqchip/realtek-intc-common: Add basic support for Realtek DHC SoCs Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 5/8] irqchip/realtek-rtd1319: Add driver for Realtek DHC RTD1319 SoC Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 6/8] irqchip/realtek-rtd1319d: Add driver for Realtek RTD1319D and RTD1325 SoCs Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 7/8] irqchip/realtek-rtd1619b: Add driver for Realtek DHC RTD1619B SoC Yu-Chun Lin
2026-10-18 16:06 ` [PATCH v5 8/8] irqchip/realtek-rtd1625: Add driver for Realtek DHC rtd1625 SoC Yu-Chun 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=b12ff328ebca405f96a9b25decdb7c81@realtek.com \
--to=eleanor.lin@realtek.com \
--cc=afaerber@suse.com \
--cc=conor+dt@kernel.org \
--cc=cy.huang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=mfd@lists.linux.dev \
--cc=radu@rendec.net \
--cc=robh@kernel.org \
--cc=stanley_chang@realtek.com \
--cc=tglx@kernel.org \
/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
all inboxes | Powered by JetHome®