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 0/3] UIO support for dfl devices
Date: Thu, 17 Dec 2020 05:35:51 -0800 [thread overview]
Message-ID: <85d48e41-0185-0938-b0ed-93d0f825e761@redhat.com> (raw)
In-Reply-To: <1608183881-18692-1-git-send-email-yilun.xu@intel.com>
On 12/16/20 9:44 PM, Xu Yilun wrote:
> This patchset supports some dfl device drivers written in userspace.
>
> In the patchset v1, the "driver_override" interface should be used to bind
> the DFL UIO driver to DFL devices. But there is concern that the
> "driver_override" interface is not OK itself. So in v2, we use a new
> matching algorithem. The "driver_override" interface is abandoned, the DFL
> UIO driver matches any DFL device which could not be handled by other DFL
> drivers. So the DFL UIO driver could be used for new DFL devices which are
> not supported by kernel, also it will not impact the devices which are
> already got supported.
This set looks good to me.
Moritz,
Is it possible to get this into 5.11 ?
Tom
>
> Main changes from v1:
> - switch to the new matching algorithem. It matches DFL devices which could
> not be handled by other DFL drivers.
> - refacor the code about device resources filling.
> - add the documentation.
>
> Main changes from v2:
> - split the match ops changes in dfl.c to an independent patch.
> - move the declarations needed for dfl-uio-pdev from include/linux/dfl.h
> to driver/fpga/dfl.h
> - some minor fixes.
>
>
> Xu Yilun (3):
> fpga: dfl: add the match() ops for dfl driver
> fpga: dfl: add the userspace I/O device support for DFL devices
> Documentation: fpga: dfl: Add description for DFL UIO support
>
> Documentation/fpga/dfl.rst | 27 +++++++++++
> drivers/fpga/Kconfig | 10 ++++
> drivers/fpga/Makefile | 1 +
> drivers/fpga/dfl-uio-pdev.c | 110 ++++++++++++++++++++++++++++++++++++++++++++
> drivers/fpga/dfl.c | 22 +++++++--
> drivers/fpga/dfl.h | 5 ++
> include/linux/dfl.h | 3 ++
> 7 files changed, 173 insertions(+), 5 deletions(-)
> create mode 100644 drivers/fpga/dfl-uio-pdev.c
>
next prev parent reply other threads:[~2020-12-17 13:37 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
2020-12-17 13:35 ` Tom Rix [this message]
2020-12-17 17:10 ` [PATCH v3 0/3] UIO support for dfl devices 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=85d48e41-0185-0938-b0ed-93d0f825e761@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).