From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.127.231.38 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795079172; b=P0oSWNEed0rhbyMC5FGD6VdWjZBCr7crgoh26EaAyBCsKZFT2Oow8pPlnMqlivbAmZg3 ryyTrBRMy0/jOxxtlJn8IgyVRhYbROdNkP7OuZX3yJ8ayg3C7n1I0lsi4g+upSBPR6hb7 Nd/mTuQeoDTy6QLoGtM2jeAI6sJ5Vux5jqB5sMPhEkSYCXkE3IlUSMfffF+SrS3M2DEW7 j/056RmjqM6AV2Febr/+3CtWDr/NH+l2jqZu351/c8aEnRIg+Te8fmUbO6sEMM5BeMf4S yyqPK11L4GNY5YCm/uPmJxwNCDyUCb8NLchwSSJYxIp1DNU4fjluJ07SvUYSxHVMj2A== 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=Uy+4QRMccP8bmUd6p/yNQy9WwT9L+aidfLwdGZHU6T0Qbe7RVhQDxI0v6zkTX8VOamIp 4HA4o78RXv2CQrbhCqcC4E1YgX4yaDEpBt67fAMUcLwAhOEuA4CJ2U9BDqWe3BsvUouZ5 7/EcafnKMoHmS6pbWLLc2MjUKOx/ocX5/9QCTsn5DCNQvwvAa0HAwDjlNaLfUAh32lgMd ne3LY/k59BSUcMZwJOBV2wdU8Zuo2LbDIBq/88eog185WO0Nk5gzNVyP7IpTglHEgIgfl hipbgocY35edItpICjkTqsPuObgDFUyzyXJPbRspkkYmrMRMnQKv/nI71KIJ/ZtuGiQ== 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.38 Received: from va-2-38.ptr.blmpb.com (va-2-38.ptr.blmpb.com [209.127.231.38]) (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 33505606A320 for ; Thu, 19 Nov 2026 09:06:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 33505606A320 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: devicetree@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