- 12 Jun, 2017 8 commits
-
-
Geert Uytterhoeven authored
The Renesas Salvator-XS (Salvator-X 2nd version) development board can be equipped with either an R-Car H3 ES2.0 or M3-W ES1.x SiP, which are pin-compatible. Add initial support for the common parts of the Salvator-XS board into its own .dtsi file, to be included by the DTSes for the H3/M3-W versions. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by:
Simon Horman <horms+renesas@verge.net.au>
-
Geert Uytterhoeven authored
The Renesas Salvator-X and Salvator-XS (Salvator-X 2nd version) boards are very similar. To avoid duplication, prepare for the advent of the latter by extracting the common board parts into its own .dtsi file. Signed-off-by:
-
Geert Uytterhoeven authored
R-Car Gen3 SoCs contain multiple PWM modules. Hence to avoid conflicts, pinctrl subnodes for PWM should include indices referring to their instances. Fixes: b33be336 ("arm64: dts: salvator-x: Add panel backlight support") Signed-off-by:
-
Geert Uytterhoeven authored
Split off support for H3ULCB boards with the ES1.x revision of the R-Car H3 SoC into a separate file. The main r8a7795-h3ulcb.dts file now corresponds to H3ULCB with R-Car H3 ES2.0 or later. Signed-off-by:
-
Wolfram Sang authored
Tested with a Salvator-X. Signed-off-by:
Wolfram Sang <wsa+renesas@sang-engineering.com> Reviewed-by:
-
Wolfram Sang authored
Tested with a Salvator-X. Signed-off-by:
-
Kuninori Morimoto authored
Current rcar_sound only has 11289600 (= for 44.1kHz) clock-frequency, but it needs 12288000 for 48kHz too. Otherwise, 48kHz based sound can't handle correctly. Signed-off-by:
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by:
-
Kuninori Morimoto authored
Current rcar_sound only has 11289600 (= for 44.1kHz) clock-frequency, but it needs 12288000 for 48kHz too. Otherwise, 48kHz based sound can't handle correctly. Signed-off-by:
-
- 22 May, 2017 32 commits
-
-
Geert Uytterhoeven authored
Split off support for Salvator-X boards with the ES1.x revision of the R-Car H3 SoC into a separate file. The main r8a7795-salvator-x.dts file now corresponds to Salvator-X with R-Car H3 ES2.0 or later. Signed-off-by:
-
Geert Uytterhoeven authored
Update r8a7795.dtsi so it corresponds to R-Car H3 ES2.0 or later: - The following devices no longer exist on ES2.0, and are thus removed: fcpf2, fcpvd3, fcpvi2, fdp1-2, usb3-if1, vspd3, vspi2. - The DU <-> VSPD topology is different on ES2.0, hence remove the "compatible" and "vsps" properties from the DU node until the driver can handle this. Move support for the ES1.x revision of the R-Car H3 SoC into a separate file. To avoid duplication, r8a7795-es1.dtsi includes r8a7795.dtsi, and adds device nodes and properties where needed. Note that while currently r8a7795-es1.dtsi only adds device nodes, removal of devices nodes and properties can be implemented using the /delete-node/ and /delete-property/ keywords, as shown below: &soc { /delete-node/ <name>@<addr>; }; &<label> { /delete-property/ <prop>; }; Switch r8a7795-salvator-x.dts and r8a7795-h3ulcb.dts from r8a7795.dtsi to r8a7795-es1.dtsi to preserve compatibility. Signed-off-by: -
Simon Horman authored
The EthernetAVB should not depend on the bootloader to setup correct drive-strength values. Values for drive-strength where found by examining the registers after the bootloader has configured the registers and successfully used the EthernetAVB. Based on: * commit 7d73a4da ("arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins") * commit 4903987033be ("arm64: dts: r8a7796: salvator-x: Set drive-strength for ravb pins") Cc: Geert Uytterhoeven <geert+renesas@glider.be> Cc: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se> Signed-off-by:
-
Koji Matsuoka authored
Enable the HDMI encoders for the H3 Salvator-X board. The number of encoders varies between the H3 and M3-W SoCs, so they can't be enabled in the common salvator-x.dtsi file. Signed-off-by:
Koji Matsuoka <koji.matsuoka.xm@renesas.com> Signed-off-by:
Ulrich Hecht <ulrich.hecht+renesas@gmail.com> Signed-off-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Reviewed-by:
-
Laurent Pinchart authored
The DU1 and DU2 external dot clocks are provided by the fixed frequency clock generators X21 and X22, while the DU0 and DU3 clocks are provided by the programmable Versaclock5 clock generator. Signed-off-by:
-
Laurent Pinchart authored
The Salvator-X board has two HDMI output connectors. Add them to the common salvator-x.dtsi. Signed-off-by:
-
Laurent Pinchart authored
The DU1 and DU2 external dot clocks are fixed frequency clock generators running at 33MHz, while the DU0 and DU3 external dot clocks are generated by an I2C-controlled programmable clock generator. All those clock generators are available on both the H3 and M3-W Salvator-X boards. Add them to the salvator-x.dtsi file. Signed-off-by:
-
Ulrich Hecht authored
Add DT nodes for the two HDMI encoders in disabled state. Based on work by Koji Matsuoka. Signed-off-by:
-
Laurent Pinchart authored
The panel backlight is controlled through a GPIO and a PWM channel. Signed-off-by:
-
Takeshi Kihara authored
This patch adds PWM{0,1,2,3,4,5,6} device nodes for R8A7796 SoC. Signed-off-by:Takeshi Kihara <takeshi.kihara.df@renesas.com> [uli: added resets, shortened reg lengths to 8] Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Kuninori Morimoto authored
Signed-off-by:
-
Jacopo Mondi authored
Add device nodes for two Maxim max961x current sense amplifiers sensing VDD_08 and DVFS_08 lines. Signed-off-by:
Jacopo Mondi <jacopo+renesas@jmondi.org> [geert: r8a7796-salvator-x.dts => salvator-x.dtsi] Signed-off-by:
-
Geert Uytterhoeven authored
The Renesas ULCB development board can be equipped with either an R-Car H3 or M3-W SiP, which are pin-compatible. Both boards use different DTBs. Reduce duplication by extracting common ULCB board support into its own .dtsi file. References to SoC-specific clocks are handled through cpp definitions. Sort device nodes while at it. For H3ULCB, there are no functional changes. For M3ULCB, the following new devices are now described in DT: - External audio, CAN, and PCIe clocks, - CS2000 clock generator, - AK4613 Audio Codec. Signed-off-by:
-
Geert Uytterhoeven authored
The Renesas Salvator-X development board can be equipped with either an R-Car H3 or M3-W SiP, which are pin-compatible. Both boards use different DTBs. Reduce duplication by extracting common Salvator-X board support into its own .dtsi file. References to SoC-specific clocks are handled through cpp definitions. Sort device nodes while at it. For boards with an R-Car H3 SiP, there are no functional changes. For boards with an R-Car M3-W SiP, the following new devices are now described in DT: - External audio, CAN, and PCIe clocks, - USB Vbus regulator, - CS2000 clock generator, - AK4613 Audio Codec, - VGA. Signed-off-by:
-
Geert Uytterhoeven authored
Add empty device nodes serving as placeholders for devices that are not yet supported and/or tested on R-Car M3-W, but are supported and used on Salvator-X or H3ULCB boards equipped with an R-Car H3 SoC. Signed-off-by:
-
Geert Uytterhoeven authored
Add the external PCIe bus clock as a zero Hz fixed-frequency clock. Boards that provide this clock should override it. Based on r8a7795.dtsi. Signed-off-by:
-
Geert Uytterhoeven authored
Add the external audio clocks as zero Hz fixed-frequency clocks. Boards that provide these clocks should override them. Based on commit 623197b9 ("arm64: renesas: r8a7795: Sound SSI PIO support"). Signed-off-by:
-
Simon Horman authored
The device trees for Renesas SoCs use either pfc or pin-controller as the node name for the PFC device. This patch is intended to take a step towards unifying the node name used as pin-controller which appears to be the more generic of the two and thus more in keeping with the DT specs. My analysis is that this is a user-visible change to the extent that kernel logs, and sysfs entries change from e6060000.pfc and pfc@e6060000 to e6060000.pin-controller and pin-controller@e6060000. Signed-off-by:
-
Geert Uytterhoeven authored
The EthernetAVB should not depend on the bootloader to setup correct drive-strength values. Values for drive-strength where found by examining the registers after the bootloader has configured the registers and successfully used the EthernetAVB. Based on commit 7d73a4da ("arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins"). Signed-off-by:
-
Geert Uytterhoeven authored
Cfr. commit b2407c56 ("arm64: dts: r8a7795: enable nfs root on Salvator-X board"). Signed-off-by:
-
Simon Horman authored
Set PHY rxc-skew-ps to 1500 and all other values to their default values. This is intended to to address failures in the case of 1Gbps communication using the salvator-x board with the KSZ9031RNX phy. This has been reported to occur with both the r8a7795 (H3) and r8a7796 (M3-W) SoCs. Based in a similar patch for the r8a7796 salvator-x by Kazuya Mizuguchi. Signed-off-by: -
Vladimir Barinov authored
This supports HS200 mode for eMMC on H3ULCB board Signed-off-by:
Vladimir Barinov <vladimir.barinov+renesas@cogentembedded.com> Reviewed-by:
-
Vladimir Barinov authored
This supports HS200 mode for eMMC on M3ULCB board Signed-off-by:
-
Wolfram Sang authored
Signed-off-by:
-
Wolfram Sang authored
Signed-off-by:
-
Takeshi Kihara authored
This patch addes memory region: - After changes, the Salvator-X board has the following map: Bank0: 1GiB RAM : 0x000048000000 -> 0x0007fffffff Bank1: 1GiB RAM : 0x000500000000 -> 0x0053fffffff Bank2: 1GiB RAM : 0x000600000000 -> 0x0063fffffff Bank3: 1GiB RAM : 0x000700000000 -> 0x0073fffffff - Before changes, the old map looked like this: Bank0: 1GiB RAM : 0x000048000000 -> 0x0007fffffff Signed-off-by:
-
