Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Dara Stotland <dstotland@nvidia.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Brad Griffis <bgriffis@nvidia.com>, <devicetree@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>
Cc: Dara Stotland <dstotland@nvidia.com>
Subject: [PATCH 0/7] Tegra234 AGX Orin DTS Updates
Date: Fri, 23 Aug 2024 21:49:50 +0000	[thread overview]
Message-ID: <20240823214957.771297-1-dstotland@nvidia.com> (raw)

This patchset restructures the AGX Orin device tree for improved
adaptability. It also fixes the placement of several nodes to be
in the proper files.

Dara Stotland (7):
  arm64: tegra: Combine AGX Orin board files
  arm64: tegra: Combine IGX Orin board files
  arm64: tegra: Move AGX Orin nodes to correct location
  arm64: tegra: Move padctl supply nodes to AGX Orin module
  arm64: tegra: Move BPMP nodes to AGX Orin module
  arm64: tegra: Add thermal nodes to AGX Orin SKU8
  arm64: tegra: Create SKU8 AGX Orin board file

 .../devicetree/bindings/arm/tegra.yaml        |   5 +
 arch/arm64/boot/dts/nvidia/Makefile           |   1 +
 .../boot/dts/nvidia/tegra234-p3701-0000.dtsi  |  52 --
 .../boot/dts/nvidia/tegra234-p3701-0008.dtsi  |  26 +-
 .../arm64/boot/dts/nvidia/tegra234-p3701.dtsi |  40 ++
 .../nvidia/tegra234-p3737-0000+p3701-0000.dts | 440 +-------------
 .../nvidia/tegra234-p3737-0000+p3701-0008.dts |  11 +
 .../dts/nvidia/tegra234-p3737-0000+p3701.dtsi | 547 ++++++++++++++++++
 .../boot/dts/nvidia/tegra234-p3737-0000.dtsi  |  90 ---
 .../nvidia/tegra234-p3740-0002+p3701-0008.dts | 230 +++++++-
 .../boot/dts/nvidia/tegra234-p3740-0002.dtsi  | 248 --------
 11 files changed, 851 insertions(+), 839 deletions(-)
 create mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0008.dts
 create mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi
 delete mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi
 delete mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3740-0002.dtsi

-- 
2.17.1


             reply	other threads:[~2024-08-23 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 21:49 Dara Stotland [this message]
2024-08-23 21:49 ` [PATCH 1/7] arm64: tegra: Combine AGX Orin board files Dara Stotland
2024-08-23 21:49 ` [PATCH 2/7] arm64: tegra: Combine IGX " Dara Stotland
2024-08-23 21:49 ` [PATCH 3/7] arm64: tegra: Move AGX Orin nodes to correct location Dara Stotland
2024-08-23 21:49 ` [PATCH 4/7] arm64: tegra: Move padctl supply nodes to AGX Orin module Dara Stotland
2024-08-23 21:49 ` [PATCH 5/7] arm64: tegra: Move BPMP " Dara Stotland
2024-08-23 21:49 ` [PATCH 6/7] arm64: tegra: Add thermal nodes to AGX Orin SKU8 Dara Stotland
2024-08-23 21:49 ` [PATCH 7/7] arm64: tegra: Create SKU8 AGX Orin board file Dara Stotland
2024-08-24  8:02   ` Krzysztof Kozlowski
2024-08-24 14:56     ` Brad Griffis

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=20240823214957.771297-1-dstotland@nvidia.com \
    --to=dstotland@nvidia.com \
    --cc=bgriffis@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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