mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Prathamesh Shete <pshete@nvidia.com>
Cc: linusw@kernel.org, brgl@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, thierry.reding@gmail.com, robh@kernel.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: gpio: Add Tegra264 support
Date: Thu, 22 Jan 2026 09:13:52 +0000	[thread overview]
Message-ID: <c0abf651-ecbd-4ca7-b49a-a74197ed92b5@nvidia.com> (raw)
In-Reply-To: <931207bd-a24e-46a5-b0e5-eb5307c5c8bb@nvidia.com>



On 19/01/2026 22:12, Jon Hunter wrote:
> 
> On 15/01/2026 13:29, Krzysztof Kozlowski wrote:
>> On Wed, Jan 14, 2026 at 10:38:44AM +0000, Prathamesh Shete wrote:
>>> Extend the existing Tegra186 GPIO controller device tree bindings with
>>> support for the GPIO controller found on Tegra264. The number of pins
>>> is slightly different, but the programming model remains the same.
>>>
>>> Add a new header, include/dt-bindings/gpio/tegra264-gpio.h,
>>> that defines port IDs as well as the TEGRA264_MAIN_GPIO() helper,
>>> both of which are used in conjunction to create a unique specifier
>>> for each pin.
>>>
>>> Document nvidia,pmc property referencing the PMC node providing the
>>> parent interrupt domain. GPIO driver uses this to select the correct
>>
>> Why do you need to reference parent interrupt not via interrupts but
>> custom phandle?
> 
> Good point. So for this specific case this is a wake-up parent and so 
> would using the 'wakeup-parent' property be OK for this?

Prathamesh, can you update this to use 'wakeup-parent' for this?

Thanks
Jon

-- 
nvpublic


      reply	other threads:[~2026-01-22  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 10:38 Prathamesh Shete
2026-01-14 10:38 ` [PATCH 2/3] gpio: tegra186: Add support for Tegra264 Prathamesh Shete
2026-01-14 10:38 ` [PATCH 3/3] arm64: tegra: Add Tegra264 GPIO controllers Prathamesh Shete
2026-01-15 13:29 ` [PATCH 1/3] dt-bindings: gpio: Add Tegra264 support Krzysztof Kozlowski
2026-01-19 22:12   ` Jon Hunter
2026-01-22  9:13     ` Jon Hunter [this message]

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=c0abf651-ecbd-4ca7-b49a-a74197ed92b5@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pshete@nvidia.com \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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®