From: Hans de Goede <hdegoede@redhat.com>
To: "K Naduvalath, Sumesh" <sumesh.k.naduvalath@intel.com>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>
Cc: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chinnu, Ganapathi" <ganapathi.chinnu@intel.com>,
"Kumar, Nachiketa" <nachiketa.kumar@intel.com>
Subject: Re: [PATCH 1/1] ishtp: Add support for Intel ishtp eclite driver
Date: Thu, 3 Jun 2021 19:05:33 +0200 [thread overview]
Message-ID: <a447321d-79fc-6d2c-4a07-d4a24223c5a5@redhat.com> (raw)
In-Reply-To: <BYAPR11MB3752E4A836546F1F07089249A93C9@BYAPR11MB3752.namprd11.prod.outlook.com>
Hi,
On 6/3/21 6:48 PM, K Naduvalath, Sumesh wrote:
> Thank you Hans for the scrutiny. Please find my comments inline.
<snip>
>>> ISH Firmware (the PSE subsystem) can boot up/reinitialize Every Sx
>>> based on usecase or sometimes PSE is always-on. So the resume path is
>>> asynchronous and unpredictable in this case. Re-initialization and
>>> clean up required if PSE also boot up every Sx and might take good
>>> amount of time (Host can come alive before PSE comes up). Thus using
>> asynchronous reset notification.
>>
>> Ok, so I guess we need to live with the ugly deregister + re-register OpRegion
>> dance for the devices where the PSE is shutdown during suspend.
>>
>> You also write: "sometimes PSE is always-on", what about that case, I assume
>> in this case there will be no reset after resume? So then unregistering the
>> OpRegion handler at suspend (and setting link_ready=false) will be wrong
>> since without the reset the OpRegion handler will never get reinstalled ?
>
> reset is called from bus after every resume. When PSE is always-on, the notification
> comes quicky, where as there reset comes bit later in case of new boot.
Ok, in that case it makes sense to treat the PSE always-on scenario the same
as the scenario where it gets turned off during suspend.
Regards,
Hans
prev parent reply other threads:[~2021-06-03 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 12:04 sumesh.k.naduvalath
2021-05-31 14:54 ` Hans de Goede
2021-06-01 18:24 ` K Naduvalath, Sumesh
2021-06-02 11:19 ` Hans de Goede
2021-06-03 16:48 ` K Naduvalath, Sumesh
2021-06-03 17:05 ` Hans de Goede [this message]
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=a447321d-79fc-6d2c-4a07-d4a24223c5a5@redhat.com \
--to=hdegoede@redhat.com \
--cc=ganapathi.chinnu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=nachiketa.kumar@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumesh.k.naduvalath@intel.com \
/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
all inboxes | Powered by JetHome®