[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c0abf651-ecbd-4ca7-b49a-a74197ed92b5@nvidia.com>
Date: Thu, 22 Jan 2026 09:13:52 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Prathamesh Shete <pshete@...dia.com>
Cc: linusw@...nel.org, brgl@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, thierry.reding@...il.com, robh@...nel.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: gpio: Add Tegra264 support
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
Powered by blists - more mailing lists