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 00/12] mei: rx enhancements
Date: Fri, 22 Jul 2016 15:56:17 +0300 [thread overview]
Message-ID: <1469192189-29042-1-git-send-email-tomas.winkler@intel.com> (raw)
This patch series contains mostly fixes and enhancements
of the rx path:
1. Better handling of fixed address clients
2. Support for consecutive reads
3. Further amthif client diet
Alexander Usyskin (10):
mei: move read cb to complete queue if not connected
mei: add file pointer to the host client structure
mei: add read callback on demand for fixed_address clients
mei: amthif: drop mei_clear_lists function
mei: drop redundant krealloc and checks in irq read
mei: prepare read cb for fixed address clients on the receive path
only.
mei: rx flow control counter
mei: enqueue consecutive reads
mei: amthif: drop mei_amthif_read
mei: drop unused file transaction states
Tomas Winkler (2):
mei: use consistent naming for TX control flow credits
mei: add wrapper for queuing control commands.
drivers/misc/mei/amthif.c | 148 ++++---------------------------------
drivers/misc/mei/bus.c | 2 +-
drivers/misc/mei/client.c | 170 +++++++++++++++++++++----------------------
drivers/misc/mei/client.h | 5 +-
drivers/misc/mei/hbm.c | 45 ++++++------
drivers/misc/mei/interrupt.c | 47 ++++++------
drivers/misc/mei/main.c | 47 ++++++------
drivers/misc/mei/mei_dev.h | 23 ++----
8 files changed, 176 insertions(+), 311 deletions(-)
--
2.7.4
next reply other threads:[~2016-07-22 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 12:56 Tomas Winkler [this message]
2016-07-22 12:56 ` [char-misc-next 01/12] mei: move read cb to complete queue if not connected Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 02/12] mei: add file pointer to the host client structure Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 03/12] mei: add read callback on demand for fixed_address clients Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 04/12] mei: amthif: drop mei_clear_lists function Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 05/12] mei: drop redundant krealloc and checks in irq read Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 06/12] mei: prepare read cb for fixed address clients on the receive path only Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 07/12] mei: rx flow control counter Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 08/12] mei: use consistent naming for TX control flow credits Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 09/12] mei: add wrapper for queuing control commands Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 10/12] mei: enqueue consecutive reads Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 11/12] mei: amthif: drop mei_amthif_read Tomas Winkler
2016-07-22 12:56 ` [char-misc-next 12/12] mei: drop unused file transaction states Tomas Winkler
2016-07-24 22:52 ` [char-misc-next 00/12] mei: rx enhancements Winkler, Tomas
2016-07-24 23:28 ` Greg Kroah-Hartman
2016-07-25 21:49 ` Winkler, Tomas
2016-08-29 21:27 ` Winkler, Tomas
2016-08-30 6:11 ` 'Greg Kroah-Hartman'
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=1469192189-29042-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 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®