Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752927AbeACO22 (ORCPT + 1 other); Wed, 3 Jan 2018 09:28:28 -0500 Received: from mga07.intel.com ([134.134.136.100]:62782 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751364AbeACO21 (ORCPT ); Wed, 3 Jan 2018 09:28:27 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,501,1508828400"; d="scan'208";a="6938573" Subject: Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI To: Mark Brown , Arnd Bergmann Cc: Joel Stanley , gregkh , Linux Kernel Mailing List , linux-spi References: <1514512387-27113-1-git-send-email-haiyue.wang@linux.intel.com> <20180103113805.GD5603@sirena.org.uk> From: "Wang, Haiyue" Message-ID: <004d3017-5477-ec42-c78a-aba0ca0621bc@linux.intel.com> Date: Wed, 3 Jan 2018 22:28:22 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180103113805.GD5603@sirena.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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 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 > More generally: > > As documented in SubmittingPatches please send patches to the > maintainers for the code you would like to change. The normal kernel > workflow is that people apply patches from their inboxes, if they aren't > copied they are likely to not see the patch at all and it is much more > difficult to apply patches. 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) Greg Kroah-Hartman (supporter:CHAR and MISC DRIVERS) linux-kernel@vger.kernel.org (open list)