This page contains helpful notes about Device Tree configurations and Device Driver details
RZ Evaluation Board Files
- 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.
If you to see a list of which peripheral nodes are set in each file, you can use this "dts_parser" tool below. For example, you want to find all the the .dtsi files that configure the i2c channels because you are looking for examples.
Device Tree Syntax
Print a Compiled DTB Output File
- When compiling a .dts file into a binary .dtb file, many include files might be combined.
- Some include files might contain nodes overwrite other nodes.
- You might not know what the final Device Tree looks like after all the includes and nodes overwrites.
- You can install the device-tree-compiler package to show the contents of a .dtb file
$ sudo apt-get install device-tree-compiler
- Below is an example command to print a .dtb file
$ dtc -I dtb -O dts -o - r8a774a3-hihope-rzg2m-ex.dtb
Top Level (root node)
Compatible for the SoC
- The .dtsi file for each SoC will have a "compatible" string to specify that SoC it is. If you decide to make your own top level compatible, make sure you include the original SoC string. The reason is that some drivers (the VSP driver for example) look for that SoC string to know what SoC they are running on. If it is missing, it will not load or run correctly.
Here is a correct example of a .dts file for a RZ/G2L board. Notice how "renesas,r9a07g044" is at the end of the line.
/ {
model = "My Really Cool RZ/G2L Board";
compatible = "my-rzg2l-board" , "renesas,r9a07g044";
chosen {
bootargs = "ignore_loglevel rw root=/dev/mmc0blk1";
stdout-path = "serial0:115200n8";
};
};
Clocks and Resets (CPG)
- System clocks, PLL setup, Dividers, Individual Peripheral Reset etc...
- CPG = Clock Pulse Generator
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- RZ/G2L, G2LC, G2UL, V2L:
- drivers/clk/renesas/*
- CONFIG_CLK_RENESAS=y
- (drivers for individual devices are auto selected by Kconfig)
Notes
- You generally do not have to do anything with these nodes or drivers. They are just listed here for reference.
Pin Control (pin mux)
Linux Drivers
- 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:
- drivers/pinctrl/renesas/pinctrl-rzg2l.c
- CONFIG_PINCTRL_RZG2L=y
- Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-pinctrl.yaml
Notes
- 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
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;
NMI {
label = "NMI Key WAKEUP";
linux,code = <143>;
wakeup-source;
interrupt-parent = <&intc_ex>;
interrupts = <8 IRQ_TYPE_EDGE_FALLING>;
debounce-interval = <50>;
};
};
&intc_ex {
status = "okay";
};
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
- drivers/gpu/drm/rcar-du/*
- 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 (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.
- 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 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.
Device Tree Examples:
- RZ/G2L: MIPI-CSI to HDMI Bridge: See device tree for evaluation board.
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
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
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:
Host
- (uses standard EHCI and XHCI kernel drivers since H/W API is fixed)
- drivers/usb/host/ehci-hcd.c
- drivers/usb/host/ehci-platform.c
- drivers/usb/host/xhci.c
- drivers/usb/host/xhci-rcar.c
- CONFIG_USB_EHCI_HCD=y
- CONFIG_XHCI_PLATFORM=y
- CONFIG_XHCI_RCAR=y
Device
- drivers/usb/renesas_usbhs/*
- USB_RENESAS_USBHS=y
PHY
- The PHY is a separate H/W block. Also used to control host/device switching for OTG.
- drivers/phy/renesas/*
- CONFIG_PHY_RCAR_GEN3_USB2=y
- CONFIG_PHY_RCAR_GEN3_USB3=y
Notes
- Disable OverCurrent Protection Interrupts:
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 Register and setting bit NOCP to '1'. Search for "HcRhDescriptorA" in the hardware manual for more information.
In the kernel, in file drivers/usb/host/ohci-hcd.c, you want 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 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)
SD Card
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- CONFIG_xxx=y
- RZ/G2L, G2LC, G2UL, V2L:
- CONFIG_xxx=y
Notes
- Same as eMMC: The drivers for SD Card and SDIO are the same as eMMC. Please the section on eMMC.
- 3.3v Only: If you only provide 3.3v (do not support dynamically switching to 1.8v for UHS), then you should add the no-1-8-v; flag to the sdhi node. This flag is used for both kernel and u-boot device trees.
- vmmc-supply: This is the voltage regulator connected to the SD card VDD pin. It could be a constant fixed 3.3v, or it be attached to a regulator that you can turn off to save power.
- vqmmc-supply: This is the voltage regulator that the pull-ups for the data lines go to. For high speed SD, they will change from 3.3v to 1.8v.
Device Tree Examples
- (see device tree for evaluation board)
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)
Notes
- Combo driver for MMC + SDHI HW
- The core of the SDHI code is using the TMIO (Toshiba Mobile IO) driver because it is the same HW block and they have shared the same driver for many years.
- CONFIG_MMC_SDHI_SYS_DMAC=y is selected automatically by MMC_SDHI, but is only for RZ/G1 series devices.
- Note that if you are using more than one mmc/sdhi channel, you might run into the issue that you don't get the same device number (ie, /dev/mmcblk0) each time you boot. To fix this, simply add an 'alias' to the top of your Device Tree to make each channel a fixed number. As an example:
aliases {
mmc0 = &sdhi3; // eMMC Flash for rootfs
mmc1 = &sdhi0; // SD Card Socket
mmc2 = &sdhi2; // SDIO for WiFi
};
Device Tree Examples
- (see device tree for evaluation board)
DMA
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- drivers/dma/sh/*
- CONFIG_RCAR_DMAC=y
- RZ/G2L, G2LC, G2UL, V2L:
- drivers/dma/sh/rz-dma.c
- CONFIG_RZ_DMAC=y
Notes
RZ/G2L, RZ/V2L, How to determine 'dmas' value
- Given the Device Tree example below for SPI-1, you will need to determine the values for the "tx" and "rx" DMA triggers.
&spi1 {
pinctrl-0 = <&spi1_pins>;
pinctrl-names = "default";
dmas = <&dmac 0x2e99 >, <&dmac 0x2e9a >;
dma-names = "tx", "rx";
status = "okay";
};
- You can find some explanation in the kernel documentation: Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml
'#dma-cells':
const: 1
description:
The cell specifies the encoded MID/RID values of the DMAC port
connected to the DMA client and the slave channel configuration
parameters.
bits[0:9] - Specifies MID/RID value
bit[10] - Specifies DMA request high enable (HIEN)
bit[11] - Specifies DMA request detection type (LVL)
bits[12:14] - Specifies DMAACK output mode (AM)
bit[15] - Specifies Transfer Mode (TM)
- 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
SPIT1 (tranmit buffer empty) dma-names = "tx"
MID[7:0] = 10100110'b
RID[1:0] = 01'b
HEIN = 1'b
LVL = 1'b
AM[2:0] = 010'b
TM = 0'b
AM HEIN RID
| | |
0 010 1 1 10100110 01 = 0010 1110 1001 1001 = 0x2e99
| | |
TM LVL MID
SPIR1 (receive buffer full) dma-names = "rx"
MID[7:0] = 10100110'b
RID[1:0] = 10'b
HEIN = 1'b
LVL = 1'b
AM[2:0] = 010'b
TM = 0'b
AM HEIN RID
| | |
0 010 1 1 10100110 10 = 0010 1110 1001 1010 = 0x2e9a
| | |
TM LVL MID
Device Tree Examples
- (see device tree for evaluation board)
I2C
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_MOBILE=y
- compatible = "renesas,rcar-gen3-i2c"
- RZ/G2L, G2LC, 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)
SPI
Linux Drivers
- MSIOF: RZ/G2H, G2M, G2N, G2E:
- CONFIG_xxx=y
- RSPI: RZ/G2L, G2LC, G2UL, V2L:
- drivers/spi/spi-rspi.c
- CONFIG_SPI_RSPI=y
Notes
- 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)
QSPI Flash
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- drivers/spi/spi-rpc-if.c
- drivers/memory/renesas-rpc-if.c
- drivers/mtd/hyperbus/rpc-if.c
- CONFIG_SPI_RPCIF=y
- CONFIG_RENESAS_RPCIF=y
- CONFIG_RPCIF_HYPERBUS=y
- RZ/G2L, G2LC, G2UL, V2L:
- CONFIG_xxx=y
Notes
- unrecognized JEDEC id bytes: If when booting the kernel, you get a message like:
[ 2.328844] rpc-if-spi rpc-if-spi: registered master spi2 [ 2.328891] spi spi2.0: setup mode 0, 8 bits/w, 50000000 Hz max --> 0 [ 2.329230] spi-nor spi2.0: unrecognized JEDEC id bytes: 1f 87 01 1f 87 01
it means this nor flash is not supported in the Linux kernel. To support this flash, you should add this flash info in "static const struct flash_info atmel_parts[]" in drivers/mtd/spi-nor/atmel.c:
{ "at25sf321", INFO(0x1f8701, 0, 64 * 1024, 64, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
Device Tree Examples
- (see device tree for evaluation board)
UART (SCIF)
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)
UART (SCI)
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)
CAN
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- RZ/G2L, G2LC, G2UL, V2L:
- drivers/net/can/rcar/*
- CONFIG_CAN_RCAR=y
- CONFIG_CAN_RCAR_FD=y
Notes
- CAN-FD is enabled by default. To switch to CAN protocol, a user can add property "renesas,no-can-fd" in the Device Tree
Device Tree Examples
- (see device tree for evaluation board)
ADC
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)
Watchdog Timer(WDT)
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- rz_linux-cip/drivers/watchdog/renesas_wdt.c
- CONFIG_RENESAS_WDT
- RZ/G2L, G2LC, G2UL, V2L:
- rz_linux-cip/drivers/watchdog/rzg2l_wdt.c
- CONFIG_RENESAS_RZG2LWDT
Notes
- When rebooting the system, the watchdog timer is used. Simply type the command line "reboot" in the console.
- To test a watch dog timeout/reboot, enter this command in the console "cat >> /dev/watchdog", then press ENTER again, then wait 1 minutes, and the board should reboot.
- RZ/G2L: Reset on a WDT Timeout: There is a register in the CPG (WDT Reset Selector Register - CPG_WDTRST_SEL) to control if the WDT will reset the system or not. To generate a system RESET, you need to set it to 0x00010001. You can do this in u-boot, or when the kernel boots (in the CPG driver, not the WDT driver).
# Add this code to u-boot #define CPG_WDTRST_SEL (CPG_BASE + 0xB14) *(volatile u32 *)(CPG_WDTRST_SEL) = 0x00010001; - or - # Add this code to the kernel CPG driver # FILE: drivers/clk/renesas/rzg2l-cpg.c # FUNCTION: rzg2l_cpg_probe() # LINE: Before the 'return 0;' at the end of the funtion writel(0x00010001, (priv->base + 0xB14));
- RZ/G2L: Toggle WDTOVF_PERROUT# Note that by default, the WDTOVF_PERROUT# pin will not toggle on a WDT reboot. You need to set the CPG_WDTRST_SEL register manually in u-boot since Linux never touches that register. For example:
#define CPG_WDTRST_SEL (CPG_BASE + 0xB14) *(volatile u32 *)(CPG_WDTRST_SEL) = 0x00100010;
Device Tree Examples
- (see device tree for evaluation board)
PWM
Linux Drivers
- RZ/G2H, G2M, G2N, G2E:
- CONFIG_PWM_RZ_MTU3=y
- drivers/pwm/pwm-rz-mtu3.c
- RZ/G2L, G2LC, G2UL, V2L:
- CONFIG_GPT_RZG2L=y
- drivers/pwm/gpt-rzg2l.c
Notes
Device Tree Examples
- (see device tree for evaluation board)
Timer
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)
Thermal
Linux Drivers
- 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/V2H
- Supported on AI_SDK 5.0 and later
- Enabled by default
- CONFIG_RZG2L_THERMAL=y
Notes
- The Linux driver reads the registers and applies the formula in the hardware manual
- You can read the current value running the command:
- $ cat /sys/class/thermal/thermal_zone0/temp
- The output value is in millicelsius
Device Tree Examples
- (see device tree for evaluation board)
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)
Device Tree Examples
- (see device tree for evaluation board)
Overview
Content Tools
