Linux Renesas SOC kernel development
 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/3] Renesas SoC updates for v6.7 (take two)
Date: Fri, 13 Oct 2023 14:39:12 +0200	[thread overview]
Message-ID: <cover.1697200117.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my second pull request for the inclusion of Renesas SoC updates
for v6.7.

It consists of 3 parts:

  [GIT PULL 1/3] Renesas ARM defconfig updates for v6.7 (take two)

    - Enable support for the Renesas RZ/G3S (R9A08G045) SoC in the arm64
      defconfig.

  [GIT PULL 2/3] Renesas DT binding updates for v6.7 (take two)

    - Document support for the Renesas RZ/G3S SMARC SoM and SMARC
      Carrier-II EVK development boards,
    - Document support for the Renesas R-Car S4 Starter Kit.

  [GIT PULL 3/3] Renesas DTS updates for v6.7 (take two)

    - Improve audio clock accuracy on the RZ/{G2L,G2LC,V2L} SMARC EVK
      development boards,
    - Add FLASH support for the Renesas Bock-W development board,
    - Add L2 cache and non-coherent DMA support on the RZ/Five SoC and the
      RZ/Five SMARC development board,
    - Add initial support for the RZ/G3S SoC and the RZ/G3S SMARC SoM and
      SMARC Carrier-II EVK development boards,
    - Add initial support for the R8A779F4 variant of the R-Car S4-8 SoC
      and the R-Car S4 Starter Kit development board,
    - Apply DT overlays to base DTBs to improve validation and usability.

  Note that this includes:
    - Tag clk-fixes-for-linus from the clock tree, which contains the
      fixed Versa3 clock generator clock index handling that was merged
      in v6.6-rc4,
    - Tag renesas-r9a08g045-dt-binding-defs-tag, which contains clock
      definitions for the Renesas RZ/G3S (R9A08G045) SoC, shared by the
      clock driver and DT source files.

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

             reply	other threads:[~2023-10-13 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 12:39 Geert Uytterhoeven [this message]
2023-10-13 12:39 ` [GIT PULL 1/3] Renesas ARM defconfig updates for v6.7 (take two) Geert Uytterhoeven
2023-10-13 12:39 ` [GIT PULL 2/3] Renesas DT binding " Geert Uytterhoeven
2023-10-13 12:39 ` [GIT PULL 3/3] Renesas DTS " 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.1697200117.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