From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.127.231.37 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795079172; b=rgaR64n8RW7NZpxoomRGX5TAmlFjXlGkIESS0YvQKRNX+ZBsyCbO/x6rtdfO9weIfPTl tzY1Pt8aQwECxM1KFMaM/aU3lUZgGpZZzYNYfZpJdZTLpN9C/WZuMNmgzv5/+VzSw+m5P TIs7kKqN5ioHb9yVf/gXSkRMlEPaRCXO8fbLssgMekRO4YJSnECKQw0zP5KLnbJX/w5vU 6GFLf1unq9vMkXH7ezSfrbngScCzYHjGazGncAe+KBTBzLGsf11w1MdRJAtk8Xu3sMbo7 Y2FL5CsszqqhBqFmpS1ThCFBQfVK/3KKncQODsTHRoO/BX+eW8ck8Hw8bL4AkWqhCMA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795079172; h=DMARC-Filter:DKIM-Signature:X-Original-From:X-Mailer:Received:Cc: From:Subject:Mime-Version:X-Lms-Return-Path:Message-Id: Content-Transfer-Encoding:Content-Type:To:Date:References: In-Reply-To; bh=4HX5+/MoRFuL5friO42awFlJeeVyzzPj59afEXfj3X4=; b=aNb9OCjjopectYb63nCp+hqYE4cE0T1ryBHMolH1Xx/HA8YNklgRP1X4kk3uLVKuWYje ZJdzZLU4UEu3ppBQHxvNygivkyqHLqeEyfKOmPRnSq/fTC+3Jt/bgEMlXxMt476BEnhQO k38/SonU0SocPkN8MvJZuKogmYBmLb93wD2eCc8SNmcr8f3nyuDnAsN6/bk5a8wpugFEL 5QwtiGcZk/QFd/tvWhlbxDQ1xI16Ud8XNsfdZuurh5BQN7MFMCFM1s/yhBqf6px73UcRx u5hkDH45PWTppYFgL8RyvHdcEcfNOenwsVDw3ZOxSCVTrjS5URG14jg/X7Rn2UHwdAA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=deepcomputing.io; spf=pass smtp.mailfrom=deepcomputing.io; dkim=pass header.d=deepcomputing-io.20200927.dkim.feishu.cn header.i=@deepcomputing-io.20200927.dkim.feishu.cn header.a=rsa-sha256 header.s=s1 header.b=grjpUPxq; arc=none smtp.remote-ip=209.127.231.37 Received: from va-2-37.ptr.blmpb.com (va-2-37.ptr.blmpb.com [209.127.231.37]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9DEA6606A32C for ; Thu, 19 Nov 2026 09:06:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 9DEA6606A32C Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=deepcomputing.io Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=deepcomputing.io Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=deepcomputing-io.20200927.dkim.feishu.cn header.i=@deepcomputing-io.20200927.dkim.feishu.cn header.a=rsa-sha256 header.s=s1 header.b=grjpUPxq DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=s1; d=deepcomputing-io.20200927.dkim.feishu.cn; t=1795079166; h=from:subject:mime-version:from:date:message-id:subject:to:cc: reply-to:content-type:mime-version:in-reply-to:message-id; bh=4HX5+/MoRFuL5friO42awFlJeeVyzzPj59afEXfj3X4=; b=grjpUPxqeB05GIa1dPz1KJ9Rbrca6OpaoKotakoD7K3u5Yb3UX0SyVmQkUH8ft8bPaoy1Q 7JzTCIsAwNlQYLTeYnFHnVv2n2GBbtfAmLO4YWi+GWGJldsjpEX8JKGZL1w+gYzEGcHQee tw+CLuKJejl+sKk+3iXjU0tjS/h7FSLqLLukiFb4hxRsYMQ8xzym9o++8eeRW30QVYvi0y YrNf3Ok4ZCFfuxPdO8xU0MVxZbxxjnzXeonBG4rWUxIp/wIyvXuMWFjjexsi09teMvSIWO jybF2WA6Ag12mHLIPmJNUWjpL5Y4z+ak1MAMgufr5w+AlGg7L/NQcHKbm6jqEw== X-Original-From: Wang Yang X-Mailer: git-send-email 2.43.0 Received: from ubuntu.. ([183.23.99.162]) by smtp.feishu.cn with ESMTPS; Thu, 19 Nov 2026 17:06:02 +0800 Cc: "Yixun Lan" , "Benson Leung" , "Troy Mitchell" , "Tzung-Bi Shih" , "Guenter Roeck" , "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Paul Walmsley" , "Palmer Dabbelt" , "Albert Ou" , "Alexandre Ghiti" , "Sandie Cao" , , , , , , , From: "Wang Yang" Subject: Re: [PATCH 1/9] dt-bindings: bus: Add SpacemiT K3 eSPI controller X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list Mime-Version: 1.0 X-Lms-Return-Path: Message-Id: <20261119090553.1886090-1-yang.wang@deepcomputing.io> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 To: "Conor Dooley" , "Aurelien Jarno" Date: Thu, 19 Nov 2026 17:05:53 +0800 References: <20261118085742.1817536-1-yang.wang@deepcomputing.io> <20261118085742.1817536-2-yang.wang@deepcomputing.io> <20261118-backdrop-scrap-1bee34e06336@spud> In-Reply-To: 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