From: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: joel@jms.id.au, arnd@arndb.de, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com
Subject: Re: [PATCH arm/aspeed/ast2500 v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI
Date: Thu, 25 Jan 2018 10:29:02 +0800 [thread overview]
Message-ID: <b1584518-2938-7faa-cd83-d0245d1ba88f@linux.intel.com> (raw)
In-Reply-To: <20180123084457.GE21463@kroah.com>
On 2018-01-23 16:44, Greg KH wrote:
> On Tue, Jan 16, 2018 at 07:52:32PM +0800, Haiyue Wang 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
>>
>> Signed-off-by: Haiyue Wang <haiyue.wang@linux.intel.com>
>> ---
>> .../devicetree/bindings/misc/aspeed-espi-slave.txt | 20 ++
>> Documentation/misc-devices/espi-slave.rst | 114 +++++++++
> DT files need to be split out into a separate patch so that the DT
> maintainers can properly review them.
>
>> --- a/drivers/misc/Kconfig
>> +++ b/drivers/misc/Kconfig
>> @@ -471,6 +471,17 @@ config VEXPRESS_SYSCFG
>> ARM Ltd. Versatile Express uses specialised platform configuration
>> bus. System Configuration interface is one of the possible means
>> of generating transactions on this bus.
>> +config ASPEED_ESPI_SLAVE
> You need a blank line above this one please.
Fixed.
>> + depends on ARCH_ASPEED || COMPILE_TEST
>> + select REGMAP_MMIO
> Select or depend?
Before, I used "depends on". I was told to to change "select". I'm not
sure which is more better by practice ?
>> + tristate "Aspeed ast2500 eSPI slave device"
>> + ---help---
>> + This allows host to access Baseboard Management Controller (BMC) over the
>> + Enhanced Serial Peripheral Interface (eSPI) bus, which replaces the Low Pin
>> + Count (LPC) bus.
>> +
>> + Its interface supports peripheral, virtual wire, out-of-band, and flash
>> + sharing channels.
> What is the module name?
You means the --help-- description is not clear and specific ?
>>
>> config ASPEED_LPC_CTRL
>> depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
>> diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
>> index 5ca5f64..a1081f4 100644
>> --- a/drivers/misc/Makefile
>> +++ b/drivers/misc/Makefile
>> @@ -52,6 +52,7 @@ obj-$(CONFIG_GENWQE) += genwqe/
>> obj-$(CONFIG_ECHO) += echo/
>> obj-$(CONFIG_VEXPRESS_SYSCFG) += vexpress-syscfg.o
>> obj-$(CONFIG_CXL_BASE) += cxl/
>> +obj-$(CONFIG_ASPEED_ESPI_SLAVE) += aspeed-espi-slave.o
> Why no tab?
Fixed, thanks.
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2018-01-25 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:52 Haiyue Wang
2018-01-23 8:44 ` Greg KH
2018-01-25 2:29 ` Wang, Haiyue [this message]
2018-01-25 12:23 ` Andy Shevchenko
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=b1584518-2938-7faa-cd83-d0245d1ba88f@linux.intel.com \
--to=haiyue.wang@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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
Powered by JetHome