From: Ulrich Hecht <uli+renesas@fpond.eu>
To: linux-renesas-soc@vger.kernel.org
Cc: horms@verge.net.au, geert@linux-m68k.org,
khiem.nguyen.xt@rvc.renesas.com, dien.pham.ry@renesas.com,
takeshi.kihara.df@renesas.com,
Ulrich Hecht <uli+renesas@fpond.eu>
Subject: [PATCH 0/5] H3/M3-W cpuidle support
Date: Fri, 17 Aug 2018 15:19:23 +0200 [thread overview]
Message-ID: <1534511968-19634-1-git-send-email-uli+renesas@fpond.eu> (raw)
Hi!
This series adds CPU idle support for H3 and M3-W. It's a straight
up-port from the BSP.
The part that disables cpuidle for the CA53 cores on M3ULCB is a bit
dodgy. Is it a valid assumption that all M3ULCB boards have an ES1.0
SoC?
CU
Uli
Dien Pham (2):
arm64: dts: r8a7795: Add cpuidle support for CA53 cores
arm64: dts: r8a7796: Add cpuidle support for CA53 cores
Khiem Nguyen (2):
arm64: dts: r8a7795: Add cpuidle support for CA57 cores
arm64: dts: r8a7796: Add cpuidle support for CA57 cores
Takeshi Kihara (1):
arm64: dts: r8a7796-m3ulcb: Disable cpuidle support for CA53 cores
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 32 ++++++++++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 22 ++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 30 ++++++++++++++++++++++++
3 files changed, 84 insertions(+)
--
2.7.4
next reply other threads:[~2018-08-17 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 13:19 Ulrich Hecht [this message]
2018-08-17 13:19 ` [PATCH 1/5] arm64: dts: r8a7795: Add cpuidle support for CA57 cores Ulrich Hecht
2018-09-05 13:29 ` Geert Uytterhoeven
2018-08-17 13:19 ` [PATCH 2/5] arm64: dts: r8a7795: Add cpuidle support for CA53 cores Ulrich Hecht
2018-08-17 13:19 ` [PATCH 3/5] arm64: dts: r8a7796: Add cpuidle support for CA57 cores Ulrich Hecht
2018-08-17 13:19 ` [PATCH 4/5] arm64: dts: r8a7796: Add cpuidle support for CA53 cores Ulrich Hecht
2018-08-17 13:19 ` [PATCH 5/5] arm64: dts: r8a7796-m3ulcb: Disable " Ulrich Hecht
2018-08-23 8:22 ` [PATCH 0/5] H3/M3-W cpuidle support Geert Uytterhoeven
2018-08-23 8:30 ` 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=1534511968-19634-1-git-send-email-uli+renesas@fpond.eu \
--to=uli+renesas@fpond.eu \
--cc=dien.pham.ry@renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=khiem.nguyen.xt@rvc.renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=takeshi.kihara.df@renesas.com \
/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).