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 v2 0/7] mei: Add DMA ring
Date: Thu, 22 Nov 2018 13:11:35 +0200 [thread overview]
Message-ID: <20181122111142.18653-1-tomas.winkler@intel.com> (raw)
This is a resend of the second part for the mei dma ring,
that was left out.
This series adds an alternative method for
transferring data between the mei driver and the device
via a DMA ring. The DMA ring allows transferring
data in bigger chunks, up to 128K, than the HW ring 512B.
The actual sizes depend on particular MEI generations.
The HW ring is faster for packets that fits
into the HW ring while a packet that would require
fragmentation is faster to send via the DMA ring.
V2: 1. Use single license for the new dma-ring.c file.
2. Adjust kdoc to new requirements:
https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html
Alexander Usyskin (2):
mei: bump hbm version to 2.1
mei: me: mark CNP devices as having dma support
Tomas Winkler (5):
mei: dma ring buffers allocation
mei: hbm: setup dma ring
mei: hw: add dma ring control block
mei: dma ring: implement rx circular buffer logic
mei: dma ring: implement transmit flow
drivers/misc/mei/Makefile | 1 +
drivers/misc/mei/client.c | 66 +++++++--
drivers/misc/mei/dma-ring.c | 269 +++++++++++++++++++++++++++++++++++
drivers/misc/mei/hbm.c | 88 +++++++++++-
drivers/misc/mei/hbm.h | 2 +
drivers/misc/mei/hw-me.c | 6 +
drivers/misc/mei/hw.h | 29 +++-
drivers/misc/mei/init.c | 2 +-
drivers/misc/mei/interrupt.c | 41 ++++--
drivers/misc/mei/mei_dev.h | 26 +++-
drivers/misc/mei/pci-me.c | 4 +-
11 files changed, 500 insertions(+), 34 deletions(-)
create mode 100644 drivers/misc/mei/dma-ring.c
--
2.17.2
next reply other threads:[~2018-11-22 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 11:11 Tomas Winkler [this message]
2018-11-22 11:11 ` [char-misc-next v2 1/7] mei: dma ring buffers allocation Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 2/7] mei: hbm: setup dma ring Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 3/7] mei: hw: add dma ring control block Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 4/7] mei: dma ring: implement rx circular buffer logic Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 5/7] mei: dma ring: implement transmit flow Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 6/7] mei: bump hbm version to 2.1 Tomas Winkler
2018-11-22 11:11 ` [char-misc-next v2 7/7] mei: me: mark CNP devices as having dma support Tomas Winkler
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=20181122111142.18653-1-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;
as well as URLs for NNTP newsgroup(s).