arm64: dts: Add IOT2050 M.2 board, describe QSPI layout
Subsystems (2)
v2 cover arm64: dts: Add IOT2050 M.2 board, describe QSPI layout
This adds the devices tree for a new variant of the IOT2050 which comes with two M.2 slots and is otherwise almost equivalent to the existing Advanced PG2 variant (USB3 is available via M.2 now).
Furthermore, the device tree of the whole device series is extended to also hold the QSPI layout.
Changes in v2:
- alphabetic ordering in binding schema and makefile
- dropped an unneeded blank line in patch 3
Jan
Jan Kiszka (2):
arm64: dts: ti: iot2050: Add layout of OSPI flash
dt-bindings: arm: ti: Add binding for Siemens IOT2050 M.2 variant
chao zeng (1):
arm64: dts: ti: iot2050: Add support for M.2 variant
.../devicetree/bindings/arm/ti/k3.yaml | 1 + arch/arm64/boot/dts/ti/Makefile | 3 + .../boot/dts/ti/k3-am65-iot2050-common.dtsi | 46 +++++++ .../dts/ti/k3-am6548-iot2050-advanced-m2.dts | 121 ++++++++++++++++++ 4 files changed, 171 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2.dts
Signature · 7 lines
2.35.3 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH v2 1/3 arm64: dts: ti: iot2050: Add layout of OSPI flash
From: Jan Kiszka <[email protected]>
Describe the layout of the OSPI flash as the latest firmware uses it. Specifically the location of the U-Boot envs is important for userspace in order to access it.
--- .../boot/dts/ti/k3-am65-iot2050-common.dtsi | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+)
arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi +46 -0
@@ -609,6 +609,52 @@ flash@0 { cdns,tchsh-ns = <60>; cdns,tslch-ns = <60>; cdns,read-delay = <2>; + + partitions { + compatible = "fixed-partitions"; + #address-cells = <1>; + #size-cells = <1>; + + seboot@0 { + label = "seboot"; + reg = <0x0 0x180000>; /* 1.5M */ + }; + + tispl@180000 { + label = "tispl"; + reg = <0x180000 0x200000>; /* 2M */ + }; + + u-boot@380000 { + label = "u-boot"; + reg = <0x380000 0x300000>; /* 3M */ + }; + + env@680000 { + label = "env"; + reg = <0x680000 0x20000>; /* 128K */ + }; + + env-backup@6a0000 { + label = "env.backup"; + reg = <0x6a0000 0x20000>; /* 128K */ + }; + + otpcmd@6c0000 { + label = "otpcmd"; + reg = <0x6c0000 0x10000>; /* 64K */ + }; + + unused@6d0000 { + label = "unused"; + reg = <0x6d0000 0x7b0000>; /* 7872K */ + }; + + seboot-backup@e80000 { + label = "seboot.backup"; + reg = <0xe80000 0x180000>; /* 1.5M */ + }; + }; }; };
Signature · 7 lines
2.35.3 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH v2 2/3 dt-bindings: arm: ti: Add binding for Siemens IOT2050 M.2 variant
In reply to Jan KiszkaFrom: Jan Kiszka <[email protected]>
This new variant is derived from the Advanced PG2 board, replacing the MiniPCI slot with B and E-keyed M.2 slots.
--- Documentation/devicetree/bindings/arm/ti/k3.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/ti/k3.yaml +1 -0
@@ -42,6 +42,7 @@ properties: items: - enum: - siemens,iot2050-advanced + - siemens,iot2050-advanced-m2 - siemens,iot2050-advanced-pg2 - siemens,iot2050-basic - siemens,iot2050-basic-pg2
Signature · 7 lines
2.35.3 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH v2 3/3 arm64: dts: ti: iot2050: Add support for M.2 variant
In reply to Jan KiszkaFrom: chao zeng <[email protected]>
The M.2 variant comes with 2 slots, one B-keyed and another one E-keyed. They are configured by the firmware during startup. Also the device tree will be adjusted according to the detect or manually configured interface mode by the firmware. The kernel only carries a single configuration as base device tree. It has to be built with a symbols node so that the firmware can apply overlays for the connector modes.
--- arch/arm64/boot/dts/ti/Makefile | 3 + .../dts/ti/k3-am6548-iot2050-advanced-m2.dts | 121 ++++++++++++++++++ 2 files changed, 124 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2.dts
arch/arm64/boot/dts/ti/Makefile +3 -0
@@ -10,8 +10,11 @@ dtb-$(CONFIG_ARCH_K3) += k3-am654-base-board.dtb dtb-$(CONFIG_ARCH_K3) += k3-am6528-iot2050-basic.dtb dtb-$(CONFIG_ARCH_K3) += k3-am6528-iot2050-basic-pg2.dtb dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced-m2.dtb dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced-pg2.dtb +DTC_FLAGS_k3-am6548-iot2050-advanced-m2 += -@ + dtb-$(CONFIG_ARCH_K3) += k3-j721e-beagleboneai64.dtb dtb-$(CONFIG_ARCH_K3) += k3-j721e-common-proc-board.dtb dtb-$(CONFIG_ARCH_K3) += k3-j721e-sk.dtb
arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2.dts new file +121 -0
121 lines not on this page · raw message
Signature · 1 line
2.35.3
Re: [PATCH v2 3/3] arm64: dts: ti: iot2050: Add support for M.2 variant
Quoted 9 lines · Jan Kiszka
From: chao zeng <[email protected]>
The M.2 variant comes with 2 slots, one B-keyed and another one E-keyed. They are configured by the firmware during startup. Also the device tree will be adjusted according to the detect or manually configured interface mode by the firmware. The kernel only carries a single configuration as base device tree. It has to be built with a symbols node so that the firmware can apply overlays for the connector modes.
Quoted 8 lines
Signed-off-by chao zeng <[email protected]>[Jan: refactored to a single DT]Signed-off-by Jan Kiszka <[email protected]>--- arch/arm64/boot/dts/ti/Makefile | 3 + .../dts/ti/k3-am6548-iot2050-advanced-m2.dts | 121 ++++++++++++++++++ 2 files changed, 124 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2.dts
Regards,
Siddharth.