linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Phong Hoang <phong.hoang.wz@renesas.com>,
	Takeshi Kihara <takeshi.kihara.df@renesas.com>,
	linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] renesas: r8a779g0: Add missing SCIF_CLK2
Date: Thu, 18 Jan 2024 17:32:35 +0100	[thread overview]
Message-ID: <cover.1705589612.git.geert+renesas@glider.be> (raw)

	Hi all,

R-Car V4H actually has two SCIF_CLK pins.
The second pin provides the SCIF_CLK signal for HSCIF2 and SCIF4.
The first pin provides the SCIF_CLK signal for the other (H)SCIF
instances.

This patch series adds the missing SCIF_CLK2 pin group/function to the
R-Car V4H pin control driver and to the R-Car V4H DTS file, and fixes
the HSCIF2 and SCIF4 DT descriptions to refer to the proper clock.

As SCIF_CLK2 cannot be used on the White Hawk development board, I could
not test proper operation of HSCIF2 and SCIF4.  I did verify that HSCIF2
and SCIF4 do not operate properly when trying to use (the first and thus
incorrect) SCIF_CLK as the clock source.

I plan to queue these in renesas-pinctrl resp. renesas-devel for v6.9.

Thanks for your comments!

Geert Uytterhoeven (2):
  pinctrl: renesas: r8a779g0: Add missing SCIF_CLK2 pin group/function
  arm64: dts: renesas: r8a779g0: Add missing SCIF_CLK2

 arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 12 +++++++++---
 drivers/pinctrl/renesas/pfc-r8a779g0.c    | 14 ++++++++++++++
 2 files changed, 23 insertions(+), 3 deletions(-)

-- 
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-18 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 16:32 Geert Uytterhoeven [this message]
2024-01-18 16:32 ` [PATCH 1/2] pinctrl: renesas: r8a779g0: Add missing SCIF_CLK2 pin group/function Geert Uytterhoeven
2024-01-18 16:32 ` [PATCH 2/2] arm64: dts: renesas: r8a779g0: Add missing SCIF_CLK2 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.1705589612.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=phong.hoang.wz@renesas.com \
    --cc=takeshi.kihara.df@renesas.com \
    --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).