From: Sascha Hauer <s.hauer@pengutronix.de>
To: Bryan Brattlof <bb@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: ti: k3-am62l: add initial infrastructure
Date: Tue, 27 May 2025 14:06:10 +0200 [thread overview]
Message-ID: <aDWqshj4G91yv6xd@pengutronix.de> (raw)
In-Reply-To: <20250507-am62lx-v5-2-4b57ea878e62@ti.com>
On Wed, May 07, 2025 at 10:09:20PM -0500, Bryan Brattlof wrote:
> + gpio0: gpio@600000 {
> + compatible = "ti,am64-gpio", "ti,keystone-gpio";
> + reg = <0x00 0x00600000 0x00 0x100>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + interrupt-parent = <&gic500>;
> + interrupts = <GIC_SPI 260 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 261 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 262 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 263 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 264 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 265 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 266 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 267 IRQ_TYPE_EDGE_RISING>;
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + power-domains = <&scmi_pds 34>;
> + clocks = <&scmi_clk 140>;
> + clock-names = "gpio";
> + ti,ngpio = <126>;
> + ti,davinci-gpio-unbanked = <0>;
> + status = "disabled";
> + };
The gpio ports are always available and do not have any dependencies.
Can we drop the status = "disabled"; here and for the other gpio nodes?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-05-27 12:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 3:09 [PATCH v5 0/3] arm64: dts: ti: introduce basic support for the AM62L Bryan Brattlof
2025-05-08 3:09 ` [PATCH v5 1/3] dt-bindings: arm: ti: Add binding for AM62L SoCs Bryan Brattlof
2025-05-08 4:08 ` Rob Herring (Arm)
2025-05-08 6:51 ` Krzysztof Kozlowski
2025-05-08 13:14 ` Bryan Brattlof
2025-05-08 15:46 ` Krzysztof Kozlowski
2025-05-08 3:09 ` [PATCH v5 2/3] arm64: dts: ti: k3-am62l: add initial infrastructure Bryan Brattlof
2025-05-08 6:52 ` Krzysztof Kozlowski
2025-05-08 6:56 ` Krzysztof Kozlowski
2025-05-08 12:33 ` Nishanth Menon
2025-05-08 13:12 ` Bryan Brattlof
2025-05-16 10:23 ` Sascha Hauer
2025-05-16 12:23 ` Bryan Brattlof
2025-05-27 12:06 ` Sascha Hauer [this message]
2025-06-03 13:38 ` Sascha Hauer
2025-06-03 13:47 ` Bryan Brattlof
2025-05-08 3:09 ` [PATCH v5 3/3] arm64: dts: ti: k3-am62l: add initial reference board file Bryan Brattlof
2025-05-09 14:16 ` [PATCH v5 0/3] arm64: dts: ti: introduce basic support for the AM62L Rob Herring (Arm)
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=aDWqshj4G91yv6xd@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).