From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/2] gpio: rcar: Add-R-Car S4-8 GPIO support
Date: Mon, 4 Apr 2022 17:29:47 +0200 [thread overview]
Message-ID: <cover.1649085875.git.geert+renesas@glider.be> (raw)
Hi Linus, Bartosz,
This patch series adds support for the Renesas R-Car S4-8 Soc to the
R-Car GPIO DT bindings and driver. It has been tested with i2c-gpio,
by reading the contents from the I2C EEPROMs on the Spider development
board.
Changes compared to v1:
- Drop RFC,
- Split series in DT bindings+driver and DTS series.
Thanks!
Geert Uytterhoeven (2):
dt-bindings: gpio: renesas,rcar-gpio: Add r8a779f0 support
gpio: rcar: Add R-Car Gen4 support
.../devicetree/bindings/gpio/renesas,rcar-gpio.yaml | 5 +++++
drivers/gpio/gpio-rcar.c | 7 +++++--
2 files changed, 10 insertions(+), 2 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-04-04 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 15:29 Geert Uytterhoeven [this message]
2022-04-04 15:29 ` [PATCH v2 1/2] dt-bindings: gpio: renesas,rcar-gpio: Add r8a779f0 support Geert Uytterhoeven
2022-04-04 15:38 ` Wolfram Sang
2022-04-04 15:29 ` [PATCH v2 2/2] gpio: rcar: Add R-Car Gen4 support Geert Uytterhoeven
2022-04-04 15:37 ` Wolfram Sang
2022-04-05 13:19 ` [PATCH v2 0/2] gpio: rcar: Add-R-Car S4-8 GPIO support Bartosz Golaszewski
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.1649085875.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).