From: Sudeep Holla <sudeep.holla@kernel.org>
To: SoC Team <soc@lists.linux.dev>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Arnd Bergmann <arnd@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>
Subject: [GIT PULL] arm64: dts: fvp/juno: Updates for v7.4
Date: Mon, 28 Sep 2026 07:50:47 +0100 [thread overview]
Message-ID: <20260928065048.2492112-1-sudeep.holla@kernel.org> (raw)
Hi ARM SoC Team,
Please pull !
Regards,
Sudeep
-->8
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/juno-updates-7.4
for you to fetch changes up to d8e88ad6f769ec55d3d8510dc53c2b08ddfea645:
arm64: dts: fvp: Add additional PCIe memory region (2026-09-16 09:20:29 +0100)
----------------------------------------------------------------
Arm FVP/Juno device tree updates for v7.4
Three updates to the FVP RevC device tree:
- Add the missing CPU topology information by describing the eight
CPUs as two clusters of four in cpu-map.
- Add the EL2 Generic Watchdog control and refresh frames.
- Add a 4 GiB PCIe memory window, matching the range advertised
by the ACPI description.
----------------------------------------------------------------
Pierre Gondois (3):
arm64: dts: fvp: Add cpu-map property
arm64: dts: fvp: Add EL2 Generic watchdog
arm64: dts: fvp: Add additional PCIe memory region
arch/arm64/boot/dts/arm/fvp-base-revc.dts | 42 ++++++++++++++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)
next reply other threads:[~2026-09-28 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 6:50 Sudeep Holla [this message]
2026-10-01 12:18 ` [GIT PULL] arm64: dts: fvp/juno: Updates for v7.4 Krzysztof Kozlowski
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=20260928065048.2492112-1-sudeep.holla@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=arnd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=soc@lists.linux.dev \
/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