Re: [PATCH 1/9] dt-bindings: bus: Add SpacemiT K3 eSPI controller
From: Wang Yang
Date: Thu Nov 19 2026 - 04:06:31 EST
Hi Conor, Aurelien,
> How is this "eSPI" different to the eSPI described in fsl,espi.yaml and
> implemented by a driver in drivers/spi?
Thank you, Aurelien, for clarifying this. K3 uses the Intel-defined
eSPI interface intended to replace LPC. It is a different protocol from the
Freescale/NXP SPI controller described by fsl,espi.yaml.
On K3, the controller exposes a CPU-accessible window for the eSPI
Peripheral Channel. The EC client accesses its command, response
and memory-map regions through this window, rather than exchanging
ordinary SPI messages.
The proposed controller driver handles clocks, resets, link
configuration and window setup. The EC transport handles the EC
register mapping and host commands. The distinction is therefore
the protocol and access model, rather than the use of MMIO itself.
I will make the Intel eSPI terminology and this access model
explicit in the binding description.
Regards,
Wang Yang