From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/5] RK3568 pinctrl
Date: Tue, 8 Jun 2021 16:05:40 +0200 [thread overview]
Message-ID: <20210608140545.30696-1-s.hauer@pengutronix.de> (raw)
Another step in getting Rockchip rk3568 support upstream: This series
adds pinctrl support for that SoC.
Unfortunately I don't have access to a board that was previously
supported by the driver, so I can't test if it still works. The rk3568
seems to work ok though, the register settings I have checked look sane.
Sascha
Sascha Hauer (5):
pinctrl: Rockchip: rename mux_offset to grf_mux_offset
pinctrl: Rockchip: print resource_size_t with %pa
pinctrl: Rockchip: Update from Linux
pinctrl: Rockchip: implement drive strength setting
pinctrl: Rockchip: Add RK3568 support
drivers/pinctrl/pinctrl-rockchip.c | 777 ++++++++++++++++++++++++++++-
1 file changed, 754 insertions(+), 23 deletions(-)
--
2.29.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2021-06-08 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:05 Sascha Hauer [this message]
2021-06-08 14:05 ` [PATCH 1/5] pinctrl: Rockchip: rename mux_offset to grf_mux_offset Sascha Hauer
2021-06-08 14:05 ` [PATCH 2/5] pinctrl: Rockchip: print resource_size_t with %pa Sascha Hauer
2021-06-08 14:05 ` [PATCH 3/5] pinctrl: Rockchip: Update from Linux Sascha Hauer
2021-06-08 14:05 ` [PATCH 4/5] pinctrl: Rockchip: implement drive strength setting Sascha Hauer
2021-06-09 8:13 ` Ahmad Fatoum
2021-06-08 14:05 ` [PATCH 5/5] pinctrl: Rockchip: Add RK3568 support Sascha Hauer
2021-06-09 8:01 ` Ahmad Fatoum
2021-06-09 9:41 ` Sascha Hauer
2021-06-09 8:11 ` Ahmad Fatoum
2021-06-09 9:45 ` Sascha Hauer
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=20210608140545.30696-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--subject='Re: [PATCH 0/5] RK3568 pinctrl' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox