[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaBTwhmzs5guoBEqkvHrrowD8+zmSsHmFroxr7a5CCc9g@mail.gmail.com>
Date: Fri, 3 May 2024 10:29:11 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Doug Berger <opendmb@...il.com>, Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Phil Elwell <phil@...pberrypi.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
Florian Fainelli <florian.fainelli@...adcom.com>, bcm-kernel-feedback-list@...adcom.com,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] gpio: brcmstb: add support for gpio-ranges
On Fri, Apr 26, 2024 at 9:33 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> [2/3] gpio: of: support gpio-ranges for multiple gpiochip devices
> commit: e818cd3c8a345c046edff00b5ad0be4d39f7e4d4
I'm not sure this is a good idea. To me it looks like the commit violates
the device tree bindings, which says offsets are on the local GPIO chip
and turn them into offsets in the Linux GPIO numberspace.
Yours,
Linus Walleij
Powered by blists - more mailing lists