public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Peter Shen <sjg168@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Joel Stanley <joel@jms.id.au>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	peter.shen@amd.com, colin.huang2@amd.com,
	Peter Shen <sjg168@gmail.com>
Subject: [PATCH v8 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC
Date: Tue, 25 Nov 2025 05:21:04 +0800	[thread overview]
Message-ID: <20251124212106.2068069-1-sjg168@gmail.com> (raw)

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



             reply	other threads:[~2025-11-24 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 21:21 Peter Shen [this message]
2025-11-24 21:21 ` [PATCH v8 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC Peter Shen
2025-11-24 21:21 ` [PATCH v8 2/2] ARM: dts: aspeed: Add Device Tree " Peter Shen
2025-11-26 23:38   ` Andrew Jeffery

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=20251124212106.2068069-1-sjg168@gmail.com \
    --to=sjg168@gmail.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=colin.huang2@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.shen@amd.com \
    --cc=robh@kernel.org \
    /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