linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.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>,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Davis <afd@ti.com>
Subject: [PATCH 0/7] Add MAC eFuse nodes to sys config areas
Date: Fri, 28 Jun 2024 10:15:11 -0500	[thread overview]
Message-ID: <20240628151518.40100-1-afd@ti.com> (raw)

Hello all,

Patches are all mostly the same but split by platform, context is in
the patches.

End result is fewer DTB check warnings, some platforms now have 0 :)

This series is a replacement for this patch[0].

Thanks,
Andrew

[0] https://lore.kernel.org/lkml/f589fcea70004cae1c822871023ade86723bb1e3.1719376928.git.jan.kiszka@siemens.com/

Andrew Davis (7):
  arm64: dts: ti: k3-am65: Add cpsw-mac-efuse node to mcu_conf
  arm64: dts: ti: k3-j7200: Add cpsw-mac-efuse node to mcu_conf
  arm64: dts: ti: k3-j721e: Add cpsw-mac-efuse node to mcu_conf
  arm64: dts: ti: k3-j721s2: Add cpsw-mac-efuse node to mcu_conf
  arm64: dts: ti: k3-j784s4: Add cpsw-mac-efuse node to mcu_conf
  arm64: dts: ti: k3-am62a: Add cpsw-mac-efuse node to wkup_conf
  arm64: dts: ti: k3-am62: Add cpsw-mac-efuse node to wkup_conf

 arch/arm64/boot/dts/ti/k3-am62-main.dtsi         |  2 +-
 arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi       |  5 +++++
 arch/arm64/boot/dts/ti/k3-am62a-main.dtsi        |  2 +-
 arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi      | 10 +++++++---
 arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi          | 12 ++++++++----
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi  | 14 +++++++++-----
 arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi  | 12 ++++++++----
 arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 12 ++++++++----
 arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 14 +++++++++-----
 9 files changed, 56 insertions(+), 27 deletions(-)

-- 
2.39.2



             reply	other threads:[~2024-06-28 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 15:15 Andrew Davis [this message]
2024-06-28 15:15 ` [PATCH 1/7] arm64: dts: ti: k3-am65: Add cpsw-mac-efuse node to mcu_conf Andrew Davis
2024-06-28 15:15 ` [PATCH 2/7] arm64: dts: ti: k3-j7200: " Andrew Davis
2024-06-28 15:15 ` [PATCH 3/7] arm64: dts: ti: k3-j721e: " Andrew Davis
2024-06-28 15:15 ` [PATCH 4/7] arm64: dts: ti: k3-j721s2: " Andrew Davis
2024-06-28 15:15 ` [PATCH 5/7] arm64: dts: ti: k3-j784s4: " Andrew Davis
2024-06-28 15:15 ` [PATCH 6/7] arm64: dts: ti: k3-am62a: Add cpsw-mac-efuse node to wkup_conf Andrew Davis
2024-06-28 15:15 ` [PATCH 7/7] arm64: dts: ti: k3-am62: " Andrew Davis
2024-07-03  4:32 ` [PATCH 0/7] Add MAC eFuse nodes to sys config areas Vignesh Raghavendra

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=20240628151518.40100-1-afd@ti.com \
    --to=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jan.kiszka@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;
as well as URLs for NNTP newsgroup(s).