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 <[email protected]>
---

 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(-)

Reply via email to