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 0/4] Renesas SoC updates for v5.16
Date: Fri,  1 Oct 2021 11:42:42 +0200	[thread overview]
Message-ID: <cover.1633081144.git.geert+renesas@glider.be> (raw)

	Hi soc folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v5.15.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v5.16

    - Enable built-in (I2C, DMAC, USB PHY control) and modular (audio,
      ADC) build of drivers for the RZ/G2L SoC and SMARC EVK board,
    - Enable modular build of the Renesas TPU PWM driver for the R-Car
      V3U SoC.

  [GIT PULL 2/4] Renesas ARM DT updates for v5.16

    - I2C EEPROM support on the RZA2MEVB development board,
    - DMA, USB2.0, and audio support for the RZ/G2L SoC,
    - USB2.0, I2C, audio, ADC, and CANFD support for the RZ/G2L SMARC EVK
      development board,
    - Support for more R-Car Gen3e SoCs (H3e, M3e, M3Ne(-2G), D3e, E3e,
      H3Ne),
    - PWM support for the R-Car M3-W+ and V3U SoCs,
    - IPMMU support for SDHI on the R-Car V3U SoC,
    - Switches support for the Falcon development board,
    - Improve Ethernet PHY descriptions to fix reset handling after kexec,
    - Miscellaneous fixes and improvements.

  [GIT PULL 3/4] Renesas driver updates for v5.16

    - Initial support for the new R-Car H3e, M3e, M3Ne(-2G), D3e, E3e, and
      H3Ne SoCs.

  [GIT PULL 4/4] Renesas DT binding updates for v5.16

    - Document support for the new R-Car H3e, M3e, M3Ne(-2G), D3e, E3e, and
      H3Ne SoCs and boards.

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:[~2021-10-01  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  9:42 Geert Uytterhoeven [this message]
2021-10-01  9:42 ` [GIT PULL 1/4] Renesas ARM defconfig updates for v5.16 Geert Uytterhoeven
2021-10-01  9:42 ` [GIT PULL 2/4] Renesas ARM DT " Geert Uytterhoeven
2021-10-01  9:42 ` [GIT PULL 3/4] Renesas driver " Geert Uytterhoeven
2021-10-01  9:42 ` [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.1633081144.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).