Hi Conor, On 2026-11-18 17:51, Conor Dooley wrote: > +CC Mark, spi, > > On Wed, Nov 18, 2026 at 04:57:34PM +0800, Wang Yang wrote: > > window, clocks, resets and link configuration. The EC uses this memory > > window rather than the ordinary SPI transfer interface. > > > > The controller implementation is carried as a separate prerequisite so > > that the hardware vendor can review it independently. > > > > Prepared with Codex assistance from the existing DC-linux EC support. > > > > Signed-off-by: Wang Yang > > --- > > .../bindings/bus/spacemit,k3-espi.yaml | 146 ++++++++++++++++++ > > 1 file changed, 146 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/bus/spacemit,k3-espi.yaml > > > > diff --git a/Documentation/devicetree/bindings/bus/spacemit,k3-espi.yaml b/Documentation/devicetree/bindings/bus/spacemit,k3-espi.yaml > > new file mode 100644 > > index 000000000..30985ee0a > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/bus/spacemit,k3-espi.yaml > > @@ -0,0 +1,146 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/bus/spacemit,k3-espi.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: SpacemiT K3 eSPI controller > > How is this "eSPI" different to the eSPI described in fsl,espi.yaml and > implemented by a driver in drivers/spi? eSPI in fsl,espi.yaml is a Freescale (now NXP) SPI controller, it implements a SPI bus. Here eSPI is a bus, replacing the LPC bus, as defined by Intel: https://www.intel.com/content/www/us/en/content-details/841685/enhanced-serial-peripheral-interface-espi-interface-base-specification-for-client-and-server-platforms.html Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net