* [PATCH 1/5] dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding
2019-11-20 11:39 [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki
@ 2019-11-20 11:39 ` Jagan Teki
2019-11-20 11:39 ` [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki
` (3 subsequent siblings)
4 siblings, 0 replies; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 11:39 UTC (permalink / raw)
To: Heiko Stuebner, Rob Herring, Mark Rutland
Cc: Manivannan Sadhasivam, Akash Gajjar, Tom Cubie, devicetree,
linux-arm-kernel, linux-rockchip, linux-kernel, linux-amarula,
Jagan Teki
VMARC RK3399Pro SOM is a standard SMARC SOM design with
Rockchip RK3399Pro SoC, which is designed by Vamrs.
Since it is a standard SMARC design, it can be easily
mounted on the supporting Carrier board. Radxa has
suitable carrier board to mount and use it as a final
version board.
Add dt-bindings for it.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index 45728fd22af8..51aa458833a9 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -526,4 +526,9 @@ properties:
items:
- const: tronsmart,orion-r68-meta
- const: rockchip,rk3368
+
+ - description: Vamrs VMARC RK3399Pro SOM
+ items:
+ - const: vamrs,rk3399pro-vmarc-som
+ - const: rockchip,rk3399pro
...
--
2.18.0.321.gffc6fa0e3
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support
2019-11-20 11:39 [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki
2019-11-20 11:39 ` [PATCH 1/5] dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding Jagan Teki
@ 2019-11-20 11:39 ` Jagan Teki
2019-11-20 13:28 ` Heiko Stübner
2019-11-20 11:39 ` [PATCH 3/5] dt-bindings: arm: rockchip: Add Rock Pi N10 binding Jagan Teki
` (2 subsequent siblings)
4 siblings, 1 reply; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 11:39 UTC (permalink / raw)
To: Heiko Stuebner, Rob Herring, Mark Rutland
Cc: Manivannan Sadhasivam, Akash Gajjar, Tom Cubie, devicetree,
linux-arm-kernel, linux-rockchip, linux-kernel, linux-amarula,
Jagan Teki
VMARC RK3399Pro SOM is a standard SMARC SOM design with
Rockchip RK3399Pro SoC, which is designed by Vamrs.
Specification:
- Rockchip RK3399Pro
- PMIC: RK809-3
- SD slot, 16GiB eMMC
- 2xUSB-2.0, 1xUSB3.0
- USB-C for power supply
- Ethernet, PCIe
- HDMI, MIPI-DSI/CSI, eDP
Add initial support for VMARC RK3399Pro SOM, this would use
with associated carrier board.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
.../dts/rockchip/rk3399pro-vmarc-som.dtsi | 339 ++++++++++++++++++
1 file changed, 339 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
diff --git a/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
new file mode 100644
index 000000000000..ddf6ebc9fbe3
--- /dev/null
+++ b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
@@ -0,0 +1,339 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
+ * Copyright (c) 2019 Vamrs Limited
+ * Copyright (c) 2019 Amarula Solutions(India)
+ */
+
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/pinctrl/rockchip.h>
+#include <dt-bindings/pwm/pwm.h>
+
+/ {
+ compatible = "vamrs,rk3399pro-vmarc-som", "rockchip,rk3399pro";
+
+ clkin_gmac: external-gmac-clock {
+ compatible = "fixed-clock";
+ clock-frequency = <125000000>;
+ clock-output-names = "clkin_gmac";
+ #clock-cells = <0>;
+ };
+
+ vcc5v0_sys: vcc5v0-sys-regulator {
+ compatible = "regulator-fixed";
+ regulator-name = "vcc5v0_sys";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ };
+
+ vcc_lan: vcc3v3-phy-regulator {
+ compatible = "regulator-fixed";
+ regulator-name = "vcc_lan";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+};
+
+&cpu_l0 {
+ cpu-supply = <&vdd_cpu_l>;
+};
+
+&cpu_l1 {
+ cpu-supply = <&vdd_cpu_l>;
+};
+
+&cpu_l2 {
+ cpu-supply = <&vdd_cpu_l>;
+};
+
+&cpu_l3 {
+ cpu-supply = <&vdd_cpu_l>;
+};
+
+&emmc_phy {
+ status = "okay";
+};
+
+&gmac {
+ assigned-clocks = <&cru SCLK_RMII_SRC>;
+ assigned-clock-parents = <&clkin_gmac>;
+ clock_in_out = "input";
+ phy-supply = <&vcc_lan>;
+ phy-mode = "rgmii";
+ pinctrl-names = "default";
+ pinctrl-0 = <&rgmii_pins>;
+ snps,reset-gpio = <&gpio3 RK_PB7 GPIO_ACTIVE_LOW>;
+ snps,reset-active-low;
+ snps,reset-delays-us = <0 10000 50000>;
+ tx_delay = <0x28>;
+ rx_delay = <0x11>;
+};
+
+&i2c0 {
+ clock-frequency = <400000>;
+ i2c-scl-rising-time-ns = <180>;
+ i2c-scl-falling-time-ns = <30>;
+ status = "okay";
+
+ rk809: pmic@20 {
+ compatible = "rockchip,rk809";
+ reg = <0x20>;
+ interrupt-parent = <&gpio1>;
+ interrupts = <RK_PC2 IRQ_TYPE_LEVEL_LOW>;
+ #clock-cells = <1>;
+ clock-output-names = "rk808-clkout1", "rk808-clkout2";
+ pinctrl-names = "default";
+ pinctrl-0 = <&pmic_int_l>;
+ rockchip,system-power-controller;
+ wakeup-source;
+
+ vcc1-supply = <&vcc5v0_sys>;
+ vcc2-supply = <&vcc5v0_sys>;
+ vcc3-supply = <&vcc5v0_sys>;
+ vcc4-supply = <&vcc5v0_sys>;
+ vcc5-supply = <&vcc_buck5>;
+ vcc6-supply = <&vcc_buck5>;
+ vcc7-supply = <&vcc5v0_sys>;
+ vcc8-supply = <&vcc3v3_sys>;
+ vcc9-supply = <&vcc5v0_sys>;
+
+ regulators {
+ vdd_log: DCDC_REG1 {
+ regulator-name = "vdd_log";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <750000>;
+ regulator-max-microvolt = <1350000>;
+ regulator-initial-mode = <0x2>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ regulator-suspend-microvolt = <900000>;
+ };
+ };
+
+ vdd_cpu_l: DCDC_REG2 {
+ regulator-name = "vdd_cpu_l";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <750000>;
+ regulator-max-microvolt = <1350000>;
+ regulator-ramp-delay = <6001>;
+ regulator-initial-mode = <0x2>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vcc_ddr: DCDC_REG3 {
+ regulator-name = "vcc_ddr";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-initial-mode = <0x2>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ };
+ };
+
+ vcc3v3_sys: DCDC_REG4 {
+ regulator-name = "vcc3v3_sys";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-initial-mode = <0x2>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ regulator-suspend-microvolt = <3300000>;
+ };
+ };
+
+ vcc_buck5: DCDC_REG5 {
+ regulator-name = "vcc_buck5";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <2200000>;
+ regulator-max-microvolt = <2200000>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ regulator-suspend-microvolt = <2200000>;
+ };
+ };
+
+ vcca_0v9: LDO_REG1 {
+ regulator-name = "vcca_0v9";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <900000>;
+ regulator-max-microvolt = <900000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vcc_1v8: LDO_REG2 {
+ regulator-name = "vcc_1v8";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ regulator-suspend-microvolt = <1800000>;
+ };
+ };
+
+ vcc_0v9: LDO_REG3 {
+ regulator-name = "vcc_0v9";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <900000>;
+ regulator-max-microvolt = <900000>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ regulator-suspend-microvolt = <900000>;
+ };
+ };
+
+ vcca_1v8: LDO_REG4 {
+ regulator-name = "vcca_1v8";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <1850000>;
+ regulator-max-microvolt = <1850000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ /*
+ * As per BSP, but schematic not showing any regulator
+ * pin for LD05.
+ */
+ vdd1v5_dvp: LDO_REG5 {
+ regulator-name = "vdd1v5_dvp";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <1500000>;
+ regulator-max-microvolt = <1500000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vcc_1v5: LDO_REG6 {
+ regulator-name = "vcc_1v5";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <1500000>;
+ regulator-max-microvolt = <1500000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vccio_3v0: LDO_REG7 {
+ regulator-name = "vccio_3v0";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <3000000>;
+ regulator-max-microvolt = <3000000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vccio_sd: LDO_REG8 {
+ regulator-name = "vccio_sd";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ /*
+ * As per BSP, but schematic not showing any regulator
+ * pin for LD09.
+ */
+ vcc_sd: LDO_REG9 {
+ regulator-name = "vcc_sd";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+
+ vcc5v0_usb2: SWITCH_REG1 {
+ regulator-name = "vcc5v0_usb2";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ regulator-state-mem {
+ regulator-on-in-suspend;
+ regulator-suspend-microvolt = <5000000>;
+ };
+ };
+
+ vccio_3v3: SWITCH_REG2 {
+ regulator-name = "vccio_3v3";
+ regulator-always-on;
+ regulator-boot-on;
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-state-mem {
+ regulator-off-in-suspend;
+ };
+ };
+ };
+ };
+};
+
+&io_domains {
+ status = "okay";
+ bt656-supply = <&vcca_1v8>;
+ sdmmc-supply = <&vccio_sd>;
+ gpio1830-supply = <&vccio_3v0>;
+};
+
+&pmu_io_domains {
+ status = "okay";
+ pmu1830-supply = <&vcc_1v8>;
+};
+
+&sdhci {
+ bus-width = <8>;
+ mmc-hs400-1_8v;
+ mmc-hs400-enhanced-strobe;
+ non-removable;
+ status = "okay";
+};
+
+&tsadc {
+ status = "okay";
+
+ /* tshut mode 0:CRU 1:GPIO */
+ rockchip,hw-tshut-mode = <1>;
+ /* tshut polarity 0:LOW 1:HIGH */
+ rockchip,hw-tshut-polarity = <1>;
+};
+
+&pinctrl {
+ pmic {
+ pmic_int_l: pmic-int-l {
+ rockchip,pins =
+ <1 RK_PC2 0 &pcfg_pull_up>;
+ };
+ };
+};
--
2.18.0.321.gffc6fa0e3
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support
2019-11-20 11:39 ` [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki
@ 2019-11-20 13:28 ` Heiko Stübner
2019-11-20 15:51 ` Jagan Teki
0 siblings, 1 reply; 12+ messages in thread
From: Heiko Stübner @ 2019-11-20 13:28 UTC (permalink / raw)
To: Jagan Teki
Cc: Rob Herring, Mark Rutland, Manivannan Sadhasivam, Akash Gajjar,
Tom Cubie, devicetree, linux-arm-kernel, linux-rockchip,
linux-kernel, linux-amarula
Hi Jagan,
looks good in general, just some small things below:
Am Mittwoch, 20. November 2019, 12:39:20 CET schrieb Jagan Teki:
> VMARC RK3399Pro SOM is a standard SMARC SOM design with
> Rockchip RK3399Pro SoC, which is designed by Vamrs.
>
> Specification:
> - Rockchip RK3399Pro
> - PMIC: RK809-3
> - SD slot, 16GiB eMMC
> - 2xUSB-2.0, 1xUSB3.0
> - USB-C for power supply
> - Ethernet, PCIe
> - HDMI, MIPI-DSI/CSI, eDP
>
> Add initial support for VMARC RK3399Pro SOM, this would use
> with associated carrier board.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> .../dts/rockchip/rk3399pro-vmarc-som.dtsi | 339 ++++++++++++++++++
> 1 file changed, 339 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
> new file mode 100644
> index 000000000000..ddf6ebc9fbe3
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
> @@ -0,0 +1,339 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
> + * Copyright (c) 2019 Vamrs Limited
> + * Copyright (c) 2019 Amarula Solutions(India)
> + */
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/pinctrl/rockchip.h>
> +#include <dt-bindings/pwm/pwm.h>
> +
> +/ {
> + compatible = "vamrs,rk3399pro-vmarc-som", "rockchip,rk3399pro";
> +
> + clkin_gmac: external-gmac-clock {
> + compatible = "fixed-clock";
> + clock-frequency = <125000000>;
> + clock-output-names = "clkin_gmac";
> + #clock-cells = <0>;
> + };
> +
> + vcc5v0_sys: vcc5v0-sys-regulator {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc5v0_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
Is vcc5v0_sys really the topmost regulator getting the outside
power-supply?
> + };
> +
> + vcc_lan: vcc3v3-phy-regulator {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc_lan";
vcc_lan / vcc_phy is mostly coming from the vendor bsp in some way
and will be named differently in schematics ... also it should be connected
to the regulator tree.
[...]
> +&tsadc {
> + status = "okay";
> +
> + /* tshut mode 0:CRU 1:GPIO */
I think we can live without the additional comments for properties :-)
> + rockchip,hw-tshut-mode = <1>;
> + /* tshut polarity 0:LOW 1:HIGH */
> + rockchip,hw-tshut-polarity = <1>;
> +};
Heiko
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support
2019-11-20 13:28 ` Heiko Stübner
@ 2019-11-20 15:51 ` Jagan Teki
0 siblings, 0 replies; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 15:51 UTC (permalink / raw)
To: Heiko Stübner
Cc: Rob Herring, Mark Rutland, Manivannan Sadhasivam, Akash Gajjar,
Tom Cubie, devicetree, linux-arm-kernel,
open list:ARM/Rockchip SoC...,
linux-kernel, linux-amarula
Hi Heiko,
On Wed, Nov 20, 2019 at 6:59 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Hi Jagan,
>
> looks good in general, just some small things below:
>
> Am Mittwoch, 20. November 2019, 12:39:20 CET schrieb Jagan Teki:
> > VMARC RK3399Pro SOM is a standard SMARC SOM design with
> > Rockchip RK3399Pro SoC, which is designed by Vamrs.
> >
> > Specification:
> > - Rockchip RK3399Pro
> > - PMIC: RK809-3
> > - SD slot, 16GiB eMMC
> > - 2xUSB-2.0, 1xUSB3.0
> > - USB-C for power supply
> > - Ethernet, PCIe
> > - HDMI, MIPI-DSI/CSI, eDP
> >
> > Add initial support for VMARC RK3399Pro SOM, this would use
> > with associated carrier board.
> >
> > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> > ---
> > .../dts/rockchip/rk3399pro-vmarc-som.dtsi | 339 ++++++++++++++++++
> > 1 file changed, 339 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
> > new file mode 100644
> > index 000000000000..ddf6ebc9fbe3
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi
> > @@ -0,0 +1,339 @@
> > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> > +/*
> > + * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
> > + * Copyright (c) 2019 Vamrs Limited
> > + * Copyright (c) 2019 Amarula Solutions(India)
> > + */
> > +
> > +#include <dt-bindings/gpio/gpio.h>
> > +#include <dt-bindings/pinctrl/rockchip.h>
> > +#include <dt-bindings/pwm/pwm.h>
> > +
> > +/ {
> > + compatible = "vamrs,rk3399pro-vmarc-som", "rockchip,rk3399pro";
> > +
> > + clkin_gmac: external-gmac-clock {
> > + compatible = "fixed-clock";
> > + clock-frequency = <125000000>;
> > + clock-output-names = "clkin_gmac";
> > + #clock-cells = <0>;
> > + };
> > +
> > + vcc5v0_sys: vcc5v0-sys-regulator {
> > + compatible = "regulator-fixed";
> > + regulator-name = "vcc5v0_sys";
> > + regulator-always-on;
> > + regulator-boot-on;
> > + regulator-min-microvolt = <5000000>;
> > + regulator-max-microvolt = <5000000>;
>
> Is vcc5v0_sys really the topmost regulator getting the outside
> power-supply?
Thanks for pointing this, I forgot to check the vin supply in carrier
board schematics, yes it is VCC12V_DCIN (with 5V to 24V range) like
rock-pi-4. Will update the same.
>
>
> > + };
> > +
> > + vcc_lan: vcc3v3-phy-regulator {
> > + compatible = "regulator-fixed";
> > + regulator-name = "vcc_lan";
>
> vcc_lan / vcc_phy is mostly coming from the vendor bsp in some way
> and will be named differently in schematics ... also it should be connected
> to the regulator tree.
Infact bsp named this as vcc_phy, I got the vcc_lan from schematics[1]
page 16. Yes it is using VCCIO_3V3_S0 (SWOUT2 from regulator tree), I
will mark this regulator.
>
> [...]
>
> > +&tsadc {
> > + status = "okay";
> > +
> > + /* tshut mode 0:CRU 1:GPIO */
>
> I think we can live without the additional comments for properties :-)
True, I have reused it from rock-pi-4 thought that it would compatible
with old. will remove.
[1] https://dl.radxa.com/rockpin10/docs/hw/VMARC_RK3399Pro_sch_V1.1_20190619.pdf
Jagan.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 3/5] dt-bindings: arm: rockchip: Add Rock Pi N10 binding
2019-11-20 11:39 [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki
2019-11-20 11:39 ` [PATCH 1/5] dt-bindings: arm: rockchip: Add VMARC RK3399Pro SOM binding Jagan Teki
2019-11-20 11:39 ` [PATCH 2/5] arm64: dts: rockchip: Add VMARC RK3399Pro SOM initial support Jagan Teki
@ 2019-11-20 11:39 ` Jagan Teki
2019-11-20 11:39 ` [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board Jagan Teki
2019-11-20 11:39 ` [PATCH 5/5] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support Jagan Teki
4 siblings, 0 replies; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 11:39 UTC (permalink / raw)
To: Heiko Stuebner, Rob Herring, Mark Rutland
Cc: Manivannan Sadhasivam, Akash Gajjar, Tom Cubie, devicetree,
linux-arm-kernel, linux-rockchip, linux-kernel, linux-amarula,
Jagan Teki
Rock Pi N10 is a Rockchip RK3399Pro based SBC, which has
- VMARC RK3399Pro SOM (as per SMARC standard) from Vamrs.
- Compatible carrier board from Radxa.
VMARC RK3399Pro SOM need to mount on top of carrier board
for making Rock PI N10 SBC.
Add dt-bindings for it.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index 51aa458833a9..63d34520c72f 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -423,6 +423,11 @@ properties:
- const: radxa,rockpi4
- const: rockchip,rk3399
+ - description: Radxa Rock Pi N10
+ items:
+ - const: radxa,rockpi-n10
+ - const: rockchip,rk3399pro
+
- description: Radxa Rock2 Square
items:
- const: radxa,rock2-square
--
2.18.0.321.gffc6fa0e3
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board
2019-11-20 11:39 [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki
` (2 preceding siblings ...)
2019-11-20 11:39 ` [PATCH 3/5] dt-bindings: arm: rockchip: Add Rock Pi N10 binding Jagan Teki
@ 2019-11-20 11:39 ` Jagan Teki
2019-11-20 13:25 ` Heiko Stübner
2019-11-20 11:39 ` [PATCH 5/5] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support Jagan Teki
4 siblings, 1 reply; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 11:39 UTC (permalink / raw)
To: Heiko Stuebner, Rob Herring, Mark Rutland
Cc: Manivannan Sadhasivam, Akash Gajjar, Tom Cubie, devicetree,
linux-arm-kernel, linux-rockchip, linux-kernel, linux-amarula,
Jagan Teki
Carrier board often referred as baseboard. For making
complete SBC, the associated SOM will mount on top of
this carrier board.
Radxa has a carrier board which supports on board
peripherals, ports like USB-2.0, USB-3.0, HDMI, MIPI DSI/CSI,
eDP, Ethernet, PCIe, USB-C, 40-Pin GPIO header and etc.
Currently this carrier board can be used together with
VMARC RK3399Por SOM for making Rock PI N10 SBC.
So add this carrier board dtsi as a separate file in
ARM directory, so-that the same can reuse it in both
arm32 and arm64 variants of Rockchip SOMs.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
.../boot/dts/rockchip-radxa-carrierboard.dtsi | 81 +++++++++++++++++++
1 file changed, 81 insertions(+)
create mode 100644 arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
diff --git a/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi b/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
new file mode 100644
index 000000000000..df3712aedf8a
--- /dev/null
+++ b/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
@@ -0,0 +1,81 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
+ * Copyright (c) 2019 Radxa Limited
+ * Copyright (c) 2019 Amarula Solutions(India)
+ */
+
+#include <dt-bindings/pwm/pwm.h>
+
+/ {
+ chosen {
+ stdout-path = "serial2:1500000n8";
+ };
+};
+
+&gmac {
+ status = "okay";
+};
+
+&i2c1 {
+ status = "okay";
+ i2c-scl-rising-time-ns = <140>;
+ i2c-scl-falling-time-ns = <30>;
+};
+
+&i2c2 {
+ status = "okay";
+ clock-frequency = <400000>;
+
+ hym8563: hym8563@51 {
+ compatible = "haoyu,hym8563";
+ reg = <0x51>;
+ #clock-cells = <0>;
+ clock-frequency = <32768>;
+ clock-output-names = "hym8563";
+ pinctrl-names = "default";
+ pinctrl-0 = <&hym8563_int>;
+ interrupt-parent = <&gpio4>;
+ interrupts = <30 IRQ_TYPE_LEVEL_LOW>;
+ };
+};
+
+&pwm0 {
+ status = "okay";
+};
+
+&pwm2 {
+ status = "okay";
+};
+
+&sdmmc {
+ bus-width = <4>;
+ cap-mmc-highspeed;
+ cap-sd-highspeed;
+ cd-gpios = <&gpio0 RK_PA7 GPIO_ACTIVE_LOW>;
+ disable-wp;
+ vqmmc-supply = <&vccio_sd>;
+ max-frequency = <150000000>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&sdmmc_clk &sdmmc_cmd &sdmmc_cd &sdmmc_bus4>;
+ status = "okay";
+};
+
+&uart0 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&uart0_xfer &uart0_cts>;
+ status = "okay";
+};
+
+&uart2 {
+ status = "okay";
+};
+
+&pinctrl {
+ hym8563 {
+ hym8563_int: hym8563-int {
+ rockchip,pins =
+ <4 RK_PD6 0 &pcfg_pull_up>;
+ };
+ };
+};
--
2.18.0.321.gffc6fa0e3
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board
2019-11-20 11:39 ` [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board Jagan Teki
@ 2019-11-20 13:25 ` Heiko Stübner
2019-11-20 13:45 ` Jagan Teki
0 siblings, 1 reply; 12+ messages in thread
From: Heiko Stübner @ 2019-11-20 13:25 UTC (permalink / raw)
To: Jagan Teki
Cc: Rob Herring, Mark Rutland, Manivannan Sadhasivam, Akash Gajjar,
Tom Cubie, devicetree, linux-arm-kernel, linux-rockchip,
linux-kernel, linux-amarula
Hi Jagan,
Am Mittwoch, 20. November 2019, 12:39:22 CET schrieb Jagan Teki:
> Carrier board often referred as baseboard. For making
> complete SBC, the associated SOM will mount on top of
> this carrier board.
>
> Radxa has a carrier board which supports on board
> peripherals, ports like USB-2.0, USB-3.0, HDMI, MIPI DSI/CSI,
> eDP, Ethernet, PCIe, USB-C, 40-Pin GPIO header and etc.
>
> Currently this carrier board can be used together with
> VMARC RK3399Por SOM for making Rock PI N10 SBC.
>
> So add this carrier board dtsi as a separate file in
> ARM directory, so-that the same can reuse it in both
> arm32 and arm64 variants of Rockchip SOMs.
Do you really think someone will create an arm32 soc using that
carrier board?
Similarly so far I don't think we haven't even seen a lot of reuse
of existing carrier boards at all, other than their initial combination.
So maybe just having the content of your
rockchip-radxa-carrierboard.dtsi
in
rockchip/rk3399pro-rock-pi-n10.dts
from patch 5 might be a better start - at least until there is any
further usage - if at all?
Also rockchip-radxa-carrierboard might even be overly generic
as there may be multiple carrierboards from Radxa later on.
Heiko
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> .../boot/dts/rockchip-radxa-carrierboard.dtsi | 81 +++++++++++++++++++
> 1 file changed, 81 insertions(+)
> create mode 100644 arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
>
> diff --git a/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi b/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
> new file mode 100644
> index 000000000000..df3712aedf8a
> --- /dev/null
> +++ b/arch/arm/boot/dts/rockchip-radxa-carrierboard.dtsi
> @@ -0,0 +1,81 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
> + * Copyright (c) 2019 Radxa Limited
> + * Copyright (c) 2019 Amarula Solutions(India)
> + */
> +
> +#include <dt-bindings/pwm/pwm.h>
> +
> +/ {
> + chosen {
> + stdout-path = "serial2:1500000n8";
> + };
> +};
> +
> +&gmac {
> + status = "okay";
> +};
> +
> +&i2c1 {
> + status = "okay";
> + i2c-scl-rising-time-ns = <140>;
> + i2c-scl-falling-time-ns = <30>;
> +};
> +
> +&i2c2 {
> + status = "okay";
> + clock-frequency = <400000>;
> +
> + hym8563: hym8563@51 {
> + compatible = "haoyu,hym8563";
> + reg = <0x51>;
> + #clock-cells = <0>;
> + clock-frequency = <32768>;
> + clock-output-names = "hym8563";
> + pinctrl-names = "default";
> + pinctrl-0 = <&hym8563_int>;
> + interrupt-parent = <&gpio4>;
> + interrupts = <30 IRQ_TYPE_LEVEL_LOW>;
> + };
> +};
> +
> +&pwm0 {
> + status = "okay";
> +};
> +
> +&pwm2 {
> + status = "okay";
> +};
> +
> +&sdmmc {
> + bus-width = <4>;
> + cap-mmc-highspeed;
> + cap-sd-highspeed;
> + cd-gpios = <&gpio0 RK_PA7 GPIO_ACTIVE_LOW>;
> + disable-wp;
> + vqmmc-supply = <&vccio_sd>;
> + max-frequency = <150000000>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&sdmmc_clk &sdmmc_cmd &sdmmc_cd &sdmmc_bus4>;
> + status = "okay";
> +};
> +
> +&uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart0_xfer &uart0_cts>;
> + status = "okay";
> +};
> +
> +&uart2 {
> + status = "okay";
> +};
> +
> +&pinctrl {
> + hym8563 {
> + hym8563_int: hym8563-int {
> + rockchip,pins =
> + <4 RK_PD6 0 &pcfg_pull_up>;
> + };
> + };
> +};
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board
2019-11-20 13:25 ` Heiko Stübner
@ 2019-11-20 13:45 ` Jagan Teki
2019-11-20 13:53 ` Heiko Stübner
0 siblings, 1 reply; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 13:45 UTC (permalink / raw)
To: Heiko Stübner
Cc: Mark Rutland, devicetree, Tom Cubie, linux-kernel,
open list:ARM/Rockchip SoC...,
Rob Herring, Akash Gajjar, Manivannan Sadhasivam, linux-amarula,
linux-arm-kernel
Hi Heiko,
On Wed, Nov 20, 2019 at 6:55 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Hi Jagan,
>
> Am Mittwoch, 20. November 2019, 12:39:22 CET schrieb Jagan Teki:
> > Carrier board often referred as baseboard. For making
> > complete SBC, the associated SOM will mount on top of
> > this carrier board.
> >
> > Radxa has a carrier board which supports on board
> > peripherals, ports like USB-2.0, USB-3.0, HDMI, MIPI DSI/CSI,
> > eDP, Ethernet, PCIe, USB-C, 40-Pin GPIO header and etc.
> >
> > Currently this carrier board can be used together with
> > VMARC RK3399Por SOM for making Rock PI N10 SBC.
> >
> > So add this carrier board dtsi as a separate file in
> > ARM directory, so-that the same can reuse it in both
> > arm32 and arm64 variants of Rockchip SOMs.
>
> Do you really think someone will create an arm32 soc using that
> carrier board?
Yes, we have Rock Pi N8 which is using same carrier board design with
(+ external codec) on top of RK3288 SOM. I didn't mentioned on the
commit message since radxa doesn't officially announced on the
website.
>
> Similarly so far I don't think we haven't even seen a lot of reuse
> of existing carrier boards at all, other than their initial combination.
>
> So maybe just having the content of your
> rockchip-radxa-carrierboard.dtsi
> in
> rockchip/rk3399pro-rock-pi-n10.dts
> from patch 5 might be a better start - at least until there is any
> further usage - if at all?
But, this particular design has proper use case.
1. rk3399pro SOM + carrier board (Rock Pi N10)
2. rk3288 SOM + carrier board (Rock Pi N8)
>
> Also rockchip-radxa-carrierboard might even be overly generic
> as there may be multiple carrierboards from Radxa later on.
I'm slightly disagree of having overlay here, since these are fixed
design combinations. where SOM with respective carrier board is
mandatory to make final board. Understand that we can have a
maintenance over-ahead if we have multiple carrier boards, but right
now radxa has only one carrier board with 2 sets of SOM's combinations
that indeed fit like a dev board, so there is unused carrier board.
Jagan.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board
2019-11-20 13:45 ` Jagan Teki
@ 2019-11-20 13:53 ` Heiko Stübner
2019-11-20 15:33 ` Jagan Teki
0 siblings, 1 reply; 12+ messages in thread
From: Heiko Stübner @ 2019-11-20 13:53 UTC (permalink / raw)
To: Jagan Teki
Cc: Mark Rutland, devicetree, Tom Cubie, linux-kernel,
open list:ARM/Rockchip SoC...,
Rob Herring, Akash Gajjar, Manivannan Sadhasivam, linux-amarula,
linux-arm-kernel
Hi Jagan,
Am Mittwoch, 20. November 2019, 14:45:35 CET schrieb Jagan Teki:
> On Wed, Nov 20, 2019 at 6:55 PM Heiko Stübner <heiko@sntech.de> wrote:
> > Am Mittwoch, 20. November 2019, 12:39:22 CET schrieb Jagan Teki:
> > > Carrier board often referred as baseboard. For making
> > > complete SBC, the associated SOM will mount on top of
> > > this carrier board.
> > >
> > > Radxa has a carrier board which supports on board
> > > peripherals, ports like USB-2.0, USB-3.0, HDMI, MIPI DSI/CSI,
> > > eDP, Ethernet, PCIe, USB-C, 40-Pin GPIO header and etc.
> > >
> > > Currently this carrier board can be used together with
> > > VMARC RK3399Por SOM for making Rock PI N10 SBC.
> > >
> > > So add this carrier board dtsi as a separate file in
> > > ARM directory, so-that the same can reuse it in both
> > > arm32 and arm64 variants of Rockchip SOMs.
> >
> > Do you really think someone will create an arm32 soc using that
> > carrier board?
>
> Yes, we have Rock Pi N8 which is using same carrier board design with
> (+ external codec) on top of RK3288 SOM. I didn't mentioned on the
> commit message since radxa doesn't officially announced on the
> website.
>
> >
> > Similarly so far I don't think we haven't even seen a lot of reuse
> > of existing carrier boards at all, other than their initial combination.
> >
> > So maybe just having the content of your
> > rockchip-radxa-carrierboard.dtsi
> > in
> > rockchip/rk3399pro-rock-pi-n10.dts
> > from patch 5 might be a better start - at least until there is any
> > further usage - if at all?
>
> But, this particular design has proper use case.
> 1. rk3399pro SOM + carrier board (Rock Pi N10)
> 2. rk3288 SOM + carrier board (Rock Pi N8)
>
> >
> > Also rockchip-radxa-carrierboard might even be overly generic
> > as there may be multiple carrierboards from Radxa later on.
>
> I'm slightly disagree of having overlay here, since these are fixed
> design combinations. where SOM with respective carrier board is
> mandatory to make final board. Understand that we can have a
> maintenance over-ahead if we have multiple carrier boards, but right
> now radxa has only one carrier board with 2 sets of SOM's combinations
> that indeed fit like a dev board, so there is unused carrier board.
All is good ... with that information from above (rk3288) this definitly
makes more sense :-)
The naming of the file is still a tiny struggle though. Does this board
maybe have some actual product name or is it really just called
"carrierboard"? :-)
Thanks
Heiko
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board
2019-11-20 13:53 ` Heiko Stübner
@ 2019-11-20 15:33 ` Jagan Teki
0 siblings, 0 replies; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 15:33 UTC (permalink / raw)
To: Heiko Stübner
Cc: Mark Rutland, devicetree, Tom Cubie, linux-kernel,
open list:ARM/Rockchip SoC...,
Rob Herring, Akash Gajjar, Manivannan Sadhasivam, linux-amarula,
linux-arm-kernel
Hi Heiko,
On Wed, Nov 20, 2019 at 7:23 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Hi Jagan,
>
> Am Mittwoch, 20. November 2019, 14:45:35 CET schrieb Jagan Teki:
> > On Wed, Nov 20, 2019 at 6:55 PM Heiko Stübner <heiko@sntech.de> wrote:
> > > Am Mittwoch, 20. November 2019, 12:39:22 CET schrieb Jagan Teki:
> > > > Carrier board often referred as baseboard. For making
> > > > complete SBC, the associated SOM will mount on top of
> > > > this carrier board.
> > > >
> > > > Radxa has a carrier board which supports on board
> > > > peripherals, ports like USB-2.0, USB-3.0, HDMI, MIPI DSI/CSI,
> > > > eDP, Ethernet, PCIe, USB-C, 40-Pin GPIO header and etc.
> > > >
> > > > Currently this carrier board can be used together with
> > > > VMARC RK3399Por SOM for making Rock PI N10 SBC.
> > > >
> > > > So add this carrier board dtsi as a separate file in
> > > > ARM directory, so-that the same can reuse it in both
> > > > arm32 and arm64 variants of Rockchip SOMs.
> > >
> > > Do you really think someone will create an arm32 soc using that
> > > carrier board?
> >
> > Yes, we have Rock Pi N8 which is using same carrier board design with
> > (+ external codec) on top of RK3288 SOM. I didn't mentioned on the
> > commit message since radxa doesn't officially announced on the
> > website.
> >
> > >
> > > Similarly so far I don't think we haven't even seen a lot of reuse
> > > of existing carrier boards at all, other than their initial combination.
> > >
> > > So maybe just having the content of your
> > > rockchip-radxa-carrierboard.dtsi
> > > in
> > > rockchip/rk3399pro-rock-pi-n10.dts
> > > from patch 5 might be a better start - at least until there is any
> > > further usage - if at all?
> >
> > But, this particular design has proper use case.
> > 1. rk3399pro SOM + carrier board (Rock Pi N10)
> > 2. rk3288 SOM + carrier board (Rock Pi N8)
> >
> > >
> > > Also rockchip-radxa-carrierboard might even be overly generic
> > > as there may be multiple carrierboards from Radxa later on.
> >
> > I'm slightly disagree of having overlay here, since these are fixed
> > design combinations. where SOM with respective carrier board is
> > mandatory to make final board. Understand that we can have a
> > maintenance over-ahead if we have multiple carrier boards, but right
> > now radxa has only one carrier board with 2 sets of SOM's combinations
> > that indeed fit like a dev board, so there is unused carrier board.
>
> All is good ... with that information from above (rk3288) this definitly
> makes more sense :-)
>
> The naming of the file is still a tiny struggle though. Does this board
> maybe have some actual product name or is it really just called
> "carrierboard"? :-)
True, I felt the same. Just now Tom has named this as 'Dalang Carrier
board' so we can have rockchip-radxa-dalang.dtsi or
rockchip-radxa-dalang-carrier.dtsi as file names. or let me know if
you have any suggestions on the file name?
Jagan.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 5/5] arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support
2019-11-20 11:39 [PATCH 0/5] arm64: dts: rockchip: Add Rock Pi N10 support Jagan Teki
` (3 preceding siblings ...)
2019-11-20 11:39 ` [PATCH 4/5] ARM: dts: rockchip: Add Radxa Carrier board Jagan Teki
@ 2019-11-20 11:39 ` Jagan Teki
4 siblings, 0 replies; 12+ messages in thread
From: Jagan Teki @ 2019-11-20 11:39 UTC (permalink / raw)
To: Heiko Stuebner, Rob Herring, Mark Rutland
Cc: Manivannan Sadhasivam, Akash Gajjar, Tom Cubie, devicetree,
linux-arm-kernel, linux-rockchip, linux-kernel, linux-amarula,
Jagan Teki
Rock Pi N10 is a Rockchip RK3399Pro based SBC, which has
- VMARC RK3399Pro SOM (as per SMARC standard) from Vamrs.
- Compatible carrier board from Radxa.
VAMRC RK3399Pro SOM need to mount on top of Radxa carrier
board for making Rock Pi N10 SBC.
So, add initial support for Rock Pi N10 by including rk3399,
rk3399pro vamrc-som and raxda carrier board dtsi files.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3399pro-rock-pi-n10.dts | 17 +++++++++++++++++
2 files changed, 18 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dts
diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
index 48fb631d5451..433033b18170 100644
--- a/arch/arm64/boot/dts/rockchip/Makefile
+++ b/arch/arm64/boot/dts/rockchip/Makefile
@@ -36,3 +36,4 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rock960.dtb
dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rockpro64.dtb
dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-sapphire.dtb
dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-sapphire-excavator.dtb
+dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399pro-rock-pi-n10.dtb
diff --git a/arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dts b/arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dts
new file mode 100644
index 000000000000..1f7fbaa92c38
--- /dev/null
+++ b/arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dts
@@ -0,0 +1,17 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Copyright (c) 2019 Fuzhou Rockchip Electronics Co., Ltd
+ * Copyright (c) 2019 Radxa Limited
+ * Copyright (c) 2019 Amarula Solutions(India)
+ */
+
+/dts-v1/;
+#include "rk3399.dtsi"
+#include "rk3399-opp.dtsi"
+#include "rk3399pro-vmarc-som.dtsi"
+#include <arm/rockchip-radxa-carrierboard.dtsi>
+
+/ {
+ model = "Radxa ROCK Pi N10";
+ compatible = "radxa,rockpi-n10", "rockchip,rk3399pro";
+};
--
2.18.0.321.gffc6fa0e3
^ permalink raw reply related [flat|nested] 12+ messages in thread