qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Kane Chen <kane_chen@aspeedtech.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Steven Lee <steven_lee@aspeedtech.com>,
	Troy Lee <leetroy@gmail.com>,
	Jamin Lin <jamin_lin@aspeedtech.com>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Joel Stanley <joel@jms.id.au>,
	"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: troy_lee@aspeedtech.com
Subject: Re: [PATCH v2 00/17] hw/arm/aspeed: AST1700 LTPI support and device hookups
Date: Wed, 5 Nov 2025 11:27:08 +0100	[thread overview]
Message-ID: <5e69d550-fc52-43e0-9437-cc8600fc65c7@redhat.com> (raw)
In-Reply-To: <20251105035859.3709907-1-kane_chen@aspeedtech.com>

On 11/5/25 04:58, Kane Chen wrote:
> From: Kane-Chen-AS <kane_chen@aspeedtech.com>
> 
> Hi all,
> 
> LTPI (LVDS Tunneling Protocol & Interface) is defined in the OCP DC-SCM
> 2.0 specification (see Figure 2):
> https://www.opencompute.org/documents/ocp-dc-scm-2-0-ltpi-ver-1-0-pdf
> 
> LTPI provides a protocol and physical interface for tunneling various
> low-speed signals between the Host Processor Module (HPM) and the
> Satellite Controller Module (SCM). In Figure 2 of the specification,
> the AST27x0 SoC (left) integrates two LTPI controllers, allowing it to
> connect to up to two AST1700 boards. On the other side, the AST1700
> consolidates HPM FPGA functions and multiple peripheral interfaces
> (GPIO, UART, I2C, I3C, etc.) onto a single board.
> 
> Because the AST1700 exposes additional I/O interfaces (GPIO, I2C, I3C,
> and others), it acts as an I/O expander. Once connected over LTPI,
> the AST27x0 can control additional downstream devices through this link.
> 
> This patch series introduces a basic LTPI controller model and wires it
> into the AST27x0 SoC. It also adds the AST1700-specific LTPI expander
> device and gradually connects common peripherals on the AST1700 model.
> For blocks that are not yet functionally implemented (I3C, SGPIOM, PWM),
> their MMIO regions are modeled as unimplemented devices to reserve
> address space and make the missing functionality explicit, ensuring that
> guest probing remains stable.
> 
> In the official release images, the AST1700 functions are not included
> by default. To test the AST1700-related functionality, please include
> the following DTS files for probing:
> https://github.com/AspeedTech-BMC/linux/blob/aspeed-master-v6.6/arch/arm64/boot/dts/aspeed/aspeed-ltpi0.dtsi
> https://github.com/AspeedTech-BMC/linux/blob/aspeed-master-v6.6/arch/arm64/boot/dts/aspeed/aspeed-ltpi1.dtsi
> 
> After including these DTS files in the BMC image, you can verify LTPI
> functionality using the following scenarios:
> 
> 1. In U-Boot:
>     Run the ltpi command to trigger the LTPI connection and display the
>     current connection status.
> 2. In BMC Linux:
>     Run i2cdetect -y <16-38> to scan and test the I2C buses exposed by
>     the AST1700.
> 
> Any feedback or suggestions are appreciated!
> 

Thanks for the update. The models look better. Let's consider them
for QEMU 11.0.


Did you run "make check" and "make check-functional" ?

Thanks,

C.



  parent reply	other threads:[~2025-11-05 10:28 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  3:58 [PATCH v2 00/17] hw/arm/aspeed: AST1700 LTPI support and device hookups Kane Chen via
2025-11-05  3:58 ` [PATCH v2 01/17] hw/arm/aspeed: Add LTPI controller Kane Chen via
2025-11-07 13:07   ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 02/17] hw/arm/aspeed: Attach LTPI controller to AST27X0 platform Kane Chen via
2025-11-07 13:08   ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 03/17] hw/arm/aspeed: Add AST1700 LTPI expander device model Kane Chen via
2025-11-07 13:10   ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 04/17] hw/arm/aspeed: Integrate AST1700 device into AST27X0 Kane Chen via
2025-11-07 13:30   ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 05/17] hw/arm/aspeed: Integrate interrupt controller for AST1700 Kane Chen via
2025-11-07 13:36   ` Cédric Le Goater
2025-11-10  2:09     ` Kane Chen
2025-11-05  3:58 ` [PATCH v2 06/17] hw/arm/aspeed: Attach LTPI controller to AST1700 model Kane Chen via
2025-11-07 13:36   ` Cédric Le Goater
2025-11-10  2:05     ` Kane Chen
2025-11-05  3:58 ` [PATCH v2 07/17] hw/arm/aspeed: Attach UART device " Kane Chen via
2025-11-10 16:04   ` Cédric Le Goater
2025-11-11  5:46     ` Jan Kiszka
2025-11-05  3:58 ` [PATCH v2 08/17] hw/arm/aspeed: Attach SRAM " Kane Chen via
2025-11-10 16:08   ` Cédric Le Goater
2025-11-11  1:42     ` Kane Chen
2025-11-05  3:58 ` [PATCH v2 09/17] hw/arm/aspeed: Attach SPI " Kane Chen via
2025-11-05 21:20   ` Nabih Estefan
2025-11-06 10:11     ` Kane Chen
2025-11-06 10:21       ` Cédric Le Goater
2025-11-07  5:39         ` Kane Chen
2025-11-07  7:54           ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 10/17] hw/arm/aspeed: Attach ADC " Kane Chen via
2025-11-05  3:58 ` [PATCH v2 11/17] hw/arm/aspeed: Attach SCU " Kane Chen via
2025-11-05  3:58 ` [PATCH v2 12/17] hw/arm/aspeed: Attach GPIO " Kane Chen via
2025-11-05  3:58 ` [PATCH v2 13/17] hw/arm/aspeed: Attach I2C " Kane Chen via
2025-11-05  3:58 ` [PATCH v2 14/17] hw/arm/aspeed: Attach WDT " Kane Chen via
2025-11-05  3:58 ` [PATCH v2 15/17] hw/arm/aspeed: Model AST1700 I3C block as unimplemented device Kane Chen via
2025-11-07  8:06   ` Cédric Le Goater
2025-11-07  8:41     ` Kane Chen
2025-11-05  3:58 ` [PATCH v2 16/17] hw/arm/aspeed: Model AST1700 SGPIOM " Kane Chen via
2025-11-10 16:14   ` Cédric Le Goater
2025-11-11  1:33     ` Kane Chen
2025-11-12  7:06       ` Cédric Le Goater
2025-11-05  3:58 ` [PATCH v2 17/17] hw/arm/aspeed: Model AST1700 PWM " Kane Chen via
2025-11-10 16:16   ` Cédric Le Goater
2025-11-11  1:27     ` Kane Chen
2025-11-05 10:27 ` Cédric Le Goater [this message]
2025-11-05 10:34   ` [PATCH v2 00/17] hw/arm/aspeed: AST1700 LTPI support and device hookups Kane Chen
2025-11-10 16:43 ` Cédric Le Goater
2025-11-11  2:32   ` Kane Chen

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=5e69d550-fc52-43e0-9437-cc8600fc65c7@redhat.com \
    --to=clg@redhat.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=jamin_lin@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=kane_chen@aspeedtech.com \
    --cc=leetroy@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=steven_lee@aspeedtech.com \
    --cc=troy_lee@aspeedtech.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).