From: Xu Yilun <yilun.xu@intel.com>
To: mdf@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: trix@redhat.com, bhu@redhat.com, Xu Yilun <yilun.xu@intel.com>,
Luwei Kang <luwei.kang@intel.com>, Wu Hao <hao.wu@intel.com>
Subject: [PATCH v3 7/7] Documentation: fpga: dfl: add descriptions for interrupt related interfaces.
Date: Tue, 24 Mar 2020 16:32:43 +0800 [thread overview]
Message-ID: <1585038763-22944-8-git-send-email-yilun.xu@intel.com> (raw)
In-Reply-To: <1585038763-22944-1-git-send-email-yilun.xu@intel.com>
This patch adds introductions of interrupt related interfaces for FME
error reporting, port error reporting and AFU user interrupts features.
Signed-off-by: Luwei Kang <luwei.kang@intel.com>
Signed-off-by: Wu Hao <hao.wu@intel.com>
Signed-off-by: Xu Yilun <yilun.xu@intel.com>
----
v2: Update Documents cause change of irq ioctl interfaces.
v3: No change
---
Documentation/fpga/dfl.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/fpga/dfl.rst b/Documentation/fpga/dfl.rst
index 094fc8a..c7ed3e4 100644
--- a/Documentation/fpga/dfl.rst
+++ b/Documentation/fpga/dfl.rst
@@ -89,6 +89,8 @@ The following functions are exposed through ioctls:
- Program bitstream (DFL_FPGA_FME_PORT_PR)
- Assign port to PF (DFL_FPGA_FME_PORT_ASSIGN)
- Release port from PF (DFL_FPGA_FME_PORT_RELEASE)
+- Get number of irqs of FME global error (DFL_FPGA_FME_ERR_GET_IRQ_NUM)
+- Set interrupt trigger for FME error (DFL_FPGA_FME_ERR_SET_IRQ)
More functions are exposed through sysfs
(/sys/class/fpga_region/regionX/dfl-fme.n/):
@@ -144,6 +146,10 @@ The following functions are exposed through ioctls:
- Map DMA buffer (DFL_FPGA_PORT_DMA_MAP)
- Unmap DMA buffer (DFL_FPGA_PORT_DMA_UNMAP)
- Reset AFU (DFL_FPGA_PORT_RESET)
+- Get number of irqs of port error (DFL_FPGA_PORT_ERR_GET_IRQ_NUM)
+- Set interrupt trigger for port error (DFL_FPGA_PORT_ERR_SET_IRQ)
+- Get number of irqs of UINT (DFL_FPGA_PORT_UINT_GET_IRQ_NUM)
+- Set interrupt trigger for UINT (DFL_FPGA_PORT_UINT_SET_IRQ)
DFL_FPGA_PORT_RESET:
reset the FPGA Port and its AFU. Userspace can do Port
@@ -378,6 +384,17 @@ The device nodes used for ioctl() or mmap() can be referenced through::
/sys/class/fpga_region/<regionX>/<dfl-port.n>/dev
+Interrupt support
+=================
+Some FME and AFU private features are able to generate interrupts. As mentioned
+above, users could call ioctl (DFL_FPGA_*_GET_IRQ_NUM) to know whether or how
+many interrupts are supported for this private feature. Drivers also implement
+an eventfd based interrupt handling mechanism for users to get notified when
+interrupt happens. Users could set eventfds to driver via
+ioctl (DFL_FPGA_*_SET_IRQ), and then poll/select on these eventfds waiting for
+notification.
+
+
Add new FIUs support
====================
It's possible that developers made some new function blocks (FIUs) under this
--
2.7.4
prev parent reply other threads:[~2020-03-24 8:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 8:32 [PATCH v3 0/7] Add interrupt support to FPGA DFL drivers Xu Yilun
2020-03-24 8:32 ` [PATCH v3 1/7] fpga: dfl: parse interrupt info for feature devices on enumeration Xu Yilun
2020-03-31 4:18 ` Wu Hao
2020-04-01 2:39 ` Xu Yilun
2020-04-01 3:41 ` Wu Hao
2020-04-01 5:37 ` Xu Yilun
2020-03-24 8:32 ` [PATCH v3 2/7] fpga: dfl: pci: add irq info for feature devices enumeration Xu Yilun
2020-03-31 4:41 ` Wu Hao
2020-04-01 2:59 ` Xu Yilun
2020-04-01 3:44 ` Wu Hao
2020-04-01 5:41 ` Xu Yilun
2020-03-24 8:32 ` [PATCH v3 3/7] fpga: dfl: introduce interrupt trigger setting API Xu Yilun
2020-03-31 5:01 ` Wu Hao
2020-04-01 3:03 ` Xu Yilun
2020-03-24 8:32 ` [PATCH v3 4/7] fpga: dfl: afu: add interrupt support for error reporting Xu Yilun
2020-03-31 5:10 ` Wu Hao
2020-03-24 8:32 ` [PATCH v3 5/7] fpga: dfl: fme: add interrupt support for global " Xu Yilun
2020-03-24 8:32 ` [PATCH v3 6/7] fpga: dfl: afu: add user interrupt support Xu Yilun
2020-03-31 5:15 ` Wu Hao
2020-04-01 3:13 ` Xu Yilun
2020-03-24 8:32 ` Xu Yilun [this message]
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=1585038763-22944-8-git-send-email-yilun.xu@intel.com \
--to=yilun.xu@intel.com \
--cc=bhu@redhat.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mdf@kernel.org \
--cc=trix@redhat.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®