[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251124212106.2068069-1-sjg168@gmail.com>
Date: Tue, 25 Nov 2025 05:21:04 +0800
From: Peter Shen <sjg168@...il.com>
To: devicetree@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
Andrew Jeffery <andrew@...econstruct.com.au>,
Joel Stanley <joel@....id.au>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
peter.shen@....com,
colin.huang2@....com,
Peter Shen <sjg168@...il.com>
Subject: [PATCH v8 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC
This patch series introduces the initial Device Tree support for the
Facebook Anacapa BMC platform, which is based on the Aspeed AST2600 SoC.
It configures the platform-specific peripherals and aliases for OpenBMC
usage.
The series is comprised of two patches:
1. Adds the compatible string for the board to the binding documentation.
2. Adds the main Device Tree Source file for the Anacapa BMC.
Changes in v8:
* Dropped the unused 'pcc_memory' reserved memory region as suggested
by Andrew Jeffery.
* Reordered the 'spi-gpio' properties to group all '-gpios' properties
together for better readability (Andrew Jeffery).
* Moved the 'pinctrl_ncsi3_default' pinctrl group from the board DTS
file to 'arch/arm/boot/dts/aspeed-g6.dtsi' (assuming this dtsi
change is applied separately or already in the base) to make it
available for other platforms (Andrew Jeffery).
* Revised the 'gpio-line-names' for better clarity and alignment with
schematic signal names, avoiding confusion with pin-muxed functions
(Andrew Jeffery).
* Improved the formatting and readability of 'sgpio-line-names' list.
* Removed the unused 'led-2' definition from the 'leds' node.
* Added support for the ADC128D818 sensor to the I2C bus.
* No functional changes in the binding patch (1/2).
* Added clarification for mixed-case signal names (Andrew Jeffery):
The mixed-case names (e.g., FM_CPU0_SYS_RESET_N) in gpio-line-names
are chosen to directly match the signal names used in the hardware
schematics.
This convention is used to maintain strict adherence and clarity when
cross-referencing between the Device Tree and the board design documents.
Peter Shen (2):
dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC
ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed/aspeed-bmc-facebook-anacapa.dts | 1044 +++++++++++++++++
3 files changed, 1046 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-anacapa.dts
--
2.34.1
Powered by blists - more mailing lists