linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
	Bao Cheng Su <baocheng.su@siemens.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Le Jin <le.jin@siemens.com>
Subject: [PATCH v2 0/4] arm64: Add TI AM65x-based IOT2050 boards
Date: Thu, 11 Feb 2021 20:32:52 +0100	[thread overview]
Message-ID: <cover.1613071976.git.jan.kiszka@siemens.com> (raw)

Changes in v2:
 - address board-specific issues found by kernel_verify_patch
 - remove dead l2-cache node from iot2050-basic DT
 - add binding for Siemens vendor prefix
 - factor out board bindings into separate patch
 - add missing device_type to common ti,am654-pcie-rc nodes

Jan

Jan Kiszka (4):
  dt-bindings: Add Siemens vendor prefix
  dt-bindings: arm: ti: Add bindings for Siemens IOT2050 boards
  arm64: dts: ti: Add support for Siemens IOT2050 boards
  arm64: dts: ti: k3-am65-main: Add device_type to pcie*_rc nodes

 .../devicetree/bindings/arm/ti/k3.yaml        |   2 +
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 arch/arm64/boot/dts/ti/Makefile               |   2 +
 .../boot/dts/ti/k3-am65-iot2050-common.dtsi   | 679 ++++++++++++++++++
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi      |   2 +
 .../boot/dts/ti/k3-am6528-iot2050-basic.dts   |  61 ++
 .../dts/ti/k3-am6548-iot2050-advanced.dts     |  60 ++
 7 files changed, 808 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dts

-- 
2.26.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-02-11 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 19:32 Jan Kiszka [this message]
2021-02-11 19:32 ` [PATCH v2 1/4] dt-bindings: Add Siemens vendor prefix Jan Kiszka
2021-03-05 19:33   ` Rob Herring
2021-03-05 20:18     ` Nishanth Menon
2021-02-11 19:32 ` [PATCH v2 2/4] dt-bindings: arm: ti: Add bindings for Siemens IOT2050 boards Jan Kiszka
2021-03-04  6:14   ` Vignesh Raghavendra
2021-03-05 19:33   ` Rob Herring
2021-02-11 19:32 ` [PATCH v2 3/4] arm64: dts: ti: Add support " Jan Kiszka
2021-03-04  6:58   ` Vignesh Raghavendra
2021-03-09  7:18     ` Jan Kiszka
2021-03-09  8:38       ` [PATCH v3 " Jan Kiszka
2021-03-09 14:41         ` Nishanth Menon
2021-03-09 15:15           ` Jan Kiszka
2021-03-09 15:10         ` Nishanth Menon
2021-03-09 15:22           ` Jan Kiszka
2021-03-09 15:38             ` Nishanth Menon
2021-02-11 19:32 ` [PATCH v2 4/4] arm64: dts: ti: k3-am65-main: Add device_type to pcie*_rc nodes Jan Kiszka
2021-02-12 14:55   ` Kishon Vijay Abraham I
2021-02-12 19:31 ` [PATCH v2 0/4] arm64: Add TI AM65x-based IOT2050 boards Jan Kiszka
2021-03-03 14:05 ` Nishanth Menon

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.1613071976.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=baocheng.su@siemens.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=le.jin@siemens.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    /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).