From: Jonas Karlman <jonas@kwiboo.se>
To: Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Tom Rini <trini@konsulko.com>
Cc: Johan Jonker <jbx6244@gmail.com>,
u-boot@lists.denx.de, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH 0/4] rockchip: Add gpio request() ops and drop PCIe reset-gpios workaround
Date: Sat, 11 May 2024 11:28:11 +0000 [thread overview]
Message-ID: <20240511112821.1156519-1-jonas@kwiboo.se> (raw)
This series add gpio request() and pinctrl gpio_request_enable() ops so
that a gpio requested pin automatically use gpio pinmux and U-Boot
behaves more similar to Linux kernel.
With the gpio and pinctrl ops implemented this series also remove a PCIe
reset-gpios related device lock-up workaround from board u-boot.dtsi.
PX30, RK3066, RK3188, RK356x and RK3588 are the only SoCs that currently
define gpio-ranges props and is affected by this series.
A follow up series adding support for the pinmux status cmd will also
add gpio-ranges props for remaining RK SoCs.
Jonas Karlman (4):
pinctrl: rockchip: Add gpio_request_enable() ops
gpio: rockchip: Add request() ops
rockchip: rk3568-rock-3a: Drop PCIe reset-gpios workaround
rockchip: rk3568-radxa-e25: Drop PCIe reset-gpios workaround
arch/arm/dts/rk3568-radxa-e25-u-boot.dtsi | 12 -------
arch/arm/dts/rk3568-rock-3a-u-boot.dtsi | 12 -------
drivers/gpio/rk_gpio.c | 10 ++++++
.../pinctrl/rockchip/pinctrl-rockchip-core.c | 31 +++++++++++++++++++
4 files changed, 41 insertions(+), 24 deletions(-)
--
2.43.2
next reply other threads:[~2024-05-11 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 11:28 Jonas Karlman [this message]
2024-05-11 11:28 ` [PATCH 1/4] pinctrl: rockchip: Add gpio_request_enable() ops Jonas Karlman
2024-05-11 11:28 ` [PATCH 2/4] gpio: rockchip: Add request() ops Jonas Karlman
2024-05-11 11:28 ` [PATCH 3/4] rockchip: rk3568-rock-3a: Drop PCIe reset-gpios workaround Jonas Karlman
2024-05-11 11:28 ` [PATCH 4/4] rockchip: rk3568-radxa-e25: " Jonas Karlman
2024-05-11 17:44 ` [PATCH 0/4] rockchip: Add gpio request() ops and drop " Alex Bee
2024-05-11 18:47 ` Jonas Karlman
2024-05-11 19:57 ` Mark Kettenis
2024-05-11 20:55 ` Jonas Karlman
2024-05-12 20:41 ` Mark Kettenis
2024-05-12 22:23 ` Jonas Karlman
2024-05-21 21:30 ` Mark Kettenis
2024-05-12 19:49 ` Alex Bee
2024-05-12 20:47 ` Mark Kettenis
2024-05-12 21:37 ` Jonas Karlman
2024-05-12 22:34 ` Alex Bee
2024-05-12 23:22 ` Jonas Karlman
2024-05-22 14:18 ` Alex Bee
2024-05-22 16:20 ` Jonas Karlman
2024-05-22 19:46 ` Alex Bee
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=20240511112821.1156519-1-jonas@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).