[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdb4dPkFrKsfQmvyLO0RHCJsZYwULncDqbX5zkJqvmbPTw@mail.gmail.com>
Date: Tue, 19 Apr 2022 23:18:48 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Stefan Wahren <stefan.wahren@...e.com>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
Phil Elwell <phil@...pberrypi.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/2] gpiolib: of: Introduce hook for missing gpio-ranges
On Sat, Apr 9, 2022 at 11:52 AM Stefan Wahren <stefan.wahren@...e.com> wrote:
> This patch series tries to provide backward compatibility for DTB which
> lacks the gpio-ranges property.
>
> The commit ("pinctrl: msm: fix gpio-hog related boot issues") by Christian
> Lamparter already contains a fallback in case the gpio-ranges property
> is missing. But this approach doesn't work on BCM2835 with a gpio-hog
> defined for the SoC GPIOs.
>
> Based Christian's on explanation i conclude that the fallback must happen
> during the gpiochip_add() call and not afterwards. So the approach is to
> call an optional hook, which can be implemented in the platform driver.
>
> This series has been tested on Raspberry Pi 3 B Plus.
>
> Changes since RFC:
> - just add all collected Fixes, Reviewed-by, Tested-by and Acked-by
Patches applied!
Sorry for being a bit slow on this :/
Yours,
Linus Walleij
Powered by blists - more mailing lists