From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] pinctrl: renesas: r8a7799[05]: Add RPC pins, groups, and functions
Date: Tue, 29 Mar 2022 11:48:49 +0200 [thread overview]
Message-ID: <cover.1648547080.git.geert+renesas@glider.be> (raw)
Hi Linus,
This patch series adds support for the various pins, groups, and
functions used by the SPI Multi I/O Bus Controller (RPC-IF) on the R-Car
E3 and D3, and RZ/G2E SoCs.
It has been tested using HyperFlash on the Ebisu-4D and Draak
development boards.
I intend to queue this in renesas-pinctrl for v5.19.
Thanks for your comments!
Geert Uytterhoeven (2):
pinctrl: renesas: r8a77990: Add RPC pins, groups, and functions
pinctrl: renesas: r8a77995: Add QSPI and RPC pins, groups, and
functions
drivers/pinctrl/renesas/pfc-r8a77990.c | 81 +++++++++++++++------
drivers/pinctrl/renesas/pfc-r8a77995.c | 98 ++++++++++++++++++++++++++
2 files changed, 159 insertions(+), 20 deletions(-)
--
2.25.1
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-03-29 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:48 Geert Uytterhoeven [this message]
2022-03-29 9:48 ` [PATCH 1/2] pinctrl: renesas: r8a77990: Add RPC pins, groups, and functions Geert Uytterhoeven
2022-04-07 6:50 ` Wolfram Sang
2022-03-29 9:48 ` [PATCH 2/2] pinctrl: renesas: r8a77995: Add QSPI and " Geert Uytterhoeven
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.1648547080.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).