From: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
To: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Cc: Martyn Welch <martyn.welch@ge.com>,
Manohar Vanga <manohar.vanga@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Igor Alekseev <igor.alekseev@itep.ru>,
Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Subject: [PATCHv2 01/16] Documentation: mention vme_master_mmap() in VME API
Date: Thu, 28 May 2015 12:31:07 +0300 [thread overview]
Message-ID: <1432805482-24129-2-git-send-email-dmitry.kalinkin@gmail.com> (raw)
In-Reply-To: <1432805482-24129-1-git-send-email-dmitry.kalinkin@gmail.com>
Signed-off-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Cc: Igor Alekseev <igor.alekseev@itep.ru>
---
Documentation/vme_api.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/vme_api.txt b/Documentation/vme_api.txt
index ffe6e22..ca5b827 100644
--- a/Documentation/vme_api.txt
+++ b/Documentation/vme_api.txt
@@ -171,6 +171,12 @@ This functions by reading the offset, applying the mask. If the bits selected in
the mask match with the values of the corresponding bits in the compare field,
the value of swap is written the specified offset.
+Parts of a VME window can be mapped into user space memory using the following
+function:
+
+ int vme_master_mmap(struct vme_resource *resource,
+ struct vm_area_struct *vma)
+
Slave windows
=============
--
1.8.3.1
next prev parent reply other threads:[~2015-05-28 9:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:31 [PATCHv2 00/16] vme DMA and user space driver improvements Dmitry Kalinkin
2015-05-28 9:31 ` Dmitry Kalinkin [this message]
2015-05-28 9:31 ` [PATCHv2 02/16] vme: tsi148: fix DMA lists longer that one item Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 03/16] vme: tsi148: fix first DMA item mapping Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 04/16] vme: stop DMA transfer on interruption Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 05/16] staging: vme_user: refactor llseek to switch(){} Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 06/16] vme: check for A64 overflow in vme_check_window() Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 07/16] vme: export vme_check_window() Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 08/16] staging: vme_user: provide DMA functionality Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 09/16] vme: ca91cx42: return error code on DMA error Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 10/16] vme: ca91cx42: fix LM_CTL address mask Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 11/16] staging: vme_user: remove unused counters Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 12/16] staging: vme_user: remove forward declarations Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 13/16] staging: vme_user: remove open/release Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 14/16] staging: vme_user: remove buf_unalloc helper Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 15/16] vme: tsi148: depend on HAS_DMA for Kconfig Dmitry Kalinkin
2015-05-28 9:31 ` [PATCHv2 16/16] vme: provide uapi header Dmitry Kalinkin
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=1432805482-24129-2-git-send-email-dmitry.kalinkin@gmail.com \
--to=dmitry.kalinkin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=igor.alekseev@itep.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@gmail.com \
--cc=martyn.welch@ge.com \
/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®