[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda1OKXnma11wKTrBsO_AAXrifVK8RDCKmufdHXBMmtMbQ@mail.gmail.com>
Date: Wed, 21 May 2025 00:14:06 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Stefan Wahren <wahrenst@....net>
Cc: Haibo Chen <haibo.chen@....com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>,
Stefan Agner <stefan@...er.ch>, Bartosz Golaszewski <brgl@...ev.pl>, devicetree@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org, peng.fan@....com,
conor@...nel.org, Frank Li <Frank.Li@....com>
Subject: Re: [PATCH v3 2/3] ARM: dts: add ngpios for vf610 compatible gpio controllers
On Tue, May 20, 2025 at 12:54 PM Stefan Wahren <wahrenst@....net> wrote:
> sorry for asking this dumb question: why do we need the redundant ngpio
> property in case there is already gpio-ranges defined? AFAIU the last
> cell already contains the necessary information. Or do I missed something?
Not all GPIOs on a gpio controller have to be present in
a range.
The ranges can be multiple and have holes in them.
The ranges are also optional.
The fact that this DTS file, for this SoC and on this controller
happens to have a range mapped right over all of the pins
is merely a coinicidence and not a general rule of any kind,
it just apophenia playing games on us.
Yours,
Linus Walleij
Powered by blists - more mailing lists