Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-04 01:08, Wang, Haiyue wrote: On 2018-01-04 00:43, Wang, Haiyue wrote: On 2018-01-03 23:17, Arnd Bergmann wrote: On Wed, Jan 3, 2018 at 3:21 AM, Wang, Haiyue wrote: On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang,

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-04 01:08, Wang, Haiyue wrote: On 2018-01-04 00:43, Wang, Haiyue wrote: On 2018-01-03 23:17, Arnd Bergmann wrote: On Wed, Jan 3, 2018 at 3:21 AM, Wang, Haiyue wrote: On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: On 2018-01-02

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Arnd Bergmann
On Wed, Jan 3, 2018 at 3:21 AM, Wang, Haiyue wrote: > On 2018-01-03 00:23, Arnd Bergmann wrote: >> On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue >> wrote: >>> On 2018-01-02 23:13, Arnd Bergmann wrote: > > On 2017-12-31 07:10, Arnd

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Arnd Bergmann
On Wed, Jan 3, 2018 at 3:21 AM, Wang, Haiyue wrote: > On 2018-01-03 00:23, Arnd Bergmann wrote: >> On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue >> wrote: >>> On 2018-01-02 23:13, Arnd Bergmann wrote: > > On 2017-12-31 07:10, Arnd Bergmann wrote: On the slave side, it seems that

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Arnd Bergmann
On Wed, Jan 3, 2018 at 3:32 PM, Mark Brown wrote: > On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: > >> Should send to like this ? Because I add patch for Aspeed chip: > >> ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c >> Joel Stanley

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Arnd Bergmann
On Wed, Jan 3, 2018 at 3:32 PM, Mark Brown wrote: > On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: > >> Should send to like this ? Because I add patch for Aspeed chip: > >> ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c >> Joel Stanley (maintainer:ARM/ASPEED MACHINE

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-03 22:32, Mark Brown wrote: On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: Should send to like this ? Because I add patch for Aspeed chip: ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c Joel Stanley (maintainer:ARM/ASPEED MACHINE

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-03 22:32, Mark Brown wrote: On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: Should send to like this ? Because I add patch for Aspeed chip: ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c Joel Stanley (maintainer:ARM/ASPEED MACHINE SUPPORT) Arnd Bergmann

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Mark Brown
On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: > Should send to like this ? Because I add patch for Aspeed chip: > ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c > Joel Stanley (maintainer:ARM/ASPEED MACHINE SUPPORT) > Arnd Bergmann

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Mark Brown
On Wed, Jan 03, 2018 at 10:28:22PM +0800, Wang, Haiyue wrote: > Should send to like this ? Because I add patch for Aspeed chip: > ./scripts/get_maintainer.pl drivers/misc/aspeed-lpc-snoop.c > Joel Stanley (maintainer:ARM/ASPEED MACHINE SUPPORT) > Arnd Bergmann (supporter:CHAR and MISC DRIVERS)

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-03 19:38, Mark Brown wrote: On Sun, Dec 31, 2017 at 12:10:51AM +0100, Arnd Bergmann wrote: On Fri, Dec 29, 2017 at 2:53 AM, Haiyue Wang wrote: When PCH works under eSPI mode, the PMC (Power Management Controller) in PCH is waiting for SUS_ACK from BMC

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Wang, Haiyue
On 2018-01-03 19:38, Mark Brown wrote: On Sun, Dec 31, 2017 at 12:10:51AM +0100, Arnd Bergmann wrote: On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Mark Brown
On Sun, Dec 31, 2017 at 12:10:51AM +0100, Arnd Bergmann wrote: > On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-03 Thread Mark Brown
On Sun, Dec 31, 2017 at 12:10:51AM +0100, Arnd Bergmann wrote: > On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Wang, Haiyue
On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Wang, Haiyue
On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both for the transport (eSPI

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Arnd Bergmann
On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: > On 2018-01-02 23:13, Arnd Bergmann wrote: >>> On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both for the transport (eSPI

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Arnd Bergmann
On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: > On 2018-01-02 23:13, Arnd Bergmann wrote: >>> On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both for the transport (eSPI register level interface for

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Wang, Haiyue
On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Wang, Haiyue
On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Arnd Bergmann
> On 2017-12-31 07:10, Arnd Bergmann wrote: > > On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2018-01-02 Thread Arnd Bergmann
> On 2017-12-31 07:10, Arnd Bergmann wrote: > > On Fri, Dec 29, 2017 at 2:53 AM, 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.

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2017-12-30 Thread Arnd Bergmann
On Fri, Dec 29, 2017 at 2:53 AM, 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

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2017-12-30 Thread Arnd Bergmann
On Fri, Dec 29, 2017 at 2:53 AM, 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

[PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2017-12-28 Thread Haiyue Wang
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,

[PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

2017-12-28 Thread Haiyue Wang
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,