devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Aswath Govindraju <a-govindraju@ti.com>,
	Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-mcu: Enable MCU GPIO module
Date: Wed, 27 Apr 2022 20:54:07 +0530	[thread overview]
Message-ID: <d802f305-90d6-decf-c7ad-547d3c8a80da@ti.com> (raw)
In-Reply-To: <96894353-2b4e-52a7-bd48-c65eb674d6f5@ti.com>



On 27/04/22 4:36 pm, Aswath Govindraju wrote:
> On 21/04/22 11:49, Vignesh Raghavendra wrote:
>> AM62 has x1 GPIO module and associated interrupt router in MCU Domain.
>> Add DT nodes for the same.
>>
>> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
>> ---
>>  arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 28 +++++++++++++++++++++++++
>>  1 file changed, 28 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
>> index d103824c963f..45343381ad0b 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
>> @@ -53,4 +53,32 @@ mcu_spi1: spi@4b10000 {
>>  		power-domains = <&k3_pds 148 TI_SCI_PD_EXCLUSIVE>;
>>  		clocks = <&k3_clks 148 0>;
>>  	};
>> +
>> +	mcu_gpio_intr: interrupt-controller@4210000 {
>> +		compatible = "ti,sci-intr";
>> +		reg = <0x00 0x04210000 0x00 0x200>;
>> +		ti,intr-trigger-type = <1>;
>> +		interrupt-controller;
>> +		interrupt-parent = <&gic500>;
>> +		#interrupt-cells = <1>;
>> +		ti,sci = <&dmsc>;
>> +		ti,sci-dev-id = <5>;
>> +		ti,interrupt-ranges = <0 104 4>;
>> +	};
>> +
>> +	mcu_gpio0: gpio@4201000 {
>> +		compatible = "ti,am64-gpio", "ti,keystone-gpio";
>> +		reg = <0x0 0x4201000 0x0 0x100>;
> 
> nitpick: reg = <0x00 0x04201000 0x00 0x100>;

Ah, yes.. Will fix locally before merging.

> 
>> +		gpio-controller;
>> +		#gpio-cells = <2>;
>> +		interrupt-parent = <&mcu_gpio_intr>;
>> +		interrupts = <30>, <31>;
>> +		interrupt-controller;
>> +		#interrupt-cells = <2>;
>> +		ti,ngpio = <24>;
>> +		ti,davinci-gpio-unbanked = <0>;
>> +		power-domains = <&k3_pds 79 TI_SCI_PD_EXCLUSIVE>;
>> +		clocks = <&k3_clks 79 0>;
>> +		clock-names = "gpio";
>> +	};
>>  };
> 
> 
> Aside from the above minor change,
> 
> Reviewed-by: Aswath Govindraju <a-govindraju@ti.com>
> 

Thanks!

Regards
Vignesh

  reply	other threads:[~2022-04-27 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  6:19 [PATCH] arm64: dts: ti: k3-am62-mcu: Enable MCU GPIO module Vignesh Raghavendra
2022-04-27 11:06 ` Aswath Govindraju
2022-04-27 15:24   ` Vignesh Raghavendra [this message]
2022-04-28  5:17 ` Vignesh Raghavendra

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=d802f305-90d6-decf-c7ad-547d3c8a80da@ti.com \
    --to=vigneshr@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.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=robh+dt@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;
as well as URLs for NNTP newsgroup(s).