From: Keerthy <j-keerthy@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, <t-kristo@ti.com>, <nm@ti.com>,
<robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] arm64: dts: ti: am6-wakeup: Add gpio node
Date: Wed, 5 Jun 2019 12:01:35 +0530 [thread overview]
Message-ID: <bac5737a-3924-b59f-1d90-a2a9b3a390f1@ti.com> (raw)
In-Reply-To: <e6ec3894-4e3d-e721-c1bc-791263b2d309@ti.com>
On 05/06/19 11:46 AM, Lokesh Vutla wrote:
>
>
> On 05/06/19 11:38 AM, Keerthy wrote:
>> Add gpio0 node under wakeup domain. This has 56 gpios
>> and all are capable of generating banked interrupts.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
>> index f1ca171abdf8..8c6c99e7c6ed 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
>> @@ -74,4 +74,19 @@
>> ti,sci-dst-id = <56>;
>> ti,sci-rm-range-girq = <0x4>;
>> };
>> +
>> + wkup_gpio0: wkup_gpio0@42110000 {
>> + compatible = "ti,k2g-gpio", "ti,keystone-gpio";
>
> This is not k2g. Can you either create a am6 specific compatible or just use
> ti,keystone-gpio.
It seems practice is now to have separate compatible. I will add am6
specific compatible.
>
> Thanks and regards,
> Lokesh
>
>> + reg = <0x42110000 0x100>;
>> + gpio-controller;
>> + #gpio-cells = <2>;
>> + interrupt-parent = <&intr_wkup_gpio>;
>> + interrupts = <59 128>, <59 129>, <59 130>, <59 131>;
>> + interrupt-controller;
>> + #interrupt-cells = <2>;
>> + ti,ngpio = <56>;
>> + ti,davinci-gpio-unbanked = <0>;
>> + clocks = <&k3_clks 59 0>;
>> + clock-names = "gpio";
>> + };
>> };
>>
next prev parent reply other threads:[~2019-06-05 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 6:08 [RFC PATCH 0/3] arm64: dts: ti: am6: Add gpio nodes Keerthy
2019-06-05 6:08 ` [RFC PATCH 1/3] arm64: dts: ti: am6-wakeup: Add gpio node Keerthy
2019-06-05 6:16 ` Lokesh Vutla
2019-06-05 6:31 ` Keerthy [this message]
2019-06-05 6:08 ` [RFC PATCH 2/3] arm64: dts: ti: am6-main: Add gpio nodes Keerthy
2019-06-05 6:08 ` [RFC PATCH 3/3] arm64: dts: ti: am654-base-board: Add gpio_keys node Keerthy
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=bac5737a-3924-b59f-1d90-a2a9b3a390f1@ti.com \
--to=j-keerthy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@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
all inboxes | Powered by JetHome®