From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] pinctrl: renesas: Updates for v5.19
Date: Fri, 22 Apr 2022 16:55:12 +0200 [thread overview]
Message-ID: <cover.1650638951.git.geert+renesas@glider.be> (raw)
Hi Linus,
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-pinctrl-for-v5.19-tag1
for you to fetch changes up to f7bc5f52d2354b41d5a111942be7ee01e5560c78:
pinctrl: renesas: rzg2l: Restore pin config order (2022-04-20 11:53:47 +0200)
----------------------------------------------------------------
pinctrl: renesas: Updates for v5.19
- Add support for the new RZ/G2UL SoC,
- Add drive-strength support for R-Car E3,
- Add RPC/QSPI pin groups on R-Car E3 and E3,
- Miscellaneous fixes and improvements.
Thanks for pulling!
----------------------------------------------------------------
Biju Das (2):
dt-bindings: pinctrl: renesas: Document RZ/G2UL pinctrl
pinctrl: renesas: rzg2l: Add RZ/G2UL support
Geert Uytterhoeven (6):
pinctrl: renesas: Simplify multiplication/shift logic
pinctrl: renesas: checker: Rework drive and bias pin iteration
pinctrl: renesas: r8a77990: Add RPC pins, groups, and functions
pinctrl: renesas: r8a77995: Add QSPI and RPC pins, groups, and functions
pinctrl: renesas: Remove unneeded #include <linux/init.h>
pinctrl: renesas: rzg2l: Restore pin config order
Lad Prabhakar (1):
pinctrl: renesas: Select PINCTRL_RZG2L if ARCH_RZG2L is enabled
Wolfram Sang (2):
pinctrl: renesas: Allow up to 10 fields for drive_regs
pinctrl: renesas: r8a77990: Add drive-strength
.../bindings/pinctrl/renesas,rzg2l-pinctrl.yaml | 5 +-
drivers/pinctrl/renesas/Kconfig | 7 +-
drivers/pinctrl/renesas/core.c | 67 +++----
drivers/pinctrl/renesas/gpio.c | 1 -
drivers/pinctrl/renesas/pfc-emev2.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77990.c | 120 ++++++++++---
drivers/pinctrl/renesas/pfc-r8a77995.c | 98 ++++++++++
drivers/pinctrl/renesas/pfc-sh7722.c | 1 -
drivers/pinctrl/renesas/pfc-sh7723.c | 1 -
drivers/pinctrl/renesas/pfc-sh7724.c | 1 -
drivers/pinctrl/renesas/pfc-sh7734.c | 1 -
drivers/pinctrl/renesas/pfc-sh7757.c | 1 -
drivers/pinctrl/renesas/pfc-sh7785.c | 1 -
drivers/pinctrl/renesas/pfc-sh7786.c | 1 -
drivers/pinctrl/renesas/pfc-shx3.c | 1 -
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 200 +++++++++++++--------
drivers/pinctrl/renesas/pinctrl.c | 1 -
drivers/pinctrl/renesas/sh_pfc.h | 7 +-
18 files changed, 362 insertions(+), 153 deletions(-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2022-04-22 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 14:55 Geert Uytterhoeven [this message]
2022-04-22 21:05 ` [GIT PULL] pinctrl: renesas: Updates for v5.19 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=cover.1650638951.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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 NNTP newsgroup(s).