linux-kernel - Re: [PATCH 1/3] dt-bindings: gpio: Add Tegra264 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <931207bd-a24e-46a5-b0e5-eb5307c5c8bb@nvidia.com>
Date: Mon, 19 Jan 2026 22:12:59 +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 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?

Jon

-- 
nvpublic