From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC 00/06] R-Car Gen3 IMP-X5 prototype code
Date: Mon, 21 Jan 2019 21:16:43 +0900 [thread overview]
Message-ID: <154807300302.2406.14245640502137089757.sendpatchset@octo> (raw)
R-Car Gen3 IMP-X5 prototype code
[PATCH/RFC 01/06] Prototype code for IMP-X5
[PATCH/RFC 02/06] arm64: dts: renesas: r8a7795: One IMP-X5 device for R-Car H3
[PATCH/RFC 03/06] arm64: dts: renesas: r8a7796: One IMP-X5 device for R-Car M3-W
[PATCH/RFC 04/06] arm64: dts: renesas: r8a77965: One IMP-X5 device for R-Car M3-N
[PATCH/RFC 05/06] arm64: dts: renesas: r8a77970: One IMP-X5 device for R-Car V3M
[PATCH/RFC 06/06] arm64: dts: renesas: r8a77980: One IMP-X5 device for R-Car V3H
These patches temporarily introduce a IMP-X5 driver that uses Runtime PM
to control clocks and power when trying to access the device.
The user should check console printouts and comment out Run-time PM
bits of the code with/without power domain DT information to verify that
register settings are changed as expected. Per-SoC modifications of the
Clock, Reset and Power domain code may be required.
Not intended for upstream merge. Written for H3 ES2 ULCB.
Created as an example of how to test power domains for a certain device.
I hope to use this approach to test IPMMU power domain support in the future.
Not-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Developed on top of v5.0-rc3
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 9 +++
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 9 +++
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 9 +++
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 9 +++
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 9 +++
drivers/soc/renesas/Makefile | 2
drivers/soc/renesas/renesas-test-imp-x5.c | 77 +++++++++++++++++++++++++++++
7 files changed, 123 insertions(+), 1 deletion(-)
next reply other threads:[~2019-01-21 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:16 Magnus Damm [this message]
2019-01-21 12:16 ` [PATCH/RFC 01/06] Prototype code for IMP-X5 Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 02/06] arm64: dts: renesas: r8a7795: One IMP-X5 device for R-Car H3 Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 03/06] arm64: dts: renesas: r8a7796: One IMP-X5 device for R-Car M3-W Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 04/06] arm64: dts: renesas: r8a77965: One IMP-X5 device for R-Car M3-N Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 05/06] arm64: dts: renesas: r8a77970: One IMP-X5 device for R-Car V3M Magnus Damm
2019-01-21 12:17 ` [PATCH/RFC 06/06] arm64: dts: renesas: r8a77980: One IMP-X5 device for R-Car V3H Magnus Damm
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=154807300302.2406.14245640502137089757.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.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