...

HTML

<font size=12><B>Device Tree and Device Driver Information</B></font>

<! To make a ToC move with the page, add a HTML macro and put this in it >
<style> .toc-macro {position: static !important;} </style>

<! Make the ToC in-line (not float on the right) >
<style> .toc-macro {float: leftnone !important;} </style>

This page contains helpful notes about Device Tree configurations

Table of Contents

indent	20px

RZ Evaluation Board Files



<! Remove border >
<style> .toc-macro {border: none !important;} </style>

<! Transparent background (no color) >
<style> .toc-macro {background: transparent !important;} </style>

This page contains helpful notes about Device Tree configurations and Device Driver details

Table of Contents

indent	20px

RZ Evaluation Board Files

Device Tree files for Renesas SoC Device Tree files for Renesas SoC and evaluation boards are under the directory arch/arm64/boot/dts/renesas/
Below is the list of Device Tree files used for the Renesas Evaluation boards.
Because the evaluation kits share common boards, and have many different test/demo configurations, there are many include files (.dtsi) for any single device tree (.dts) build. For your custom board, you might only need your Device Tree for your board (my_board.dst) and that will only #include one other file which will be the base SoC file (RZ/G2H for example will #include "r8a774e1.dtsi").
RZ board names that end in "-dev" are internal Renesas boards. While their Device Trees files appear in the BSP, they are not mainlined.

...

RZ/G2H, G2M, G2N, G2E:
- drivers/pinctrl/renesas/core.c, pinctrl.c, pfc-xxxx.c, etc... (refer to the Makefile)
- CONFIG_PINCTRL_RENESAS=y
- Documentation/devicetree/bindings/pinctrl/renesas,pcf.yaml

RZ/G2L, G2LC, G2UL:
RZ/V2L:
RZ/G3S: , V2L:
- drivers/pinctrl/renesas/pinctrl-rzg2l.c
- CONFIG_PINCTRL_RZG2L=y
- Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-pinctrl.yaml

...

Helpful Debug Messages: Sometimes it is helpful to see how the pins are being configured on boot up. By putting #define DEBUG at the top of the driver file (pinctrl.c or pinctrl-rzg2.c) will make it print out how each pins is being configured.

Device Tree Examples

Expand
title
(see device tree for evaluation board)
Use any GPIO as wake-up source, e.g. P37.2:

...

   gpio_keys {
        compatible = "gpio-keys";
        #address-cells = <1>;
        #size-cells = <0>;
        autorepeat;

        P37_2 {
            label = "GPIO Key WAKEUP";
            linux,code = <143>;
            wakeup-source;
            interrupt-parent = <&pinctrl>;
            interrupts = <RZG2L_GPIO(37, 2) IRQ_TYPE_EDGE_FALLING>;
            debounce-interval = <50>;
        };
    };

...

IRQ0-7

Linux Drivers

RZ/G2H, G2M, G2N, G2E:
- CONFIG_xxx=y

RZ/G2L, G2LC, G2UL, V2L:
- drivers/irqchip/irq-renesas-rzg2l.c
- CONFIG_RENESAS_RZG2L_IRQC=y
- Added after 'rz-5.10-cip13'

Notes

Device Tree Examples

Use NMI as wake-up source:

...

Expand

title	Example of defining a GPIO with pull-down

&pinctrl {
        test_gpio: test-gpio {

...

gpio-hog;

...

 gpios = <RZG2L_GPIO(6, 0) (GPIO_ACTIVE_HIGH

...

| GPIO_PULL_DOWN)>;

...

input;

...

line-name =

...

"test_gpio"; };

...

};

IRQ0-7

Linux Drivers

RZ/G2H, G2M, G2N, G2E:
- CONFIG_xxx=y

RZ/G2L, G2LC, G2UL, V2L:
- drivers/irqchip/irq-renesas-rzg2l.c
- CONFIG_RENESAS_RZG2L_IRQC=y
- Added after 'rz-5.10-cip13'

Notes

Device Tree Examples

Use NMI as wake-up source:

   gpio_keys {
       compatible = "gpio-keys";
       #address-cells = <1>;
       #size-cells = <0>;
       autorepeat;
       pinctrl-0 = <&user_key_pin>;

       IRQ_7NMI {
           label = "IRQ_7NMI Key WAKEUP";
           linux,code = <143>;
           wakeup-source;
           interrupt-parent = <&intc_ex>;
           interrupts = <7<8 IRQ_TYPE_EDGE_FALLING>;
           debounce-interval = <50>;
       };
   };

&intc_ex {
    status = "okay";
};

&pinctrl{
	user_key_pin: user_key {
		pinmux = <RZG2L_PORT_PINMUX(3, 1, 1)>;	/* IRQ7 */
	};
};

Display

Linux Drivers

Common:
- drivers/gpu/drm/rcar-du/*
  - CONFIG_DRM_RCAR_DU=y
- drivers/media/platform/vsp1/*
  - CONFIG_VIDEO_RENESAS_VSP1=y
RZ/G2H, G2M, G2N, G2E:
- CONFIG_DRM_RCAR_LVDS=y
RZ/G2L, G2LC, G2UL, V2L:
- drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.h
- drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.c
- drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi_regs.h

Notes

IRQs can be used as well:
   gpio_keys {
       compatible = "gpio-keys";
       #address-cells = <1>;
       #size-cells = <0>;
       autorepeat;
       pinctrl-0 = <&user_key_pin>;

       IRQ_7 {
           label = "IRQ_7 Key WAKEUP";
           linux,code = <143>;
           wakeup-source;
           interrupt-parent = <&intc_ex>;
           interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
           debounce-interval = <50>;
       };
   };

&intc_ex {
    status = "okay";
};

&pinctrl{
	user_key_pin: user_key {
		pinmux = <RZG2L_PORT_PINMUX(3, 1, 1)>;	/* IRQ7 */
	};
}; 
Display
Linux Drivers
Common:drivers/gpu/drm/rcar-du/*CONFIG_DRM_RCAR_DU=y
drivers/media/platform/vsp1/*CONFIG_VIDEO_RENESAS_VSP1=y
RZ/G2H, G2M, G2N, G2E:CONFIG_DRM_RCAR_LVDS=y
RZ/G2L, G2LC, G2UL, V2L:drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.h
drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi.c
drivers/gpu/drm/rcar-du/rzg2l_mipi_dsi_regs.h
Notes
Ports Node When defining ports { } (meaning more than 1 port), you must set #address-cells = <1>; and #size-cells = <0>;. For more information, see the documentation in the kernel source: Documentation/devicetree/bindings/media/video-interfaces.txt
Resolution and Clock Definitions: An LCD Panel will have it's own separate driver. That driver will define the clock rate and resolution. The Renesas LCD driver will then get that information in order to set up the LCD controller (DU) output.
MIPI DSI Overview: Here is a good article explaining the MIPI DSI interface, packets and commands:  https://circuitcellar.com/resources/quickbits/mipi-display-serial-interface
MIPI DCS Commands: Many (most) MIPI DSI Panels require setup command (DCS) to be set over MIPI DSI to configure the panel's controller before pixel data can be sent. This is why there is usually a separate driver for each LCD since these commands are specific to each LCD panel.
Simple-Panel Driver: If your panel requires no special setup (
Ports Node When defining ports { }, you must set #address-cells = <1>; and #size-cells = <0>;. For more information, see the documentation in the kernel source: Documentation/devicetree/bindings/media/video-interfaces.txt
Resolution and Clock Definitions: An LCD Panel will have it's own separate driver. That driver will define the clock rate and resolution. The Renesas LCD driver will then get that information in order to set up the LCD controller (DU) output.
MIPI DSI Overview: Here is a good article explaining the MIPI DSI interface, packets and commands. https://circuitcellar.com/resources/quickbits/mipi-display-serial-interface
MIPI DCS Commands: Many (most) MIPI DSI Panels require setup command (DCS) to be set over MIPI DSI to configure the panel's controller before pixel data can be sent. This is why there is usually a separate driver for each LCD since these commands are specific to each LCD panel.
Simple-Panel Driver: If your panel requires no special setup (no MIPI DSI DCS commands) or your system is configuring your LCD manually over I2C, or you are using a parallel RGB panel that typically requires no setup, you can use the kernel's "simple-panel" driver.The main reason is that you need to tell the kernel about the resolution and pixel timing is of your panel, but that information is not described in a Device Tree, it must come from a source code driver file. The panel-simple driver is there as a way to do that by simply adding in a new entry for your custom panel.
Note that you will be required to edit the driver file (drivers/gpu/drm/panel/panel-simple.c) to add your specific panel resolution and timing that you want
. See kernel documentation Documentation/devicetree/bindings/panel/simple-panel.txt..
It is possible to set all your timing parameters in the Device Tree an not edit the panel-simple.c driver. You do this by specifying compatible = "panel-dpi". See example below
You must set CONFIG_DRM_PANEL_SIMPLE=y in your kernel to use this driver.
See kernel documentation Documentation/devicetree/bindings/panel/simple-panel.txt.
Parallel RGB Parallel RGB LCD: Since a parallel LCD does not need any special setup, you can use simple-panel driver in the kernel.
Check Display Settings: You can use the command modetest -M rcar-du -c to check the status of your display driver. It will also show you the supported resolutions of your display (in the case that you are using an HDMI interface where it will read what is supported by the HDMI panel).
Check VBLANK Timings: You can use the command vbltest -M rcar-du to check the VBLANK timings. If your result is always around 60Hz, your panel is set correctly.
...
 Expand
title Example of MIPI DSI Panel on RZ/G2L
Ilitek ILI9881c panel controller
2-lane MIPI interface
800x1280 Portrait Panel
Please remember "reg = <0>;" in panel@0
&du {
	status = "okay";
};

&dsi0 {
	status = "okay";
	#address-cells = <1>;
	#size-cells = <0>;

	ports {
			#address&du {
	status = "okay";
};

&dsi0 {
	status = "okay";
	#address-cells = <1>;
	#size-cells = <0>;

	ports {
			#address-cells = <1>;
			#size-cells = <0>;

			port@1 {
					dsi0_out: endpoint {
							remote-endpoint = <&panel_in>;
							data-lanes = <1 2>;
					};
			};
	};

	panel@0 {
			compatible = "ilitek,ili9881c";
			reg = <0>;
			dsi-lanes = <2>;
			enable-gpios = <&pinctrl RZG2L_GPIO(43, 0) GPIO_ACTIVE_HIGH>;
			backlight = <&backlight>;
			status = "okay";

			port {
					panel_in: endpoint {
							remote-endpoint = <&dsi0_out>;
					};
			};
	};
};
 Expand
title Example of Parallel(RGB) Panel on RZ/G2L (5.10)
Please use kernel version 5.10.201-cip41+
Configure pins
&pinctrl {
	du_pins: du {
		data {
			pinmux = <RZG2L_PORT_PINMUX(7, 2, 1)>,
				 <RZG2L_PORT_PINMUX(8, 0, 1)>,
				 <RZG2L_PORT_PINMUX(8, 1, 1)>,
				 <RZG2L_PORT_PINMUX(8, 2, 1)>,
				 <RZG2L_PORT_PINMUX(9, 0, 1)>,
				 <RZG2L_PORT_PINMUX(9, 1, 1)>,
				 <RZG2L_PORT_PINMUX(10, 0, 1)>,
				 <RZG2L_PORT_PINMUX(10, 1, 1)>,
				 <RZG2L_PORT_PINMUX(11, 0, 1)>,
				 <RZG2L_PORT_PINMUX(11, 1, 1)>,
				 <RZG2L_PORT_PINMUX(12, 0, 1)>,
				 <RZG2L_PORT_PINMUX(12, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 0, 1)>,
				 <RZG2L_PORT_PINMUX(13, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 2, 1)>,
				 <RZG2L_PORT_PINMUX(14, 0, 1)>,
				 <RZG2L_PORT_PINMUX(14, 1, 1)>,
				 <RZG2L_PORT_PINMUX(15, 0, 1)>,
				 <RZG2L_PORT_PINMUX(15, 1, 1)>,
				 <RZG2L_PORT_PINMUX(16, 0, 1)>,
				 <RZG2L_PORT_PINMUX(16, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 0, 1)>,
				 <RZG2L_PORT_PINMUX(17, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 2, 1)>;
		};

		sync {
			pinmux = <RZG2L_PORT_PINMUX(6, 1, 1)>, /* HSYNC */
				 <RZG2L_PORT_PINMUX(7, 0, 1)>; /* VSYNC */
		};

		de {
			pinmux = <RZG2L_PORT_PINMUX(7, 1, 1)>; /* DE */
		};

		clk {
			pinmux = <RZG2L_PORT_PINMUX(6, 0, 1)>; /* CLK */
		};
	};
};
We want to use simple panel driver and add the device node
panel_rgb: panel-rgb {
      		compatible = "arm,rtsm-display"; //<-- this property "arm,rtsm-display" is an example.
                                             // please fill in the correct information based on your panel spec.
      		port {
        		panel_in_rgb: endpoint {
          					remote-endpoint = <&du_out_rgb>;
       			};
     		};
};
Add endpoint for DU RGB out:
&du {
	pinctrl-0 = <&du_pins>;
	pinctrl-names = "default";
	status = "okay";

	ports {
		port@0 {
			du_out_rgb: endpoint {
						remote-endpoint = <&panel_in_rgb>;
			};
		};
	};
};
We want the MIPI DSI driver disabled
&dsi0 {
	status = "disabled";
};

 Expand
title Simple Panel Example using Device Tree only ("panel-dpi")
If you do not want to edit the panel-simple.c file, you can use compatible = "panel-dpi" and then enter your LCD timings in the Device Tree.
Here is an example of attaching a parallel RGB LCD to a RZ/G2L and using "panel-dpi" and only using the Device Tree. The driver panel-simple.c does not have to be modified.
Remember, the kernel configuration CONFIG_DRM_PANEL_SIMPLE=y must be set.

/ {
    panel_rgb: panel-rgb {
        compatible = "panel-dpi";

        /* panel-timing is used for "panel-dpi" compatible */
        panel-timing {
            clock-frequency = <9000000>;
            hactive = <480>;
            vactive = <272>;
            hsync-len = <43>;
            hfront-porch = <8>;
            hback-porch = <41>;
            vfront-porch = <4>;
            vback-porch = <10>;
            vsync-len = <21>;
        };

        port {
            panel_in_rgb: endpoint {
                remote-endpoint = <&du_out_rgb>;
            };
        };
    };
};

&pinctrl {
    du_pins: du {
        data {
            pinmux = <RZG2L_PORT_PINMUX(14, 1, 1)>,
            <RZG2L_PORT_PINMUX(15, 0, 1)>,
            <RZG2L_PORT_PINMUX(15, 1, 1)>,
            <RZG2L_PORT_PINMUX(16, 0, 1)>,
            <RZG2L_PORT_PINMUX(16, 1, 1)>,
            <RZG2L_PORT_PINMUX(17, 0, 1)>,
            <RZG2L_PORT_PINMUX(17, 1, 1)>,
            <RZG2L_PORT_PINMUX(17, 2, 1)>,
            <RZG2L_PORT_PINMUX(11, 0, 1)>,
            <RZG2L_PORT_PINMUX(11, 1, 1)>,
            <RZG2L_PORT_PINMUX(12, 0, 1)>,
            <RZG2L_PORT_PINMUX(12, 1, 1)>,
            <RZG2L_PORT_PINMUX(13, 0, 1)>,
            <RZG2L_PORT_PINMUX(13, 1, 1)>,
            <RZG2L_PORT_PINMUX(13, 2, 1)>,
            <RZG2L_PORT_PINMUX(14, 0, 1)>,
            <RZG2L_PORT_PINMUX(7, 2, 1)>,
            <RZG2L_PORT_PINMUX(8, 0, 1)>,
            <RZG2L_PORT_PINMUX(8, 1, 1)>,
            <RZG2L_PORT_PINMUX(8, 2, 1)>,
            <RZG2L_PORT_PINMUX(9, 0, 1)>,
            <RZG2L_PORT_PINMUX(9, 1, 1)>,
            <RZG2L_PORT_PINMUX(10, 0, 1)>,
            <RZG2L_PORT_PINMUX(10, 1, 1)>;
        };

        sync {
            pinmux = <RZG2L_PORT_PINMUX(6, 1, 1)>, /* HSYNC */
            <RZG2L_PORT_PINMUX(7, 0, 1)>; /* VSYNC */
        };

        de {
            pinmux = <RZG2L_PORT_PINMUX(7, 1, 1)>; /* DE */
        };

        clk {
            pinmux = <RZG2L_PORT_PINMUX(6, 0, 1)>; /* CLK */
        };
    };
};

&dsi0 {
    status = "disabled";
};

&du {
    pinctrl-0 = <&du_pins>;
    pinctrl-names = "default";
    status = "okay";

    ports {
        port@0 {
            du_out_rgb: endpoint {
                remote-endpoint = <&panel_in_rgb>;
            };
        };
    };
};



 Expand
title Example of RGB Panel on RZ/G2L (4.19 kernel only)
Configure pins
&pinctrl {
	du_pins: du {
		data {
			pinmux = <RZG2L_PORT_PINMUX(7,  2, 1)>,
				 <RZG2L_PORT_PINMUX(8,  0, 1)>,
				 <RZG2L_PORT_PINMUX(8,  1, 1)>,
				 <RZG2L_PORT_PINMUX(8,  2, 1)>,
				 <RZG2L_PORT_PINMUX(9,  0, 1)>,
				 <RZG2L_PORT_PINMUX(9,  1, 1)>,
				 <RZG2L_PORT_PINMUX(10, 0, 1)>,
				 <RZG2L_PORT_PINMUX(10, 1, 1)>,
				 <RZG2L_PORT_PINMUX(11, 0, 1)>,
				 <RZG2L_PORT_PINMUX(11, 1, 1)>,
				 <RZG2L_PORT_PINMUX(12, 0, 1)>,
				 <RZG2L_PORT_PINMUX(12, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 0, 1)>,
				 <RZG2L_PORT_PINMUX(13, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 2, 1)>,
				 <RZG2L_PORT_PINMUX(14, 0, 1)>,
				 <RZG2L_PORT_PINMUX(14, 1, 1)>,
				 <RZG2L_PORT_PINMUX(15, 0, 1)>,
				 <RZG2L_PORT_PINMUX(15, 1, 1)>,
				 <RZG2L_PORT_PINMUX(16, 0, 1)>,
				 <RZG2L_PORT_PINMUX(16, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 0, 1)>,
				 <RZG2L_PORT_PINMUX(17, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 2, 1)>;
		};

		sync {
			pinmux = <RZG2L_PORT_PINMUX(6, 1, 1)>, /* HSYNC */
				 <RZG2L_PORT_PINMUX(7, 0, 1)>; /* VSYNC */
		};

		de {
			pinmux = <RZG2L_PORT_PINMUX(7, 1, 1)>; /* DE */
		};
		
		clk {
			pinmux = <RZG2L_PORT_PINMUX(6, 0, 1)>; /* CLK */
		};
	};
};

Add a rgb-dummy device
	rgb-dummy {
		compatible = "renesas,rgb-dummy";
		ports {
			#address-cells = <1>;
			#size-cells = <0>;

			port@0 {
				reg = <0>;
				rgb_in: endpoint {
					remote-endpoint = <&du_out_rgb>;
					};
				};
				port@1 {
					reg = <1>;
						rgb_out: endpoint {
							remote-endpoint = <&panel_in>;
						};
				};
			};
		};
Add panel device node:
panel {
	/* 
	* Define code for panel here such as compatible, backlight, power,...
	* Can refer drivers/gpu/drm/panel/panel-simple.c
	*/
	port {
		panel_in: endpoint {
			remote-endpoint = <&rgb_out>;
		};
	};
};

We want the MIPI DSI driver disabled
&dsi0 {
	status = "disabled";
};
Add endpoint for DU RGB out:
&du {
	pinctrl-0 = <&du_pins>;
	pinctrl-names = "default";

	ports {
		port@0 {
			du_out_rgb: endpoint {
				remote-endpoint = <&rgb_in>;
			};
		};
	};
 };


Audio
 Linux Drivers
RZ/G2H, G2M, G2N, G2E: rz_linux-cip/sound/soc/sh/rcar/*.c
RZ/G2L, G2LC, G2UL, V2L: rz_linux-cip/sound/soc/sh/rz-ssi.c
Device Tree Examples
Configure pins
&pinctrl {
	du_pins: du {
		data {
			pinmux = <RZG2L_PORT_PINMUX(7,  2, 1)>,
				 <RZG2L_PORT_PINMUX(8,  0, 1)>,
				 <RZG2L_PORT_PINMUX(8,  1, 1)>,
				 <RZG2L_PORT_PINMUX(8,  2, 1)>,
				 <RZG2L_PORT_PINMUX(9,  0, 1)>,
				 <RZG2L_PORT_PINMUX(9,  1, 1)>,
				 <RZG2L_PORT_PINMUX(10, 0, 1)>,
				 <RZG2L_PORT_PINMUX(10, 1, 1)>,
				 <RZG2L_PORT_PINMUX(11, 0, 1)>,
				 <RZG2L_PORT_PINMUX(11, 1, 1)>,
				 <RZG2L_PORT_PINMUX(12, 0, 1)>,
				 <RZG2L_PORT_PINMUX(12, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 0, 1)>,
				 <RZG2L_PORT_PINMUX(13, 1, 1)>,
				 <RZG2L_PORT_PINMUX(13, 2, 1)>,
				 <RZG2L_PORT_PINMUX(14, 0, 1)>,
				 <RZG2L_PORT_PINMUX(14, 1, 1)>,
				 <RZG2L_PORT_PINMUX(15, 0, 1)>,
				 <RZG2L_PORT_PINMUX(15, 1, 1)>,
				 <RZG2L_PORT_PINMUX(16, 0, 1)>,
				 <RZG2L_PORT_PINMUX(16, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 0, 1)>,
				 <RZG2L_PORT_PINMUX(17, 1, 1)>,
				 <RZG2L_PORT_PINMUX(17, 2, 1)>;
		};

		sync {
			pinmux = <RZG2L_PORT_PINMUX(6, 1, 1)>, /* HSYNC */
				 <RZG2L_PORT_PINMUX(7, 0, 1)>; /* VSYNC */
		};

		de {
			pinmux = <RZG2L_PORT_PINMUX(7, 1, 1)>; /* DE */
		};
		
		clk {
			pinmux = <RZG2L_PORT_PINMUX(6, 0, 1)>; /* CLK */
		};
	};
};
Add a rgb-dummy device
	rgb-dummy {
		compatible = "renesas,rgb-dummy";
		ports {
			#address-cells = <1>;
			#size-cells = <0>;

			port@0 {
				reg = <0>;
				rgb_in: endpoint {
					remote-endpoint = <&du_out_rgb>;
					};
				};
				port@1 {
					reg = <1>;
						rgb_out: endpoint {
							remote-endpoint = <&panel_in>;
						};
				};
			};
		};
Add panel device node:
panel {
	/* 
	* Define code for panel here such as compatible, backlight, power,...
	* Can refer drivers/gpu/drm/panel/panel-simple.c
	*/
	port {
		panel_in: endpoint {
			remote-endpoint = <&rgb_out>;
		};
	};
};
We want the MIPI DSI driver disabled
&dsi0 {
	status = "disabled";
};
Add endpoint for DU RGB out:
&du {
	pinctrl-0 = <&du_pins>;
	pinctrl-names = "default";

	ports {
		port@0 {
			du_out_rgb: endpoint {
				remote-endpoint = <&rgb_in>;
			};
		};
	};
 };

 Expand
title Example of MAX9867 codec with MAX98390 Amplifier for RZ/G2L
Here is an example of a MAX9867 on SSI channel 3, using I2C-3. MAX98390 Amplifier on I2C-2.
This is for the Linux-5.10 kernel. For the older Linux-4.19 kernel, there are some differences.
Pin Setup
&pinctrl {

	/* MAX98390 Amplifier */
	i2c2_pins: i2c2 {
		pinmux = <RZG2L_PORT_PINMUX(42, 3, 1)>, /* SDA */
			 <RZG2L_PORT_PINMUX(42, 4, 1)>; /* SCL */
	};

	/* MAX9867 Codec */
	i2c3_pins: i2c3 {
		pinmux = <RZG2L_PORT_PINMUX(18, 0, 3)>, /* SDA */
			 <RZG2L_PORT_PINMUX(18, 1, 3)>; /* SCL */
	};

	ssi3_pins: ssi3 {
	pinmux = <RZG2L_PORT_PINMUX(31, 0, 5)>, /* BCK */
		<RZG2L_PORT_PINMUX(31, 1, 5)>, /* RCK */
		<RZG2L_PORT_PINMUX(32, 0, 5)>, /* TXD */
		<RZG2L_PORT_PINMUX(32, 1, 5)>; /* RXD */
	};
};
Enable SSI channel
&ssi3 {
	pinctrl-0 = <&ssi3_pins>;
	pinctrl-names = "default";

	#sound-dai-cells = <1>;
	
		#size-cellsstatus = 
<0>"okay";

			port@1 {
					dsi0_out: endpoint};
Create a node for the MAX9867
	my_snd: sound {
		
					remote-endpointcompatible = 
<&panel_in>"simple-audio-card";
		
					data-lanes = <1 2>;
					};
			};
	};

	panel@0 {
			compatible = "ilitek,ili9881c";
			reg = <0>;
			dsi-lanes = <2>;
			enable-gpios = <&pinctrl RZG2L_GPIO(43, 0) GPIO_ACTIVE_HIGH>;
			backlight = <&backlight>;
			status = "okay";

			port {
					panel_in: endpointsimple-audio-card,widgets = "Speaker", "Ext Spk";

		simple-audio-card,routing =
		"Ext Spk", "BE_OUT";
		"Ext Spk", "LOUT",
		"Ext Spk", "ROUT";

		/* MAX98390 Amplifier */
		simple-audio-card,dai-link@0{
			format = "i2s";
			bitclock-master = <&cpu_dai3>;
			frame-master = <&cpu_dai3>;
			mclk-fs = <256>;
			cpu_dai3: cpu {
				sound-dai = <&ssi3>;
			};

			codec_dai3: codec {
				
			remote-endpointsound-dai = <&
dsi0_out>max98390>;
				
	}clocks = <&mclk>;
			};
		};
};
 Expand
title Example of RGB Panel on RZ/G2L
Audio
 
Linux Drivers
RZ/G2H, G2M, G2N, G2E: rz_linux-cip/sound/soc/sh/rcar/*.c
RZ/G2L, G2LC, G2UL, V2L: rz_linux-cip/sound/soc/sh/rz-ssi.c
Device Tree Examples

		/* MAX9867 Codec */
		simple-audio-card,dai-link@1{
			format = "i2s";
			bitclock-master = <&cpu_dai0>;
			frame-master = <&cpu_dai0>;
			mclk-fs = <256>;
			cpu_dai0: cpu {
				sound-dai = <&ssi0>;
			};

			codec_dai0: codec {
				sound-dai = <&max9867>;
				clocks = <&mclk>;
			};
		};
	};

I2C node for the Codec and Amp
&i2c2 {
	pinctrl-0 = <&i2c2_pins>;
	pinctrl-names = "default";

	status = "okay";
	clock-frequency = <400000>;

	/* MAX98390 Amplifier */
	max98390: codec@3d {
		status = "okay";
		compatible = "maxim,max98390";
		#sound-dai-cells = <0>;
		reg = <0x3d>;
	};
};

&i2c3 {
	pinctrl-0 = <&i2c3_pins>;
	pinctrl-names = "default";

	status = "okay";
	clock-frequency = <400000>;

	/* MAX9867 Codec */
	max9867: codec@18 {
		status = "okay";
		compatible = "maxim,max9867";
		#sound-dai-cells = <0>;
		reg = <0x18>;
	};
};


Camera
Linux Drivers
RZ/G2H, G2M, G2N, G2E:CONFIG_xxx=y
RZ/G2L, G2LC, G2UL, V2L:CONFIG_xxx=y
Notes
Device Tree Examples
(see device tree for evaluation board)

Ethernet
 Linux Drivers
RZ/G2H, G2M, G2N, G2E, G2L, G2LC, G2UL, V2L:rz_linux-cip/drivers/net/ethernet/renesas/ (ravb_main.c, ravb_ptp.c)
Documentation/devicetree/bindings/net/renesas,etheravb.yaml
CONFIG_NET_VENDOR_RENESAS=y
# CONFIG_SH_ETH is not set
CONFIG_RAVB=y
Notes
The Link Status input pin (LINKSTA) is not used. The driver instead relies on the PHY to inform it that the link is up by using in-band status messages on the RGMII lines.
Do not forget to set the correct voltage levels for the pins (3.3v, 1.5v, etc..) in the device tree in the pinctrl node.You use the syntax "power-source = <3300>;" when you declare the pins for Ethernet. If an Ethernet PHY supports multiple voltages (3.3v or 1.8v), then choose the lower voltage because the Electrical Characteristics are better.
Refer to the pinctrl documentation in the kernel for more info.
Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-pinctrl.yaml
Documentation/devicetree/bindings/pinctrl/renesas,pcf.yaml
In the Device Tree, the MDIO address is set by @x and the "reg =<x>;" For example, MDIO address of 0:
	phy0: ethernet-phy@0 {
		reg = <0>;
If using MII (not RGMII), do not include output-enable; in txc{  } in your Device Tree. For RGMII, TX_CLK is always an output. But for MII, TX_CLK pin needs to be an input, so output-enable should not be set.


Device Tree Examples
 Expand
title Example of enabling MII mode for RZ/G2L
Ethernet node for MII mode
&eth0 {
	pinctrl-0 = <&eth0_mii_pins>;
	pinctrl-names = "default";
	phy-handle = <&phy0>;
	phy-mode = "mii";
	status = "okay";

	phy0: ethernet-phy@7 {
		compatible = "ethernet-phy-id0022.1640",
			     "ethernet-phy-ieee802.3-c22";
		reg = <7>;
		rxc-skew-psec = <2400>;
		txc-skew-psec = <2400>;
		rxdv-skew-psec = <0>;
		txdv-skew-psec = <0>;
		rxd0-skew-psec = <0>;
		rxd1-skew-psec = <0>;
		rxd2-skew-psec = <0>;
		rxd3-skew-psec = <0>;
		txd0-skew-psec = <0>;
		txd1-skew-psec = <0>;
		txd2-skew-psec = <0>;
		txd3-skew-psec = <0>;

		interrupt-parent = <&pinctrl>;
		interrupts = <RZG2L_GPIO(1, 0) IRQ_TYPE_LEVEL_LOW>;
	};
};

&eth1 {
	pinctrl-0 = <&eth1_mii_pins>;
	pinctrl-names = "default";
	phy-handle = <&phy1>;
	phy-mode = "mii";
	status = "okay";

	phy1: ethernet-phy@7 {
		compatible = "ethernet-phy-id0022.1640",
			     "ethernet-phy-ieee802.3-c22";
		reg = <7>;
		rxc-skew-psec = <2400>;
		txc-skew-psec = <2400>;
		rxdv-skew-psec = <0>;
		txdv-skew-psec = <0>;
		rxd0-skew-psec = <0>;
		rxd1-skew-psec = <0>;
		rxd2-skew-psec = <0>;
		rxd3-skew-psec = <0>;
		txd0-skew-psec = <0>;
		txd1-skew-psec = <0>;
		txd2-skew-psec = <0>;
		txd3-skew-psec = <0>;

		interrupt-parent = <&pinctrl>;
		interrupts = <RZG2L_GPIO(1, 1) IRQ_TYPE_LEVEL_LOW>;
	};
};

Pin Setup
&pinctrl {

	eth0_mii_pins: eth0
 Expand
title Example of MAX9867 codec with MAX98390 Amplifier for RZ/G2L
Here is an example of a MAX9867 on SSI channel 3, using I2C-3. MAX98390 Amplifier on I2C-2.
This is for the Linux-5.10 kernel. For the older Linux-4.19 kernel, there are some differences.
Pin Setup
&pinctrl {

	/* MAX98390 Amplifier */
	i2c2_pins: i2c2 {
		pinmux = <RZG2L_PORT_PINMUX(42, 3, 1)>, /* SDA */
			 <RZG2L_PORT_PINMUX(42, 4, 1)>; /* SCL */
	};

	/* MAX9867 Codec */
	i2c3_pins: i2c3 {
		pinmux = <RZG2L_PORT_PINMUX(1828, 01, 31)>, /* SDA */
			 <RZG2L_PORT_PINMUX(18, 1, 3)>; /* SCLET0_LINKSTA */
	};

	ssi3_pins: ssi3 {
	pinmux = <RZG2L_PORT_PINMUX(3127, 01, 51)>, /* BCKET0_MDC */
			 <RZG2L_PORT_PINMUX(3128, 10, 51)>, /* RCKET0_MDIO */
			 <RZG2L_PORT_PINMUX(3220, 0, 51)>, /* TXDET0_TXC */
			 <RZG2L_PORT_PINMUX(3220, 1, 51)>;, /* RXDET0_TX_CTL */
	};
};
Enable SSI channel
&ssi3 {
	pinctrl-0 = <&ssi3_pins>;
	pinctrl-names = "default";

	#sound-dai-cells = <1>;
	status = "okay";
};
Create a node for the MAX9867
	my_snd: sound {
		compatible = "simple-audio-card";
		simple-audio-card,widgets = "Speaker", "Ext Spk";

		simple-audio-card,routing =
		"Ext Spk", "BE_OUT";
		"Ext Spk", "LOUT",
		"Ext Spk", "ROUT";

		/* MAX98390 Amplifier */
		simple-audio-card,dai-link@0{
			format = "i2s";
			bitclock-master = <&cpu_dai3>;
			frame-master = <&cpu_dai3>;
			mclk-fs = <256>;
			cpu_dai3: cpu {
				sound-dai = <&ssi3>;
			};

			codec_dai3: codec {
				sound-dai = <&max98390>;
				clocks = <&mclk>;
			};
		};

		/* MAX9867 Codec */
		simple-audio-card,dai-link@1{
			format = "i2s";
			bitclock-master = <&cpu_dai0>;
			frame-master = <&cpu_dai0>;
			mclk-fs = <256>;
			cpu_dai0: cpu {
				sound-dai = <&ssi0>;
			};

			codec_dai0: codec {
				sound-dai = <&max9867>;
				clocks = <&mclk>;
			};
		};
	};
I2C node for the Codec and Amp&i2c2 {
	pinctrl-0 = <&i2c2_pins>;
	pinctrl-names = "default";

	status = "okay";
	clock-frequency = <400000>;

	/* MAX98390 Amplifier */
	max98390: codec@3d {
		status = "okay";
		compatible = "maxim,max98390";
		#sound-dai-cells = <0>;
		reg = <0x3d>;
	};
};

&i2c3 {
	pinctrl-0 = <&i2c3_pins>;
	pinctrl-names = "default";

	status = "okay";
	clock-frequency = <400000>;

	/* MAX9867 Codec */
	max9867: codec@18 {
		status = "okay";
		compatible = "maxim,max9867";
		#sound-dai-cells = <0>;
		reg = <0x18>;
	};
};
Camera
Linux Drivers
RZ/G2H, G2M, G2N, G2E:CONFIG_xxx=y
RZ/G2L, G2LC, G2UL, V2L:CONFIG_xxx=y
Notes
Device Tree Examples
(see device tree for evaluation board)
Ethernet
 
Linux Drivers
RZ/G2H, G2M, G2N, G2E, G2L, G2LC, G2UL, V2L:rz_linux-cip/drivers/net/ethernet/renesas/ (ravb_main.c, ravb_ptp.c)
Documentation/devicetree/bindings/net/renesas,etheravb.yaml
CONFIG_NET_VENDOR_RENESAS=y
# CONFIG_SH_ETH is not set
CONFIG_RAVB=y
Notes
The Link Status input pin (LINKSTA) is not used. The driver instead relies on the PHY to inform it that the link is up by using in-band status messages on the RGMII lines.
Do not forget to set the correct voltage levels for the pins (3.3v, 1.5v, etc..) in the device tree in the pinctrl node.You use the syntax "power-source = <3300>;" when you declare the pins for Ethernet.
Refer to the pinctrl documentation in the kernel for more info.
Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-pinctrl.yaml
Documentation/devicetree/bindings/pinctrl/renesas,pcf.yaml
In the Device Tree, the MDIO address is set by @x and the "reg =<x>;" For example, MDIO address of 0:
	phy0: ethernet-phy@0 {
		reg = <0>;
Device Tree Examples
...
title Example of enabling MII mode for RZ/G2L
Ethernet node for MII mode
&eth0 {
	pinctrl-0 = <&eth0_mii_pins>;
	pinctrl-names = "default";
	phy-handle = <&phy0>;
	phy-mode = "mii";
	status = "okay";

	phy0: ethernet-phy@7 {
		compatible = "ethernet-phy-id0022.1640",
			     "ethernet-phy-ieee802.3-c22";
		reg = <7>;
		rxc-skew-psec = <2400>;
		txc-skew-psec = <2400>;
		rxdv-skew-psec = <0>;
		txdv-skew-psec = <0>;
		rxd0-skew-psec = <0>;
		rxd1-skew-psec = <0>;
		rxd2-skew-psec = <0>;
		rxd3-skew-psec = <0>;
		txd0-skew-psec = <0>;
		txd1-skew-psec = <0>;
		txd2-skew-psec = <0>;
		txd3-skew-psec = <0>;

		interrupt-parent = <&pinctrl>;
		interrupts = <RZG2L_GPIO(1, 0) IRQ_TYPE_LEVEL_LOW>;
	};
};

&eth1 {
	pinctrl-0 = <&eth1_mii_pins>;
	pinctrl-names = "default";
	phy-handle = <&phy1>;
	phy-mode = "mii";
	status = "okay";

	phy1: ethernet-phy@7 {
		compatible = "ethernet-phy-id0022.1640",
			     "ethernet-phy-ieee802.3-c22";
		reg = <7>;
		rxc-skew-psec = <2400>;
		txc-skew-psec = <2400>;
		rxdv-skew-psec = <0>;
		txdv-skew-psec = <0>;
		rxd0-skew-psec = <0>;
		rxd1-skew-psec = <0>;
		rxd2-skew-psec = <0>;
		rxd3-skew-psec = <0>;
		txd0-skew-psec = <0>;
		txd1-skew-psec = <0>;
		txd2-skew-psec = <0>;
		txd3-skew-psec = <0>;

		interrupt-parent = <&pinctrl>;
		interrupts = <RZG2L_GPIO(1, 1) IRQ_TYPE_LEVEL_LOW>;
	};
};
...
			 <RZG2L_PORT_PINMUX(20, 2, 1)>, /* ET0_TXD0 */
			 <RZG2L_PORT_PINMUX(21, 0, 1)>, /* ET0_TXD1 */
			 <RZG2L_PORT_PINMUX(21, 1, 1)>, /* ET0_TXD2 */
			 <RZG2L_PORT_PINMUX(22, 0, 1)>, /* ET0_TXD3 */
			 <RZG2L_PORT_PINMUX(22, 1, 1)>,	/* ETH0_TX_ERR */
			 <RZG2L_PORT_PINMUX(23, 0, 1)>,	/* ETH0_TX_COL */
			 <RZG2L_PORT_PINMUX(23, 1, 1)>, /* ETH0_TX_CRS */
			 <RZG2L_PORT_PINMUX(24, 0, 1)>, /* ET0_RXC */
			 <RZG2L_PORT_PINMUX(24, 1, 1)>, /* ET0_RX_CTL */
			 <RZG2L_PORT_PINMUX(25, 0, 1)>, /* ET0_RXD0 */
			 <RZG2L_PORT_PINMUX(25, 1, 1)>, /* ET0_RXD1 */
			 <RZG2L_PORT_PINMUX(26, 0, 1)>, /* ET0_RXD2 */
			 <RZG2L_PORT_PINMUX(26, 1, 1)>, /* ET0_RXD3 */
			 <RZG2L_PORT_PINMUX(27, 0, 1)>; /* ETH0_RX_ERR */
	};

	eth1_mii_pins: eth1 {
		pinmux = <RZG2L_PORT_PINMUX(37, 2, 1)>, /* ET1_LINKSTA */
			 <RZG2L_PORT_PINMUX(37, 0, 1)>, /* ET1_MDC */
			 <RZG2L_PORT_PINMUX(37, 1, 1)>, /* ET1_MDIO */
			 <RZG2L_PORT_PINMUX(29, 0, 1)>, /* ET1_TXC */
			 <RZG2L_PORT_PINMUX(29, 1, 1)>, /* ET1_TX_CTL */
			 <RZG2L_PORT_PINMUX(30, 0, 1)>, /* ET1_TXD0 */
			 <RZG2L_PORT_PINMUX(30, 1, 1)>, /* ET1_TXD1 */
			 <RZG2L_PORT_PINMUX(31, 0, 1)>, /* ET1_TXD2 */
			 <RZG2L_PORT_PINMUX(31, 1, 1)>, /* ET1_TXD3 */
			 <RZG2L_PORT_PINMUX(32, 0, 1)>, /* ETH1_TX_ERR */
			 <RZG2L_PORT_PINMUX(32, 1, 1)>, /* ETH1_TX_COL */
			 <RZG2L_PORT_PINMUX(33, 0, 1)>, /* ETH1_TX_CRS */
			 <RZG2L_PORT_PINMUX(33, 1, 1)>, /* ET1_RXC */
			 <RZG2L_PORT_PINMUX(34, 0, 1)>, /* ET1_RX_CTL */
			 <RZG2L_PORT_PINMUX(34, 1, 1)>, /* ET1_RXD0 */
			 <RZG2L_PORT_PINMUX(35, 0, 1)>, /* ET1_RXD1 */
			 <RZG2L_PORT_PINMUX(35, 1, 1)>, /* ET1_RXD2 */
			 <RZG2L_PORT_PINMUX(36, 0, 1)>, /* ET1_RXD3 */
			 <RZG2L_PORT_PINMUX(36, 1, 1)>; /* ETH1_RX_ERR */
	};
};  
PCIe
Linux Drivers
RZ/G2, RZ/G3
Host:
drivers/pci/controller/pcie-rcar.c
drivers/pci/controller/pcie-rcar.h
drivers/pci/controller/pcie-rcar-host.c
Documentation/devicetree/bindings/pci/rcar-pci.txt
CONFIG_PCIE_RCAR_HOST=y
End Point:
drivers/pci/controller/pcie-rcar.c
drivers/pci/controller/pcie-rcar.h
drivers/pci/controller/pcie-rcar-ep.c
Documentation/devicetree/bindings/pci/rcar-pci-ep.yaml
CONFIG_PCIE_RCAR_EP=y

Notes
PCIe testing using SSD:
Enable Kernel configuration:
         PCIe was enabled by default in the RZ/G2 BSP. But you need to modify the kernel menuconfig to add support for NVME M.2 SDD.
         Example to modify kernel in yocto is:
$ bitbake -c menuconfig virtual/kernel
Once menuconfig appears, enable device driver for nvme support and save the changes.
Then build the kernel with new configuration.
$ bitbake linux-renesas -fc compile
$ bitbake linux-renesas -fc install
$ bitbake linux-renesas -fc deploy
       Once the built is done, update your kernel and device tree with newly built.
    2. Connect the SSD adapter board to RZ/G2H PCIe slot and check PCIe:
$ root@hihope-rzg2h:~# lspci
00:00.0 PCI bridge: Renesas Technology Corp. Device 0025
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
$ root@hihope-rzg2h:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0  29.7G  0 disk
`-mmcblk0p1  179:1    0  29.7G  0 part
mmcblk0boot0 179:8    0  31.5M  1 disk
mmcblk0boot1 179:16   0  31.5M  1 disk
mmcblk1      179:24   0  14.9G  0 disk
|-mmcblk1p1  179:25   0   512M  0 part
`-mmcblk1p2  179:26   0   1.8G  0 part /
nvme0n1      259:0    0 238.5G  0 disk   # recognized the NVME SSD
    3. Create a partition on the nvme to use
$ root@hihope-rzg2h:~# fdisk /dev/nvme0n1
Choose "n" to create a new partition
Choose "P" then "1" to create a new primary partition
Use defaults for the sector numbers
Then "w" to write the data to the disk
    After partition, "lsblk" command shows this:
$ root@hihope-rzg2h:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0  29.7G  0 disk
`-mmcblk0p1  179:1    0  29.7G  0 part
mmcblk0boot0 179:8    0  31.5M  1 disk
mmcblk0boot1 179:16   0  31.5M  1 disk
mmcblk1      179:24   0  14.9G  0 disk
|-mmcblk1p1  179:25   0   512M  0 part
`-mmcblk1p2  179:26   0   1.8G  0 part /
nvme0n1      259:0    0 238.5G  0 disk
`-nvme0n1p1  259:1    0 238.5G  0 part   # new partition
    4. Create the filesystem:
$ root@hihope-rzg2h:~# mkfs -t ext4 /dev/nvme0n1p1
   5. Create mount point:
$ root@hihope-rzg2h:~# mkdir /mnt/nvme
root@hihope-rzg2h:~# mount /dev/nvme0n1p1 /mnt/nvme
[  970.462102] EXT4-fs (nvme0n1p1): recovery complete
[  970.468717] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
   6. Create file to write/read:
$ root@hihope-rzg2h:~# touch /mnt/nvme/testfile
   7. Example for PCIe performance measured on PCIe Slot port of RZ/G2H, and with a Samsung NVMe SSD PM981a:
root@hihope-rzg2h:~# echo 3 > /proc/sys/vm/drop_caches  # to drop both page cache and dentries/inodes
[  498.378440] sh (620): drop_caches: 3
root@hihope-rzg2h:~# dd if=/dev/zero of=/mnt/nvme/testfile bs=200M count=50 oflag=direct
50+0 records in
50+0 records out
10485760000 bytes (10 GB, 9.8 GiB) copied, 29.009 s, 361 MB/s
root@hihope-rzg2h:~# echo 3 > /proc/sys/vm/drop_caches
[  616.062183] sh (620): drop_caches: 3
root@hihope-rzg2h:~# dd if=/mnt/nvme/testfile of=/dev/null bs=200M  count=50 iflag=direct
50+0 records in
50+0 records out
10485760000 bytes (10 GB, 9.8 GiB) copied, 24.6171 s, 426 MB/s
USB
Linux Drivers
RZ/G2H, G2M, G2N, G2E:
RZ/G2L, G2LC, G2UL, V2L:
...
If you did not connect the USB_OVCUR pin on your board, and it floats, you will get interrupt messages about over current. However, you can disable this interrupt by modifying the setting for the OHCI HcRhDescriptorA OHCI HcRhDescriptorA Register and setting bit NOCP to bit NOCP to '1'. Search for "HcRhDescriptorA" in the hardware manual for more information.
In the kernelthe kernel, in file driversfile drivers/usb/host/ohci-hcd.c, you want to comment out the to comment out the line:
/* Configure for per-port over-current protection by default */
val &= ~RH_A_NOCP;
In u-boot, can see this is sometimes done for Renesas boards. See file boardfile board/renesas/rzg2l-dev/rzg2l-dev.c
(*(volatile u32 *)(USB1_BASE + HcRhDescriptorA)) |= (0x1u << 12); /* NOCP = 1 */

Dynamic changing from Device and Host for OTG:
If you are using a device as OTG (On-the-Go) and want to change from device to you, you set a sysfs setting under the PHY driver (not the USB controller driver)
$ echo host > /sys/devices/platform/soc/ee080200.usb-phy/role


Device Tree Examples
(see device tree for evaluation board)
...
 Expand
title RZ/G2L SMARC Device Tree Example
/ {
	reg_3p3v: regulator1 {
		compatible = "regulator-fixed";

		regulator-name = "fixed-3.3V";
		regulator-min-microvolt = <3300000>;
		regulator-max-microvolt = <3300000>;
		regulator-boot-on;
		regulator-always-on;
	};

	vccq_sdhi1: regulator-vccq-sdhi1 {
		compatible = "regulator-gpio";
		regulator-name = "SDHI1 VccQ";
		regulator-min-microvolt = <1800000>;
		regulator-max-microvolt = <3300000>;
		gpios-states = <1>;
		states = <3300000 1>, <1800000 0>;
	};
};

&sdhi1 {
	pinctrl-0 = <&sdhi1_pins>;
	pinctrl-1 = <&sdhi1_pins_uhs>;
	pinctrl-names = "default", "state_uhs";

	vmmc-supply = <&reg_3p3v>;
	vqmmc-supply = <&vccq_sdhi1>;
	bus-width = <4>;
	sd-uhs-sdr50;
	sd-uhs-sdr104;
	status = "okay";
};

eMMC
Linux Drivers
RZ/G2H, G2M, G2N, G2E:
RZ/G2L, G2LC, G2UL, V2L:driver/mmc/host/renesas_sdhi.h
driver/mmc/host/renesas_sdhi_core.c
driver/mmc/host/renesas_sdhi_internal_dmac.c
driver/mmc/host/tmio_mmc.h
driver/mmc/host/tmio_mmc_core.c
CONFIG_MMC_SDHI=y
CONFIG_MMC_SDHI_INTERNAL_DMAC=y (selected automatically by MMC_SDHI)
CONFIG_MMC_TMIO_CORE=y (selected automatically by MMC_SDHI)
...
Given the Device Tree example below for SPI-1, you will need to determine the values for the "tx" and "rx" DMA triggers.
 HTML
<pre>
&spi1 { 
      pinctrl-0 = <&spi1_pins>;
      pinctrl-names = "default";
      dmas = <&dmac <span><font color=red> 0x2e99 
...
</font></span>>, <&dmac <span><font color=red> 0x2e9a
...
 </font></span>>;
      dma-names = "tx", "rx";
      status = "okay";
};
</pre>

You can find some explanation in the kernel documentation: Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml
...
These values are what get written directly to the DMA registers. Also, the values for these bits are fixed and shown in a table in the hardware manual.
If you look in the Direct Memory Access Control (DMA) chapter in the hardware manual, you will find the table "On-Chip Module Requests"
Example: RZ/G2L RSPI ch1
Image RemovedImage Added


SPIT1 (tranmit buffer empty) dma-names = "tx"
...
Linux Drivers
RZ/G2H, G2M, G2N, G2E:compatible = "renesas,rcar-gen3-i2c"drivers/i2c/busses/i2c-rcar.c
CONFIG_I2C_RCAR=y
compatible = "renesas,rcar-gen3-iic" (I2C for PMIC)drivers/i2c/busses/i2c-sh_mobile.c
CONFIG_I2C_SH_
xxxMOBILE=y
RZ/G2L, G2LC, G2UL, V2L:drivers/i2c/busses/ i2c-riic.c
CONFIG_I2C_RIIC=y
...
, G2UL, V2L:drivers/i2c/busses/i2c-riic.c
CONFIG_I2C_RIIC=y
Notes
The frequency for the driver i2c-rcar.c is hard coded to 100kHz. If you want to change it, you have to modify function rcar_i2c_clock_calculate( )
Device Tree Examples
(see device tree for evaluation board)
...
spidev:If you want a generic SPI device (/dev/spi-0), in the past you would allocate a compatible = "spidev"; node. Unfortunately, that spidev name has been removed from Linux (since Linux-5.17). However, you can still create a spidev device by simply using another name that is already in the kernel. The compatible name will be different, but it will work the exact same way.
Below is the list of device that can be used with spidev from file drivers/spi/spidev.c
static const struct of_device_id spidev_dt_ids[] = {
    { .compatible = "rohm,dh2228fv" },
    { .compatible = "lineartechnology,ltc2488" },
    { .compatible = "ge,achc" },
    { .compatible = "semtech,sx1301" },
    { .compatible = "lwn,bk4" },
    { .compatible = "dh,dhcom-board" },
    { .compatible = "menlo,m53cpld" },
    {},
};
For example, if you just pick the first name in the list ("rohm,dh2228fv") this will work on any kernel version:
&spi1 {
	pinctrl-0 = <&spi1_pins>;
	pinctrl-names = "default";
	status = "okay";
	dmas = <&dmac 0x2e99>,
	       <&dmac 0x2e9a>;
	dma-names = "tx", "rx";

    spidev@0{
        compatible = "rohm,dh2228fv"; // (Using fake name to use spidev driver)
        reg = <0>;
        spi-max-frequency = <1000000>;
    };
};
Device Tree Examples
(see device tree for evaluation board)
...
RZ/G2H, G2M, G2N, G2E:CONFIG_PWM_RZ_xxxMTU3=y
drivers/pwm/pwm-rz-mtu3.c
RZ/G2L, G2LC, G2UL, V2L:CONFIG_GPT_xxxRZG2L=y
drivers/pwm/gpt-rzg2l.c
Notes
Device Tree Examples
...
RZ/G2H, G2M, G2N, G2E:drivers/thermal/rcar_gen3__thermal.c
CONFIG_RCAR_GEN3_THERMAL=y
RZ/G2L, G2LC, G2UL, V2L:drivers/thermal/rzg2l_thermal.c
CONFIG_RZG2L_THERMAL=y
RZ/V2HSupported on AI_SDK 5.0 and later
Enabled by default
CONFIG_RZG2L_THERMAL=y
Notes
...
PMIC RAA215300
Linux Drivers
drivers/mfd/raa215300.c
CONFIG_PMIC_RAA215300=y
Documentation/devicetree/bindings/mfd/raa215300.txt
Notes
Only supports RTC function
Added in VLP/G v3.0.1 release (branch rz-5.10-cip13)
...

Navigation

Page tree

Versions Compared

Old Version 7

New Version Current

Key

RZ Evaluation Board Files

RZ Evaluation Board Files

IRQ0-7

IRQ0-7

Display

Display

Audio

Camera

Ethernet

Ethernet

PCIe

USB

eMMC

PMIC RAA215300

Navigation

Page tree

Page History

Versions Compared

Old Version 7

New Version Current

Key

RZ Evaluation Board Files

RZ Evaluation Board Files

IRQ0-7

IRQ0-7

Display

Display

Audio

Camera

Ethernet

Ethernet

PCIe

USB

eMMC

PMIC RAA215300