From: Tomas Winkler <tomas.winkler@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: arnd@arndb.de, Alexander Usyskin <alexander.usyskin@intel.com>,
linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [char-misc-next 0/9 RESEND] mei: support for async event notifications
Date: Sun, 26 Jul 2015 09:54:14 +0300 [thread overview]
Message-ID: <1437893663-2068-1-git-send-email-tomas.winkler@intel.com> (raw)
FW has gained new capability where a FW client can asynchronously
notify the host that an event has occurred in its process.
The notification doesn't provide any data and host may need to query
further the FW client in order to get details of the event.
New IOCTLs are introduced for the user space to enable/disable
and consume the event notifications.
The asynchronous nature is provided via poll and fasync.
Alexander Usyskin (1):
mei: bus: add and call callback on notify event
Tomas Winkler (8):
mei: define async notification hbm commands
mei: implement async notification hbm messages
mei: enable async event notifications only from hbm version 2.0
mei: add mei_cl_notify_request command
mei: add a handler that waits for notification on event
mei: add async event notification ioctls
mei: support polling for event notification
mei: implement fasync for event notification
Documentation/ioctl/ioctl-number.txt | 2 +
Documentation/misc-devices/mei/mei.txt | 45 ++++++-
drivers/misc/mei/bus.c | 50 +++++++-
drivers/misc/mei/client.c | 224 +++++++++++++++++++++++++++++++++
drivers/misc/mei/client.h | 8 ++
drivers/misc/mei/debugfs.c | 2 +
drivers/misc/mei/hbm.c | 136 ++++++++++++++++++++
drivers/misc/mei/hbm.h | 2 +
drivers/misc/mei/hw.h | 68 ++++++++++
drivers/misc/mei/interrupt.c | 7 ++
drivers/misc/mei/main.c | 96 ++++++++++++++
drivers/misc/mei/mei_dev.h | 15 +++
drivers/nfc/mei_phy.c | 3 +-
include/linux/mei_cl_bus.h | 4 +
include/uapi/linux/mei.h | 19 +++
15 files changed, 675 insertions(+), 6 deletions(-)
--
2.4.3
next reply other threads:[~2015-07-26 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 6:54 Tomas Winkler [this message]
2015-07-26 6:54 ` [char-misc-next 1/9 RESEND] mei: define async notification hbm commands Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 2/9 RESEND] mei: implement async notification hbm messages Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 3/9 RESEND] mei: enable async event notifications only from hbm version 2.0 Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 4/9 RESEND] mei: add mei_cl_notify_request command Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 5/9 RESEND] mei: add a handler that waits for notification on event Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 6/9 RESEND] mei: add async event notification ioctls Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 7/9 RESEND] mei: support polling for event notification Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 8/9 RESEND] mei: implement fasync " Tomas Winkler
2015-07-26 6:54 ` [char-misc-next 9/9 RESEND] mei: bus: add and call callback on notify event Tomas Winkler
2015-07-26 17:45 ` [char-misc-next 0/9 RESEND] mei: support for async event notifications Greg Kroah-Hartman
2015-07-27 6:36 ` Winkler, Tomas
2015-08-04 0:18 ` Greg Kroah-Hartman
2015-08-04 10:59 ` Winkler, Tomas
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=1437893663-2068-1-git-send-email-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.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®