From: Stefan Wahren <stefan.wahren@i2se.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Phil Elwell <phil@raspberrypi.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH 0/2] gpiolib: of: Introduce hook for missing gpio-ranges
Date: Sat, 9 Apr 2022 11:51:27 +0200 [thread overview]
Message-ID: <20220409095129.45786-1-stefan.wahren@i2se.com> (raw)
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Phil Elwell <phil@raspberrypi.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH 0/2] gpiolib: of: Introduce hook for missing gpio-ranges
Date: Sat, 9 Apr 2022 11:51:27 +0200 [thread overview]
Message-ID: <20220409095129.45786-1-stefan.wahren@i2se.com> (raw)
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
next reply other threads:[~2022-04-09 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 9:51 Stefan Wahren [this message]
2022-04-09 9:51 ` [PATCH 0/2] gpiolib: of: Introduce hook for missing gpio-ranges Stefan Wahren
2022-04-09 9:51 ` [PATCH 1/2] " Stefan Wahren
2022-04-09 9:51 ` Stefan Wahren
2022-04-09 9:51 ` [PATCH 2/2] pinctrl: bcm2835: implement " Stefan Wahren
2022-04-09 9:51 ` Stefan Wahren
2022-04-19 21:18 ` [PATCH 0/2] gpiolib: of: Introduce " Linus Walleij
2022-04-19 21:18 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220409095129.45786-1-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brgl@bgdev.pl \
--cc=f.fainelli@gmail.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.