linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 1/4] Renesas ARM DT updates for v6.2
Date: Fri,  4 Nov 2022 11:49:53 +0100	[thread overview]
Message-ID: <cover.1667558738.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v6.2.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM DT updates for v6.2

    - DMA, SPI (MSIOF), external interrupt (INTC-EX), PWM (PWM and TPU),
      SDHI, HyperFLASH/QSPI (RPC), and serial ((H)SCIF) support for the
      R-Car V4H SoC,
    - I/O expander, eMMC, and QSPI FLASH support for the White Hawk
      development board,
    - Preparatory work to share r9a07g043.dtsi between the ARM-based
      RZ/G2UL (R9A07G043U) and the RISC-V-based RZ/Five (R9A07G043F) SoCs,
    - Miscellaneous fixes and improvements.

  [GIT PULL 2/4] Renesas ARM SoC updates for v6.2

    - Drop selecting GPIOLIB and PINCTRL, which are already automatically
      selected as part of the SOC_RENESAS config option in
      drivers/soc/renesas/Kconfig.

  [GIT PULL 3/4] Renesas driver updates for v6.2

    - Let SOC_RENESAS select GPIOLIB and PINCTRL, so this does not have to
      be handled in two (soon three: arm/arm64/riscv), places.

  [GIT PULL 4/4] Renesas DT binding updates for v6.2

    - Move renesas.yaml from arm to soc, and document RZ/Five support.

Note that the second pull request depends on the third, and thus is
based on it.

Thanks for pulling!

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-11-04 10:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 10:49 Geert Uytterhoeven [this message]
2022-11-04 10:49 ` [GIT PULL 1/4] Renesas ARM DT updates for v6.2 Geert Uytterhoeven
2022-11-04 10:49 ` [GIT PULL 2/4] Renesas ARM SoC " Geert Uytterhoeven
2022-11-04 10:49 ` [GIT PULL 3/4] Renesas driver " Geert Uytterhoeven
2022-11-04 10:49 ` [GIT PULL 4/4] Renesas DT binding " 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.1667558738.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=soc@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).