[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220409095129.45786-1-stefan.wahren@i2se.com>
Date: Sat, 9 Apr 2022 11:51:27 +0200
From: Stefan Wahren <stefan.wahren@...e.com>
To: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>
Cc: 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,
Stefan Wahren <stefan.wahren@...e.com>
Subject: [PATCH 0/2] gpiolib: of: Introduce hook for missing gpio-ranges
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
Stefan Wahren (2):
gpiolib: of: Introduce hook for missing gpio-ranges
pinctrl: bcm2835: implement hook for missing gpio-ranges
drivers/gpio/gpiolib-of.c | 5 +++++
drivers/pinctrl/bcm/pinctrl-bcm2835.c | 18 ++++++++++++++++++
include/linux/gpio/driver.h | 12 ++++++++++++
3 files changed, 35 insertions(+)
--
2.25.1
Powered by blists - more mailing lists