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, lgoncalv@redhat.com, Xu Yilun <yilun.xu@intel.com>
Subject: [PATCH 0/2] Modularization of DFL private feature drivers
Date: Wed, 15 Jul 2020 13:38:16 +0800 [thread overview]
Message-ID: <1594791498-14495-1-git-send-email-yilun.xu@intel.com> (raw)
This patchset makes it possible to develop independent driver modules
for DFL private features. It also helps to leverage existing kernel
drivers to enable some IP blocks in DFL.
Xu Yilun (2):
fpga: dfl: map feature mmio resources in their own feature drivers
fpga: dfl: create a dfl bus type to support DFL devices
Documentation/ABI/testing/sysfs-bus-dfl | 15 ++
drivers/fpga/dfl-pci.c | 21 +-
drivers/fpga/dfl.c | 435 +++++++++++++++++++++++++++-----
drivers/fpga/dfl.h | 91 ++++++-
4 files changed, 492 insertions(+), 70 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl
--
2.7.4
next reply other threads:[~2020-07-15 5:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 5:38 Xu Yilun [this message]
2020-07-15 5:38 ` [PATCH 1/2] fpga: dfl: map feature mmio resources in their own feature drivers Xu Yilun
2020-07-17 9:48 ` Wu, Hao
2020-07-21 6:57 ` Xu Yilun
2020-07-17 16:51 ` Tom Rix
2020-07-21 7:34 ` Xu Yilun
2020-07-22 6:51 ` Xu Yilun
2020-07-20 9:09 ` Wu, Hao
2020-07-21 7:40 ` Xu Yilun
2020-07-15 5:38 ` [PATCH 2/2] fpga: dfl: create a dfl bus type to support DFL devices Xu Yilun
2020-07-17 10:26 ` Wu, Hao
2020-07-21 8:30 ` Xu Yilun
2020-07-21 11:41 ` Wu, Hao
2020-07-21 14:44 ` Xu Yilun
2020-07-17 19:47 ` Tom Rix
2020-07-21 8:54 ` Xu Yilun
2020-07-21 14:39 ` Xu Yilun
2020-07-16 22:50 ` [PATCH 0/2] Modularization of DFL private feature drivers Tom Rix
2020-07-17 3:48 ` Wu, Hao
2020-07-17 13:32 ` Tom Rix
2020-07-20 9:21 ` Wu, Hao
2020-07-21 6:04 ` Xu Yilun
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=1594791498-14495-1-git-send-email-yilun.xu@intel.com \
--to=yilun.xu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).