From: Thierry Escande <thierry.escande@collabora.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Benson Leung <bleung@chromium.org>, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] mfd: cros_ec: non-wake host events support
Date: Tue, 14 Feb 2017 20:57:59 +0100 [thread overview]
Message-ID: <1487102282-12259-1-git-send-email-thierry.escande@collabora.com> (raw)
Hi,
This patchset adds support for non-wake host events. These are events
sent by the EC that should not wakeup the device.
This patchset also adds 2 fixes in cros_ec regarding a possible deadlock
and an error code returned when it should not.
This patchset depends on [1] to compile
v2:
- Check for wake_event state in cros_ec_get_next_event()
- Remove cros_ec_get_host_event() implementation already
introduced by [1]
[1] https://lkml.org/lkml/2017/1/19/278
Gwendal Grignou (1):
cros_ec: Fix deadlock when EC is not responsive at probe
Shawn Nematbakhsh (1):
cros_ec: Don't signal wake event for non-wake host events
Thierry Escande (1):
cros_ec: Don't return error when checking command version
drivers/mfd/cros_ec.c | 13 +++--
drivers/platform/chrome/cros_ec_proto.c | 96 ++++++++++++++++++++++++++++++---
include/linux/mfd/cros_ec.h | 16 +++++-
3 files changed, 115 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-14 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 19:57 Thierry Escande [this message]
2017-02-14 19:58 ` [PATCH v2 1/3] cros_ec: Don't return error when checking command version Thierry Escande
2017-06-27 15:35 ` Benson Leung
2017-02-14 19:58 ` [PATCH v2 2/3] cros_ec: Fix deadlock when EC is not responsive at probe Thierry Escande
2017-06-27 15:36 ` Benson Leung
2017-02-14 19:58 ` [PATCH v2 3/3] cros_ec: Don't signal wake event for non-wake host events Thierry Escande
2017-03-14 13:56 ` Lee Jones
2017-06-27 16:23 ` Benson Leung
2017-07-03 11:46 ` Lee Jones
2017-07-05 20:11 ` Benson Leung
2017-07-06 7:12 ` Lee Jones
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=1487102282-12259-1-git-send-email-thierry.escande@collabora.com \
--to=thierry.escande@collabora.com \
--cc=bleung@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®