Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Brattlof <bb@ti.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	"Andrew Davis" <afd@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Tony Lindgren" <tony@atomide.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v7 2/3] arm64: dts: ti: k3-am62l: add initial infrastructure
Date: Wed, 5 Nov 2025 08:22:42 -0600	[thread overview]
Message-ID: <20251105142242.gly4brezn4lnlfkv@bryanbrattlof.com> (raw)
In-Reply-To: <aQha9-oNEQd2Ds7Z@pengutronix.de>

On November  3, 2025 thus sayeth Sascha Hauer:
> On Fri, Oct 31, 2025 at 09:08:05AM -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";
> 
> Virtually all boards use GPIOs and a GPIO controller doesn't have any
> external dependencies, so could you enable them by default like done on
> many other SoCs?
> 

Yeah that is fair. I'll enable this.

> > +
> > +	target-module@2b300050 {
> > +		compatible = "ti,sysc-omap2", "ti,sysc";
> > +		reg = <0x00 0x2b300050 0x00 0x4>,
> > +		      <0x00 0x2b300054 0x00 0x4>,
> > +		      <0x00 0x2b300058 0x00 0x4>;
> > +		reg-names = "rev", "sysc", "syss";
> > +		ranges = <0x00 0x00 0x2b300000 0x100000>;
> > +		#address-cells = <1>;
> > +		#size-cells = <1>;
> > +		power-domains = <&scmi_pds 83>;
> > +		clocks = <&scmi_clk 324>;
> > +		clock-names = "fck";
> > +		ti,sysc-mask = <(SYSC_OMAP2_ENAWAKEUP |
> > +				 SYSC_OMAP2_SOFTRESET |
> > +				 SYSC_OMAP2_AUTOIDLE)>;
> > +		ti,sysc-sidle = <SYSC_IDLE_FORCE>,
> > +				<SYSC_IDLE_NO>,
> > +				<SYSC_IDLE_SMART>,
> > +				<SYSC_IDLE_SMART_WKUP>;
> > +		ti,syss-mask = <1>;
> > +		ti,no-reset-on-init;
> > +		status = "disabled";
> 
> This node is present on many other TI SoCs, all I have looked at have
> this node enabled by default. I think it makes sense to have this node
> enabled given that it has child nodes like this UART:
> 

I agree as well. 


Thanks again Sascha

~Bryan


  reply	other threads:[~2025-11-05 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 14:08 [PATCH v7 0/3] arm64: dts: ti: introduce basic support for the AM62L Bryan Brattlof
2025-10-31 14:08 ` [PATCH v7 1/3] dt-bindings: arm: ti: Add binding for AM62L SoCs Bryan Brattlof
2025-10-31 14:08 ` [PATCH v7 2/3] arm64: dts: ti: k3-am62l: add initial infrastructure Bryan Brattlof
2025-10-31 18:13   ` Dhruva Gole
2025-11-03  7:34   ` Sascha Hauer
2025-11-05 14:22     ` Bryan Brattlof [this message]
2025-10-31 14:08 ` [PATCH v7 3/3] arm64: dts: ti: k3-am62l: add initial reference board file Bryan Brattlof
2025-10-31 18:15   ` Dhruva Gole
2025-11-03  7:39   ` Sascha Hauer
2025-11-05 14:18     ` Bryan Brattlof

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=20251105142242.gly4brezn4lnlfkv@bryanbrattlof.com \
    --to=bb@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox