public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: trini@konsulko.com
Cc: nm@ti.com, vigneshr@ti.com, srk@ti.com, r-gunasekaran@ti.com,
	s-vadapalli@ti.com, u-boot@lists.denx.de,
	Roger Quadros <rogerq@kernel.org>
Subject: [PATCH v5 0/4] arm: dts: k3-am64: Sync DT with Linux
Date: Sat,  5 Aug 2023 11:14:36 +0300	[thread overview]
Message-ID: <20230805081440.7045-1-rogerq@kernel.org> (raw)

Hi,

This series syncs AM64 DT files from Linux v6.5-rc1.

Tested on AM642-EVM GP SR1.0 and AM642-SK-EVM HS-FS SR2.0.

cheers,
-roger

Changelog:

v5:
-squash documenation change to correct patch. Update commit log.
-add Nishanth's Reviewed/Tested by

v4:
-Add documentation for am642-evm and am642-sk-evm.
-Add license to am64 svg file
-drop mmc0 pinmux from k3-am642-r5-evm.dts
-drop stdout-path from -r5 & -u-boot dts.
-drop vtt-supply and vtt pinmux from memorycontroller in k3-am642-r5-evm.dts
-am642-evm: move bootph-pre-ram for main_esm, mcu_esm into -r5 .dts

v3:
- include board DT file in -r5 DT file.
- move including -u-boot.dtsi file at the top of -r5 DT file.
- drop duplicate nodes
- document why we need to delete clock/power properties from
  main_timer0

v2:
- Sync with v6.5-rc1
- Rebase on latest uboot/master
- CPSW node cleanup
- Timer node cleanup


Roger Quadros (4):
  board: ti: am64x: Recognize AM64-HSEVM
  Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node"
  doc: board: ti: am64: Add boot flow diagram
  arm: dts: k3-am64: Sync DT with Linux v6.5-rc1

 arch/arm/dts/k3-am64-main.dtsi         |  171 ++-
 arch/arm/dts/k3-am64-mcu.dtsi          |   53 +-
 arch/arm/dts/k3-am64-thermal.dtsi      |   33 +
 arch/arm/dts/k3-am64.dtsi              |   22 +-
 arch/arm/dts/k3-am642-evm-u-boot.dtsi  |   57 +-
 arch/arm/dts/k3-am642-evm.dts          |  173 ++-
 arch/arm/dts/k3-am642-r5-evm.dts       |  231 +---
 arch/arm/dts/k3-am642-r5-sk.dts        |  218 +--
 arch/arm/dts/k3-am642-sk-u-boot.dtsi   |  113 +-
 arch/arm/dts/k3-am642-sk.dts           |  166 ++-
 arch/arm/dts/k3-am642.dtsi             |    1 +
 board/ti/am64x/evm.c                   |    3 +-
 doc/board/ti/am64x_evm.rst             |  197 +++
 doc/board/ti/img/boot_diagram_am64.svg | 1702 ++++++++++++++++++++++++
 doc/board/ti/k3.rst                    |    1 +
 15 files changed, 2506 insertions(+), 635 deletions(-)
 create mode 100644 arch/arm/dts/k3-am64-thermal.dtsi
 create mode 100644 doc/board/ti/am64x_evm.rst
 create mode 100644 doc/board/ti/img/boot_diagram_am64.svg

-- 
2.34.1


             reply	other threads:[~2023-08-05  8:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  8:14 Roger Quadros [this message]
2023-08-05  8:14 ` [PATCH v5 1/4] board: ti: am64x: Recognize AM64-HSEVM Roger Quadros
2023-08-05  8:14 ` [PATCH v5 2/4] Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node" Roger Quadros
2023-08-05  8:14 ` [PATCH v5 3/4] doc: board: ti: am64: Add boot flow diagram Roger Quadros
2023-08-05  8:14 ` [PATCH v5 4/4] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 Roger Quadros
2023-08-05 16:29   ` Nishanth Menon
2023-08-17 19:18 ` [PATCH v5 0/4] arm: dts: k3-am64: Sync DT with Linux Tom Rini

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=20230805081440.7045-1-rogerq@kernel.org \
    --to=rogerq@kernel.org \
    --cc=nm@ti.com \
    --cc=r-gunasekaran@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --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