From: Tom Rix <trix@redhat.com>
To: Xu Yilun <yilun.xu@intel.com>,
mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, lgoncalv@redhat.com, hao.wu@intel.com
Subject: Re: [PATCH v3 3/3] Documentation: fpga: dfl: Add description for DFL UIO support
Date: Thu, 17 Dec 2020 05:26:29 -0800 [thread overview]
Message-ID: <994de3b8-0374-40d1-2644-5604742a264e@redhat.com> (raw)
In-Reply-To: <1608183881-18692-4-git-send-email-yilun.xu@intel.com>
On 12/16/20 9:44 PM, Xu Yilun wrote:
> This patch adds description for UIO support for dfl devices on DFL
> bus.
Thanks for the changes.
Reviewed-by: Tom Rix <trix@redhat.com>
> Signed-off-by: Xu Yilun <yilun.xu@intel.com>
> ---
> v2: no doc in v1, add it for v2.
> v3: some documentation fixes.
> ---
> Documentation/fpga/dfl.rst | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/Documentation/fpga/dfl.rst b/Documentation/fpga/dfl.rst
> index 0404fe6..b298ad9 100644
> --- a/Documentation/fpga/dfl.rst
> +++ b/Documentation/fpga/dfl.rst
> @@ -7,6 +7,7 @@ Authors:
> - Enno Luebbers <enno.luebbers@intel.com>
> - Xiao Guangrong <guangrong.xiao@linux.intel.com>
> - Wu Hao <hao.wu@intel.com>
> +- Xu Yilun <yilun.xu@intel.com>
>
> The Device Feature List (DFL) FPGA framework (and drivers according to
> this framework) hides the very details of low layer hardwares and provides
> @@ -502,6 +503,32 @@ FME Partial Reconfiguration Sub Feature driver (see drivers/fpga/dfl-fme-pr.c)
> could be a reference.
>
>
> +UIO support for DFL devices
> +===========================
> +The purpose of an FPGA is to be reprogrammed with newly developed hardware
> +components. New hardware can instantiate a new private feature in the DFL, and
> +then get a DFL device in their system. In some cases users may need a userspace
> +driver for the DFL device:
> +
> +* Users may need to run some diagnostic test for their hardwares.
> +* Users may prototype the kernel driver in user space.
> +* Some hardware is designed for specific purposes and does not fit into one of
> + the standard kernel subsystems.
> +
> +This requires the direct access to the MMIO space and interrupt handling in
> +userspace. The dfl-uio-pdev module exposes the UIO device interfaces for this
> +purpose. It adds the uio_pdrv_genirq platform device with the resources of
> +the DFL feature, and lets the generic UIO platform device driver provide UIO
> +support to userspace.
> +
> +FPGA_DFL_UIO_PDEV should be selected to enable this feature.
> +
> +The DFL UIO driver has a special matching algorithem. It will match any DFL
> +device which could not be handled by other DFL drivers. In this way, it will
> +not impact the functionality of the features which are already supported by the
> +system.
> +
> +
> Open discussion
> ===============
> FME driver exports one ioctl (DFL_FPGA_FME_PORT_PR) for partial reconfiguration
next prev parent reply other threads:[~2020-12-17 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 5:44 [PATCH v3 0/3] UIO support for dfl devices Xu Yilun
2020-12-17 5:44 ` [PATCH v3 1/3] fpga: dfl: add the match() ops for dfl driver Xu Yilun
2020-12-17 13:23 ` Tom Rix
2020-12-17 5:44 ` [PATCH v3 2/3] fpga: dfl: add the userspace I/O device support for DFL devices Xu Yilun
2020-12-17 13:25 ` Tom Rix
2020-12-18 8:05 ` Wu, Hao
2020-12-18 13:59 ` Tom Rix
2020-12-21 2:44 ` Wu, Hao
2020-12-21 3:33 ` Xu Yilun
2020-12-21 6:23 ` Wu, Hao
2020-12-17 5:44 ` [PATCH v3 3/3] Documentation: fpga: dfl: Add description for DFL UIO support Xu Yilun
2020-12-17 13:26 ` Tom Rix [this message]
2020-12-17 13:35 ` [PATCH v3 0/3] UIO support for dfl devices Tom Rix
2020-12-17 17:10 ` Greg KH
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=994de3b8-0374-40d1-2644-5604742a264e@redhat.com \
--to=trix@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).