devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>
Subject: [PATCH 0/2] Add APMU support to r8a77470
Date: Mon, 17 Sep 2018 09:44:08 +0100	[thread overview]
Message-ID: <1537173850-5310-1-git-send-email-fabrizio.castro@bp.renesas.com> (raw)

Dear All,

this series adds APMU support to the RZ/G1C (a.k.a. r8a77470).

Thanks,
Fab

Fabrizio Castro (2):
  dt-bindings: apmu: Document r8a77470 support
  ARM: dts: r8a77470: Add APMU node and second CPU core

 Documentation/devicetree/bindings/power/renesas,apmu.txt |  1 +
 arch/arm/boot/dts/r8a77470.dtsi                          | 16 ++++++++++++++++
 2 files changed, 17 insertions(+)

-- 
2.7.4

             reply	other threads:[~2018-09-17  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17  8:44 Fabrizio Castro [this message]
2018-09-17  8:44 ` [PATCH 1/2] dt-bindings: apmu: Document r8a77470 support Fabrizio Castro
2018-09-17  8:52   ` Geert Uytterhoeven
2018-09-19  8:24     ` Simon Horman
2018-09-17  8:44 ` [PATCH 2/2] ARM: dts: r8a77470: Add APMU node and second CPU core Fabrizio Castro
2018-09-17  8:53   ` Geert Uytterhoeven
2018-09-19  8:25     ` Simon Horman
2018-09-19  9:23       ` Simon Horman
2018-09-19 10:32         ` Fabrizio Castro
2018-09-19 10:24       ` Fabrizio Castro
2018-09-19 10:21     ` Fabrizio Castro
2018-09-21  7:15       ` Simon Horman

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=1537173850-5310-1-git-send-email-fabrizio.castro@bp.renesas.com \
    --to=fabrizio.castro@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).