From: Jiri Kosina <jikos@kernel.org>
To: Zhang Lixu <lixu.zhang@intel.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
srinivas.pandruvada@linux.intel.com,
benjamin.tissoires@redhat.com
Subject: Re: [PATCH 0/2] hid: intel-ish-hid: ipc: enable OOB support for EHL
Date: Wed, 6 Jan 2021 17:20:43 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2101061720310.13752@cbobk.fhfr.pm> (raw)
In-Reply-To: <20201216063640.4086068-1-lixu.zhang@intel.com>
On Wed, 16 Dec 2020, Zhang Lixu wrote:
> The EHL (Elkhart Lake) based platforms provide a OOB (Out of band)
> service, which allows wakup device when the system is in S5 (Soft-Off
> state). This OOB service can be enabled/disabled from BIOS settings.
>
> These two patches is to enable this feature for EHL platform.
>
> We have tested these patches on both ISH platforms and EHL platforms,
> it works fine.
>
> Zhang Lixu (2):
> hid: intel-ish-hid: ipc: finish power flow for EHL OOB
> hid: intel-ish-hid: ipc: Address EHL Sx resume issues
>
> drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 +
> drivers/hid/intel-ish-hid/ipc/ipc.c | 27 +++++++++++++
> drivers/hid/intel-ish-hid/ipc/pci-ish.c | 54 ++++++++++++++++++++++++-
> 3 files changed, 81 insertions(+), 1 deletion(-)
Applied to hid.git#for-5.12/intel-ish.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2021-01-06 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:36 [PATCH 0/2] hid: intel-ish-hid: ipc: enable OOB support for EHL Zhang Lixu
2020-12-16 6:36 ` [PATCH 1/2] hid: intel-ish-hid: ipc: finish power flow for EHL OOB Zhang Lixu
2021-01-04 15:59 ` Srinivas Pandruvada
2020-12-16 6:36 ` [PATCH 2/2] hid: intel-ish-hid: ipc: Address EHL Sx resume issues Zhang Lixu
2021-01-04 16:00 ` Srinivas Pandruvada
2021-01-04 15:12 ` [PATCH 0/2] hid: intel-ish-hid: ipc: enable OOB support for EHL Jiri Kosina
2021-01-04 16:01 ` Srinivas Pandruvada
2021-01-05 2:42 ` Zhang, Lixu
2021-01-06 16:20 ` Jiri Kosina [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=nycvar.YFH.7.76.2101061720310.13752@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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;
as well as URLs for NNTP newsgroup(s).