From: Tomas Winkler <tomas.winkler@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [char-misc-next 0/4] mei: bus: rx fixes
Date: Wed, 16 Nov 2016 22:51:26 +0200 [thread overview]
Message-ID: <1479329490-23176-1-git-send-email-tomas.winkler@intel.com> (raw)
The motivation behind this series is better support
for fixed address clients on the mei client bus.
Fixed address clients do not have flow control and hence
it is hard to work with clients especially if they have
unsolicitedreceive.
The top most patch add non blocking receive function for easier
check on data availability.
Alexander Usyskin (4):
mei: introduce host client uninitialized state
mei: bus: make a client pointer always available
mei: bus: split RX and async notification callbacks
mei: bus: enable non-blocking RX
drivers/misc/mei/bus-fixup.c | 4 +-
drivers/misc/mei/bus.c | 189 +++++++++++++++++++++++++------------------
drivers/misc/mei/client.c | 11 ++-
drivers/misc/mei/mei_dev.h | 10 ++-
drivers/nfc/mei_phy.c | 43 +++++-----
drivers/watchdog/mei_wdt.c | 38 +++------
include/linux/mei_cl_bus.h | 35 ++++----
7 files changed, 178 insertions(+), 152 deletions(-)
--
2.7.4
next reply other threads:[~2016-11-16 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 20:51 Tomas Winkler [this message]
2016-11-16 20:51 ` [char-misc-next 1/4] mei: introduce host client uninitialized state Tomas Winkler
2016-11-16 20:51 ` [char-misc-next 2/4] mei: bus: make a client pointer always available Tomas Winkler
2016-11-16 20:51 ` [char-misc-next 3/4] mei: bus: split RX and async notification callbacks Tomas Winkler
2016-11-16 20:51 ` [char-misc-next 4/4] mei: bus: enable non-blocking RX Tomas Winkler
2016-11-17 15:37 ` Greg Kroah-Hartman
2016-11-17 16:22 ` Winkler, Tomas
2016-11-17 16:27 ` Greg Kroah-Hartman
2016-11-18 19:30 ` Winkler, Tomas
2016-11-19 8:49 ` Greg Kroah-Hartman
2016-11-19 10:43 ` 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=1479329490-23176-1-git-send-email-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.