From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 00/09] Test R-Car Gen3 IMR-LX4 device
Date: Wed, 19 Dec 2018 19:26:06 +0900 [thread overview]
Message-ID: <154521516632.7290.5245227863765109428.sendpatchset@octo> (raw)
Test R-Car Gen3 IMR-LX4 device
[PATCH 01/09] Prototype code for basic IMR-LX4 test
[PATCH 02/09] arm64: dts: renesas: r8a7795: One IMR-LX4 device for R-Car H3
[PATCH 03/09] arm64: dts: renesas: r8a7796: One IMR-LX4 device for R-Car M3-W
[PATCH 04/09] arm64: dts: renesas: r8a77965: One IMR-LX4 device for R-Car M3-N
[PATCH 05/09] arm64: dts: renesas: r8a77970: One IMR-LX4 device for R-Car V3M
[PATCH 06/09] arm64: dts: renesas: r8a77980: One IMR-LX4 device for R-Car V3H
[PATCH 07/09] arm64: dts: renesas: r8a77995: One IMR-LX4 device for R-Car D3
[PATCH 08/09] arm64: dts: renesas: r8a77990: One IMR-LX4 device for R-Car E3
[PATCH 09/09] Random build workarounds for renesas-drivers
These patches temporarily introduce a IMR-LX4 driver that uses Runtime PM
to control clocks and power when performing a basic reset of the device.
The user should check console printouts and verify that register settings
are changed after the reset has been performed during probe().
Not intended for upstream merge. Successfully tested on 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 renesas-drivers-2018-12-18-v4.20-rc7
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 30 ---------
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 10 ---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 11 +++
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 10 +++
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 10 +++
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 10 +++
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 10 +++
arch/arm64/include/asm/smp.h | 2
drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 2
drivers/soc/renesas/Makefile | 2
drivers/soc/renesas/renesas-test-imr-lx4.c | 71 +++++++++++++++++++++++
drivers/tty/serial/sh-sci.c | 2
12 files changed, 126 insertions(+), 44 deletions(-)
next reply other threads:[~2018-12-19 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 10:26 Magnus Damm [this message]
2018-12-19 10:26 ` [PATCH 01/09] Prototype code for basic IMR-LX4 test Magnus Damm
2018-12-19 10:26 ` [PATCH 02/09] arm64: dts: renesas: r8a7795: One IMR-LX4 device for R-Car H3 Magnus Damm
2018-12-19 10:26 ` [PATCH 03/09] arm64: dts: renesas: r8a7796: One IMR-LX4 device for R-Car M3-W Magnus Damm
2018-12-19 10:26 ` [PATCH 04/09] arm64: dts: renesas: r8a77965: One IMR-LX4 device for R-Car M3-N Magnus Damm
2018-12-19 10:26 ` [PATCH 05/09] arm64: dts: renesas: r8a77970: One IMR-LX4 device for R-Car V3M Magnus Damm
2018-12-19 10:27 ` [PATCH 06/09] arm64: dts: renesas: r8a77980: One IMR-LX4 device for R-Car V3H Magnus Damm
2018-12-19 10:27 ` [PATCH 07/09] arm64: dts: renesas: r8a77995: One IMR-LX4 device for R-Car D3 Magnus Damm
2018-12-19 10:27 ` [PATCH 08/09] arm64: dts: renesas: r8a77990: One IMR-LX4 device for R-Car E3 Magnus Damm
2018-12-19 10:27 ` [PATCH 09/09] Random build workarounds for renesas-drivers 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=154521516632.7290.5245227863765109428.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;
as well as URLs for NNTP newsgroup(s).