Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	<arm@kernel.org>, <soc@kernel.org>
Cc: Tero Kristo <kristo@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Subject: [GIT PULL] arm64: dts: TI K3 fixes for v6.11
Date: Tue, 6 Aug 2024 07:26:59 -0500	[thread overview]
Message-ID: <20240806122659.vmasq2qjy6457bbs@peroxide> (raw)

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

Hi SoC maintainers,

Please find DT fixups for the v6.11 rc cycle - This tag includes the
previous late PR
https://patchwork.kernel.org/project/linux-soc/patch/aacd1e96-9ff4-4222-9f4d-29e63041f7fb@ti.com/

The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:

  Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-k3-dt-fixes-for-v6.11

for you to fetch changes up to 402d336053a5d827c70ec11109e079811e86e0e8:

  arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs (2024-08-06 06:39:23 -0500)

----------------------------------------------------------------
Devicetree fixes for TI K3 platforms for v6.11

Critical fixes for the following:
* j784s4: Fix for McASP DMA map
* J722s/AM62p: GPIO ranges fixes
* k3-am62-verdin-dahlia: sleep-moci fixes for deep-sleep (revert)

----------------------------------------------------------------
Andrew Halaney (2):
      arm64: dts: ti: k3-j784s4-evm: Assign only lanes 0 and 1 to PCIe1
      arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references

Francesco Dolcini (1):
      arm64: dts: ti: k3-am62-verdin-dahlia: Keep CTRL_SLEEP_MOCI# regulator on

Jared McArthur (3):
      arm64: dts: ti: k3-am62p: Add gpio-ranges for mcu_gpio0
      arm64: dts: ti: k3-am62p: Fix gpio-range for main_pmx0
      arm64: dts: ti: k3-j722s: Fix gpio-range for main_pmx0

Nishanth Menon (1):
      Merge tag 'ti-k3-dt-for-v6.11-part2' into ti-k3-dts-next

Parth Pancholi (1):
      arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs

 arch/arm64/boot/dts/ti/k3-am62-verdin-dahlia.dtsi  | 22 -------------------
 arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi         |  6 ------
 .../boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi     |  2 ++
 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi          |  3 ++-
 arch/arm64/boot/dts/ti/k3-j722s-main.dtsi          |  3 ++-
 arch/arm64/boot/dts/ti/k3-j784s4-evm.dts           | 25 +++++++---------------
 arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi         |  4 ++--
 7 files changed, 16 insertions(+), 49 deletions(-)
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2024-08-06 12:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240806122659.vmasq2qjy6457bbs@peroxide \
    --to=nm@ti.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=soc@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