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>, arm-soc <soc@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/5] Renesas SoC updates for v5.5
Date: Fri, 18 Oct 2019 12:11:31 +0200	[thread overview]
Message-ID: <20191018101136.26350-1-geert+renesas@glider.be> (raw)

	Hi arm-soc folks,

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

It consists of 5 parts:

  [GIT PULL 1/5] Renesas ARM DT updates for v5.5

    - Whitespace cleanups.

  [GIT PULL 2/5] Renesas ARM64 defconfig updates for v5.5

    - Enable support for the new RZ/G2N (r8a774b1) SoC.

  [GIT PULL 3/5] Renesas ARM64 DT updates for v5.5

    - Support for the RZ/G2N (r8a774b1) SoC and the HiHope RZ/G2N board,
    - CPU idle support for R-Car H3 and M3-W,
    - LVDS and backlight support on the HiHope RZ/G2M and RZ/G2N boards,
      with Advantech idk-1110wr LVDS panel,
    - Minor fixes and improvements.

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

    - Add support for the new RZ/G2N (r8a774b1) SoC,
    - Fix System Controller power request conflicts on recent R-Car Gen3
      and RZ/G2N SoC variants and revisions,
    - Minor cleanups.

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

    - RZ/G2M update for the Renesas Timer Unit bindings,
    - Support for the new RZ/G2N (r8a774b1) SoC and the HiHope RZ/G2N
      board.

Note that the new Renesas RZ/G2N DT Binding Definitions are shared by
driver and DT source files, and thus included in 3 pull requests:
  - "[GIT PULL 3/5] Renesas ARM64 DT updates for v5.5" (for arm-soc),
  - "[GIT PULL 4/5] Renesas driver updates for v5.5" (for arm-soc).
  - "[GIT PULL] clk: renesas: Updates for v5.5] (for clk).

If you prefer to merge this dependency explicitly, please pull tag
renesas-r8a774b1-dt-binding-defs-tag first.

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:[~2019-10-18 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 10:11 Geert Uytterhoeven [this message]
2019-10-18 10:11 ` [PULL 1/5] Renesas ARM DT updates for v5.5 Geert Uytterhoeven
2019-10-18 10:11 ` [PULL 2/5] Renesas ARM64 defconfig " Geert Uytterhoeven
2019-10-18 10:11 ` [PULL 3/5] Renesas ARM64 DT " Geert Uytterhoeven
2019-10-18 10:11 ` [PULL 4/5] Renesas driver " Geert Uytterhoeven
2019-10-18 10:11 ` [PULL 5/5] 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=20191018101136.26350-1-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).