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, yilun.xu@intel.com,
hao.wu@intel.com
Subject: [PATCH v3 0/5] add DFL bus support to MODULE_DEVICE_TABLE()
Date: Fri, 25 Sep 2020 00:59:56 +0800 [thread overview]
Message-ID: <1600966801-30586-1-git-send-email-yilun.xu@intel.com> (raw)
I will refactor the code for dfl-n3000-nios driver, so just sent the
fpga-dfl bus code this time. fpga-dfl-emif driver could be the first
use case for fpga-dfl bus.
Main changes from v1:
- A new patch (Patch #3) to fix the description.
- Rename the dfl-bus.h to dfl.h
- Updated the MAINTAINERS under FPGA DFL DRIVERS.
- Improve comments and minor fixes.
Main changes from v2:
- Change the bus name from "dfl" to "fpga-dfl", also rename related
variables, functions ...
- Changes the data type of fpga_dfl_device_id.type from u8 to u16
- Explicitly defines the values of enum fpga_dfl_id_type
- Delete the comments for the valid bits of type & feature_id
- changes MODALIAS format for fpga dfl devices
Xu Yilun (5):
fpga: dfl: rename the bus type "dfl" to "fpga-dfl"
fpga: dfl: fix the definitions of type & feature_id for dfl devices
fpga: dfl: move fpga_dfl_device_id to mod_devicetable.h
fpga: dfl: add fpga dfl bus support to MODULE_DEVICE_TABLE()
fpga: dfl: move fpga dfl bus related APIs to include/linux/fpga/dfl.h
Documentation/ABI/testing/sysfs-bus-dfl | 15 --
Documentation/ABI/testing/sysfs-bus-fpga-dfl | 15 ++
MAINTAINERS | 3 +-
drivers/fpga/dfl.c | 256 ++++++++++++++-------------
drivers/fpga/dfl.h | 89 +---------
include/linux/fpga/dfl.h | 87 +++++++++
include/linux/mod_devicetable.h | 12 ++
scripts/mod/devicetable-offsets.c | 4 +
scripts/mod/file2alias.c | 13 ++
9 files changed, 265 insertions(+), 229 deletions(-)
delete mode 100644 Documentation/ABI/testing/sysfs-bus-dfl
create mode 100644 Documentation/ABI/testing/sysfs-bus-fpga-dfl
create mode 100644 include/linux/fpga/dfl.h
--
2.7.4
next reply other threads:[~2020-09-24 17:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 16:59 Xu Yilun [this message]
2020-09-24 16:59 ` [PATCH v3 1/5] fpga: dfl: rename the bus type "dfl" to "fpga-dfl" Xu Yilun
2020-09-24 17:27 ` Moritz Fischer
[not found] ` <20200926022346.GA5623@yilunxu-OptiPlex-7050>
2020-09-26 6:09 ` Greg KH
2020-09-26 19:22 ` Moritz Fischer
2020-09-27 5:51 ` Greg KH
2020-09-27 7:37 ` Xu Yilun
2020-09-27 7:54 ` Greg KH
[not found] ` <20200927083647.GC16433@yilunxu-OptiPlex-7050>
2020-09-29 1:23 ` Xu Yilun
2020-09-29 4:19 ` Moritz Fischer
2020-09-29 7:19 ` Xu Yilun
2020-10-09 6:20 ` Xu Yilun
2020-10-09 6:41 ` Greg KH
2020-10-09 7:34 ` Xu Yilun
2020-10-09 21:28 ` Moritz Fischer
2020-10-10 7:03 ` Greg KH
2020-09-24 19:01 ` Tom Rix
2020-09-25 2:41 ` Moritz Fischer
2020-09-25 3:15 ` Xu Yilun
2020-09-24 16:59 ` [PATCH v3 2/5] fpga: dfl: fix the definitions of type & feature_id for dfl devices Xu Yilun
2020-09-24 16:59 ` [PATCH v3 3/5] fpga: dfl: move fpga_dfl_device_id to mod_devicetable.h Xu Yilun
2020-09-24 17:00 ` [PATCH v3 4/5] fpga: dfl: add fpga dfl bus support to MODULE_DEVICE_TABLE() Xu Yilun
2020-09-24 17:00 ` [PATCH v3 5/5] fpga: dfl: move fpga dfl bus related APIs to include/linux/fpga/dfl.h 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=1600966801-30586-1-git-send-email-yilun.xu@intel.com \
--to=yilun.xu@intel.com \
--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=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).