public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Joel Stanley <joel@jms.id.au>,
	gregkh <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI
Date: Mon, 1 Jan 2018 01:04:48 +0800	[thread overview]
Message-ID: <742d4e69-0af9-cafe-67d1-ad9003757c46@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a2nZzc22FgupGjGeS7uQkrxH_W7=T7m_foejDMHtp70_w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

Hi Arnd,

Thanks for your reply. Happy new year! :-)

On 2017-12-31 07:10, Arnd Bergmann wrote:
> On Fri, Dec 29, 2017 at 2:53 AM, Haiyue Wang
> <haiyue.wang@linux.intel.com> wrote:
>> When PCH works under eSPI mode, the PMC (Power Management Controller) in
>> PCH is waiting for SUS_ACK from BMC after it alerts SUS_WARN. It is in
>> dead loop if no SUS_ACK assert. This is the basic requirement for the BMC
>> works as eSPI slave.
>>
>> Also for the host power on / off actions, from BMC side, the following VW
>> (Virtual Wire) messages are done in firmware:
>> 1. SLAVE_BOOT_LOAD_DONE / SLAVE_BOOT_LOAD_STATUS
>> 2. SUS_ACK
>> 3. OOB_RESET_ACK
>> 4. HOST_RESET_ACK
> I have not looked at the driver contents yet, but I'm adding the SPI
> maintainer and
> mailing list to Cc here for further discussion. Can you clarify how
> the eSPI slave
> mode relates to SPI slaves that we already support? I was under the impression
> that the difference between SPI and eSPI is mainly on the master side, but that
> any SPI slave can also act as an eSPI slave. Would this driver fit into the SPI
> slave framework, possibly with some extensions to the generic abstraction?
In simple word, the eSPI uses the SPI interface pin definition, but it 
will replace Low Pin Count (LPC)
interface. From its name, sure, it will confuse you! ;-)
> It also seems rather inflexible to have a single driver that is responsible both
> for the transport (eSPI register level interface for ASPEED) and the high-level
> protocol (talking to an Intel PCH), since either half of the work could be
> done elsewhere, using either a different eSPI slave implementation, or
> a different
> host architecture)
Yes, eSPI has the architecture such as transaction layer, link Layer; 
all of it is about the **silicon**
design. That's why I put the driver under /misc directory, not /spi 
directory.

>         Arnd

---
BR,

Haiyue

[-- Attachment #2: Type: text/html, Size: 3296 bytes --]

  reply	other threads:[~2017-12-31 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29  1:53 [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI Haiyue Wang
2017-12-30 23:10 ` Arnd Bergmann
2017-12-31 17:04   ` Wang, Haiyue [this message]
2017-12-31 17:08   ` Wang, Haiyue
2018-01-02 15:13     ` Arnd Bergmann
2018-01-02 15:36       ` Wang, Haiyue
2018-01-02 16:23         ` Arnd Bergmann
2018-01-03  2:21           ` Wang, Haiyue
2018-01-03 15:17             ` Arnd Bergmann
2018-01-03 16:43               ` Wang, Haiyue
2018-01-03 17:08                 ` Wang, Haiyue
2018-01-04  0:11                   ` Wang, Haiyue
2018-01-03 11:38   ` Mark Brown
2018-01-03 14:28     ` Wang, Haiyue
2018-01-03 14:32       ` Mark Brown
2018-01-03 14:34         ` Wang, Haiyue
2018-01-03 15:05         ` Arnd Bergmann
2018-01-03 16:48           ` Wang, Haiyue

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=742d4e69-0af9-cafe-67d1-ad9003757c46@linux.intel.com \
    --to=haiyue.wang@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /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