From: Detlev Casanova <detlev.casanova@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Detlev Casanova <detlev.casanova@collabora.com>,
Linus Walleij <linus.walleij@linaro.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Shresth Prasad <shresthprasad7@gmail.com>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
kernel@collabora.com, Sascha Hauer <s.hauer@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Add pinctrl support for rk3576
Date: Thu, 22 Aug 2024 15:53:35 -0400 [thread overview]
Message-ID: <20240822195706.920567-1-detlev.casanova@collabora.com> (raw)
Add support for the pinctrl core on the rk3576 SoC.
The patch from downstream has been rebased.
The grf driver is added support for the rk3576 default values:
- enable i3c weakpull SW control
- disable jtag on sdmmc IO lines
Changes since v3:
- Set GRF bits through the GRF driver
- Drop the rockchip,sys-grf phandle
Changes since v2:
- Document rockchip,sys-grf field as only needed for rk3576
Changes since v1:
- Reorder commits
- Describe sys-grf use
- Update imperative commit message
Detlev.
Detlev Casanova (3):
dt-bindings: soc: rockchip: Add rk3576 syscon compatibles
grf: rk3576: Add default GRF values
dt-bindings: pinctrl: Add rk3576 pinctrl support
Steven Liu (1):
pinctrl: rockchip: Add rk3576 pinctrl support
.../bindings/pinctrl/rockchip,pinctrl.yaml | 1 +
.../devicetree/bindings/soc/rockchip/grf.yaml | 16 ++
drivers/pinctrl/pinctrl-rockchip.c | 207 ++++++++++++++++++
drivers/pinctrl/pinctrl-rockchip.h | 1 +
drivers/soc/rockchip/grf.c | 30 ++-
5 files changed, 254 insertions(+), 1 deletion(-)
--
2.46.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2024-08-22 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 19:53 Detlev Casanova [this message]
2024-08-22 19:53 ` [PATCH v4 1/4] dt-bindings: soc: rockchip: Add rk3576 syscon compatibles Detlev Casanova
2024-08-23 7:34 ` Krzysztof Kozlowski
2024-08-22 19:53 ` [PATCH v4 2/4] grf: rk3576: Add default GRF values Detlev Casanova
2024-08-23 5:20 ` Dragan Simic
2024-08-22 19:53 ` [PATCH v4 3/4] dt-bindings: pinctrl: Add rk3576 pinctrl support Detlev Casanova
2024-08-23 7:35 ` Krzysztof Kozlowski
2024-08-23 9:49 ` Heiko Stübner
2024-08-22 19:53 ` [PATCH v4 4/4] pinctrl: rockchip: " Detlev Casanova
2024-08-23 5:21 ` Dragan Simic
2024-08-23 9:51 ` Heiko Stübner
2024-08-23 12:34 ` (subset) [PATCH v4 0/4] Add pinctrl support for rk3576 Heiko Stuebner
2024-08-23 15:47 ` 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=20240822195706.920567-1-detlev.casanova@collabora.com \
--to=detlev.casanova@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@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-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--cc=shresthprasad7@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox