From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Bao Cheng Su <baocheng.su@siemens.com>,
Chao Zeng <chao.zeng@siemens.com>
Subject: [PATCH v2 0/3] arm64: dts: Add IOT2050 M.2 board, describe QSPI layout
Date: Thu, 19 Jan 2023 07:40:39 +0100 [thread overview]
Message-ID: <cover.1674110442.git.jan.kiszka@siemens.com> (raw)
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
--
2.35.3
next reply other threads:[~2023-01-19 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 6:40 Jan Kiszka [this message]
2023-01-19 6:40 ` [PATCH v2 1/3] arm64: dts: ti: iot2050: Add layout of OSPI flash Jan Kiszka
2023-01-19 6:40 ` [PATCH v2 2/3] dt-bindings: arm: ti: Add binding for Siemens IOT2050 M.2 variant Jan Kiszka
2023-01-19 6:40 ` [PATCH v2 3/3] arm64: dts: ti: iot2050: Add support for " Jan Kiszka
2023-01-25 6:11 ` Siddharth Vadapalli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1674110442.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).