devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 00/14] pinctrl: renesas: Add support for R-Car V4M
Date: Fri, 26 Jan 2024 11:43:58 +0100	[thread overview]
Message-ID: <cover.1706264667.git.geert+renesas@glider.be> (raw)

	Hi all,

This patch series adds pin control support for the R-Car V4M (R8A779H0)
SoC.

Some, but not all, of this has been tested on the Gray Hawk Single
development board.

There are also a few unresolved questions:
  - According to the documentation, using I2C requires setting
    SEL_S{CL,DA}[0-3]_1 instead of SEL_S{CL,DA}[0-3]_0 in the MOD_SEL
    register.  However, I2C works regardless of this setting, just like
    on R-Car V4H (see commit 42cbd16e7c547499 ("pinctrl: renesas:
    r8a779g0: Fixup MODSEL8")),
  - Using i2c-gpio instead of i2c-rcar for I2C0 does not work, even
    when using a similar scheme like on R-Car S4 and V3U (see e.g.
    commit 8bdd369dba7ff2f8 ("pinctrl: renesas: r8a779f0: Fix GPIO
    function on I2C-capable pins").

For testing, I have updated [1] accordingly.
Thanks for your comments!

[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/v4m-gray-hawk-single-v2

Cong Dang (13):
  pinctrl: renesas: Initial R8A779H0 (R-Car V4M) PFC support
  pinctrl: renesas: r8a779h0: Add Ethernet AVB pins, groups, functions
  pinctrl: renesas: r8a779h0: Add SD/MMC pins, groups, functions
  pinctrl: renesas: r8a779h0: Add QSPI pins, groups, functions
  pinctrl: renesas: r8a779h0: Add SCIF pins, groups, functions
  pinctrl: renesas: r8a779h0: Add SCIF_CLK pins, groups, functions
  pinctrl: renesas: r8a779h0: Add HSCIF pins, groups, functions
  pinctrl: renesas: r8a779h0: Add I2C pins, groups, functions
  pinctrl: renesas: r8a779h0: Add MSIOF pins, groups, functions
  pinctrl: renesas: r8a779h0: Add PWM/TPU pins, groups, functions
  pinctrl: renesas: r8a779h0: Add CANFD pins, groups, functions
  pinctrl: renesas: r8a779h0: Add PCIe pins, groups, functions
  pinctrl: renesas: r8a779h0: Add Audio pins, groups, functions

Geert Uytterhoeven (1):
  dt-bindings: pinctrl: renesas,pfc: Document R-Car V4M support

 .../bindings/pinctrl/renesas,pfc.yaml         |    1 +
 drivers/pinctrl/renesas/Kconfig               |    5 +
 drivers/pinctrl/renesas/Makefile              |    1 +
 drivers/pinctrl/renesas/core.c                |    6 +
 drivers/pinctrl/renesas/pfc-r8a779h0.c        | 3967 +++++++++++++++++
 drivers/pinctrl/renesas/sh_pfc.h              |    1 +
 6 files changed, 3981 insertions(+)
 create mode 100644 drivers/pinctrl/renesas/pfc-r8a779h0.c

-- 
2.34.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

             reply	other threads:[~2024-01-26 10:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 10:43 Geert Uytterhoeven [this message]
2024-01-26 10:43 ` [PATCH 01/14] dt-bindings: pinctrl: renesas,pfc: Document R-Car V4M support Geert Uytterhoeven
2024-01-26 16:25   ` Conor Dooley
2024-01-26 10:44 ` [PATCH 02/14] pinctrl: renesas: Initial R8A779H0 (R-Car V4M) PFC support Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 03/14] pinctrl: renesas: r8a779h0: Add Ethernet AVB pins, groups, functions Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 04/14] pinctrl: renesas: r8a779h0: Add SD/MMC " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 05/14] pinctrl: renesas: r8a779h0: Add QSPI " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 06/14] pinctrl: renesas: r8a779h0: Add SCIF " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 07/14] pinctrl: renesas: r8a779h0: Add SCIF_CLK " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 08/14] pinctrl: renesas: r8a779h0: Add HSCIF " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 09/14] pinctrl: renesas: r8a779h0: Add I2C " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 10/14] pinctrl: renesas: r8a779h0: Add MSIOF " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 11/14] pinctrl: renesas: r8a779h0: Add PWM/TPU " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 12/14] pinctrl: renesas: r8a779h0: Add CANFD " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 13/14] pinctrl: renesas: r8a779h0: Add PCIe " Geert Uytterhoeven
2024-01-26 10:44 ` [PATCH 14/14] pinctrl: renesas: r8a779h0: Add Audio " Geert Uytterhoeven
2024-02-20 10:47 ` [PATCH 00/14] pinctrl: renesas: Add support for R-Car V4M 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.1706264667.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh+dt@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).