From: Nishanth Menon <nm@ti.com>
To: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>
Cc: Wadim Egorov <w.egorov@phytec.de>,
Francesco Dolcini <francesco@dolcini.it>,
Sjoerd Simons <sjoerd@collabora.com>,
Neha Malcom Francis <n-francis@ti.com>,
Bryan Brattlof <bb@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Nitin Yadav <n-yadav@ti.com>, Nishanth Menon <nm@ti.com>
Subject: [RFC PATCH 0/4] arm: dts: Sync k3-am62 with upstream
Date: Thu, 13 Jul 2023 02:20:15 -0500 [thread overview]
Message-ID: <20230713072019.3153871-1-nm@ti.com> (raw)
This series depends on Neha's binman series[1] and is intended for
review and I will repost once binman series is merged in.
I have picked up part of Sjoerd's series[2] to keep it constrained just
to dts sync at this point rather than adding newer functionality on top.
You can find the full series in [3].
Attempting am625 as a start of a series of clean ups for device tree for
u-boot, but will love to get any review comments to improve this series
up.
Nishanth Menon (2):
arm: dts: Fix build of am62a7 dtbs
arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1
Sjoerd Simons (2):
omap: timer: add ti,am654-timer compatibility
arm: mach-k3: am62: Add timer0 id to the dev list
arch/arm/dts/Makefile | 2 +-
arch/arm/dts/k3-am62-main.dtsi | 389 +++++++++++++++++++++++--
arch/arm/dts/k3-am62-mcu.dtsi | 66 +++++
arch/arm/dts/k3-am62-thermal.dtsi | 33 +++
arch/arm/dts/k3-am62-wakeup.dtsi | 33 ++-
arch/arm/dts/k3-am62.dtsi | 11 +-
arch/arm/dts/k3-am625-r5-sk.dts | 92 +-----
arch/arm/dts/k3-am625-sk-u-boot.dtsi | 24 +-
arch/arm/dts/k3-am625-sk.dts | 286 ++-----------------
arch/arm/dts/k3-am625.dtsi | 54 +++-
arch/arm/dts/k3-am62x-sk-common.dtsi | 412 +++++++++++++++++++++++++++
arch/arm/dts/k3-pinctrl.h | 53 ++++
arch/arm/mach-k3/am62x/dev-data.c | 3 +-
drivers/timer/omap-timer.c | 1 +
14 files changed, 1069 insertions(+), 390 deletions(-)
create mode 100644 arch/arm/dts/k3-am62-thermal.dtsi
create mode 100644 arch/arm/dts/k3-am62x-sk-common.dtsi
create mode 100644 arch/arm/dts/k3-pinctrl.h
[1] https://lore.kernel.org/all/20230712183453.7623-1-n-francis@ti.com/
[2] https://lore.kernel.org/all/20230406185542.1179073-1-sjoerd@collabora.com/
[3] https://github.com/nmenon/fix-k3-dt-u-boot/commits/fdt-fixup-s1-am625-rev1
--
2.40.0
next reply other threads:[~2023-07-13 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:20 Nishanth Menon [this message]
2023-07-13 7:20 ` [RFC PATCH 1/4] omap: timer: add ti,am654-timer compatibility Nishanth Menon
2023-07-13 7:20 ` [RFC PATCH 2/4] arm: mach-k3: am62: Add timer0 id to the dev list Nishanth Menon
2023-07-13 11:38 ` Ravi Gunasekaran
2023-07-13 18:35 ` Nishanth Menon
2023-07-13 18:59 ` Bryan Brattlof
2023-07-13 7:20 ` [RFC PATCH 3/4] arm: dts: Fix build of am62a7 dtbs Nishanth Menon
2023-07-13 9:11 ` Mattijs Korpershoek
2023-07-13 19:00 ` Bryan Brattlof
2023-07-13 19:38 ` Nishanth Menon
2023-07-13 7:20 ` [RFC PATCH 4/4] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1 Nishanth Menon
2023-07-19 8:27 ` Maxime Ripard
2023-07-19 14:05 ` Nishanth Menon
2023-07-19 14:14 ` Maxime Ripard
2023-07-19 17:22 ` Nishanth Menon
2023-07-20 15:24 ` Roger Quadros
2023-07-17 12:27 ` [RFC PATCH 0/4] arm: dts: Sync k3-am62 with upstream Maxime Ripard
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=20230713072019.3153871-1-nm@ti.com \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=n-francis@ti.com \
--cc=n-yadav@ti.com \
--cc=sjoerd@collabora.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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