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>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Bao Cheng Su <baocheng.su@siemens.com>,
Hua Qian Li <huaqian.li@siemens.com>
Subject: [PATCH 0/2] arm64: dts: iot2050: Fix R5 lock-step settings, add overlays
Date: Mon, 26 Aug 2024 16:28:57 +0200 [thread overview]
Message-ID: <cover.1724682539.git.jan.kiszka@siemens.com> (raw)
Trying to get our backlog closer to zero. See patches for details.
Jan
Jan Kiszka (1):
arm64: dts: ti: iot2050: Add overlays for M.2 used by firmware
Li Hua Qian (1):
arm64: dts: ti: iot2050: Disable lock-step for all iot2050 boards
arch/arm64/boot/dts/ti/Makefile | 2 +
.../dts/ti/k3-am65-iot2050-common-pg2.dtsi | 5 --
.../boot/dts/ti/k3-am65-iot2050-common.dtsi | 5 ++
.../boot/dts/ti/k3-am6528-iot2050-basic.dts | 5 --
...48-iot2050-advanced-m2-bkey-ekey-pcie.dtso | 27 +++++++++++
...-am6548-iot2050-advanced-m2-bkey-usb3.dtso | 47 +++++++++++++++++++
6 files changed, 81 insertions(+), 10 deletions(-)
create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie.dtso
create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2-bkey-usb3.dtso
--
2.43.0
next reply other threads:[~2024-08-26 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 14:28 Jan Kiszka [this message]
2024-08-26 14:28 ` [PATCH 1/2] arm64: dts: ti: iot2050: Disable lock-step for all iot2050 boards Jan Kiszka
2024-08-26 14:28 ` [PATCH 2/2] arm64: dts: ti: iot2050: Add overlays for M.2 used by firmware Jan Kiszka
2024-08-27 15:33 ` Rob Herring
2024-08-27 16:20 ` Jan Kiszka
2024-08-27 17:30 ` Krzysztof Kozlowski
2024-08-28 5:39 ` Jan Kiszka
2024-08-28 12:54 ` Krzysztof Kozlowski
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.1724682539.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huaqian.li@siemens.com \
--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
all inboxes | Powered by JetHome®