add new features for FPGA DFL drivers
Subsystems (4)
v4 cover add new features for FPGA DFL drivers
This patchset adds more features support for FPGA Device Feature List (DFL) drivers, including PR enhancement, virtualization support based on PCIe SRIOV, private features of Port, private features of FME, and enhancement to DFL framework. Please refer to details in below list.
Main changes from v3:
- split performance reporting support into another patchset for better review.
Main changes from v2:
- move thermal/power management private feature support to another patchset, including hwmon patches and related documentation update.
- update sysfs doc for kernel version and date.
- replace scnprintf to sprintf for sysfs interfaces.
- fix comments for performance reporting support. (patch #16)
Main changes from v1:
- split the clean up code in a separated patch (patch #2)
- add cpu_feature_enabled check for AVX512 code (patch #4)
- improve sysfs return values and also sysfs doc (patch #12 #17)
- create a hwmon for thermal management sysfs interfaces (patch #15)
- create a hwmon for power management sysfs interfaces (patch #16)
- update docmentation according to above changes (patch #5)
- improve sysfs doc for performance reporting support (patch #18)
Wu Hao (15):
fpga: dfl-fme-mgr: fix FME_PR_INTFC_ID register address.
fpga: dfl: fme: remove copy_to_user() in ioctl for PR
fpga: dfl: fme: align PR buffer size per PR datawidth
fpga: dfl: fme: support 512bit data width PR
Documentation: fpga: dfl: add descriptions for virtualization and new
interfaces.
fpga: dfl: fme: add DFL_FPGA_FME_PORT_RELEASE/ASSIGN ioctl support.
fpga: dfl: pci: enable SRIOV support.
fpga: dfl: afu: add AFU state related sysfs interfaces
fpga: dfl: afu: add userclock sysfs interfaces.
fpga: dfl: add id_table for dfl private feature driver
fpga: dfl: afu: export __port_enable/disable function.
fpga: dfl: afu: add error reporting support.
fpga: dfl: afu: add STP (SignalTap) support
fpga: dfl: fme: add capability sysfs interfaces
fpga: dfl: fme: add global error reporting support
Documentation/ABI/testing/sysfs-platform-dfl-fme | 98 ++++++ Documentation/ABI/testing/sysfs-platform-dfl-port | 104 ++++++ Documentation/fpga/dfl.txt | 101 ++++++ drivers/fpga/Makefile | 3 +- drivers/fpga/dfl-afu-error.c | 225 +++++++++++++ drivers/fpga/dfl-afu-main.c | 330 ++++++++++++++++++- drivers/fpga/dfl-afu.h | 7 + drivers/fpga/dfl-fme-error.c | 385 ++++++++++++++++++++++ drivers/fpga/dfl-fme-main.c | 120 ++++++- drivers/fpga/dfl-fme-mgr.c | 117 ++++++- drivers/fpga/dfl-fme-pr.c | 65 ++-- drivers/fpga/dfl-fme.h | 7 +- drivers/fpga/dfl-pci.c | 40 +++ drivers/fpga/dfl.c | 169 +++++++++- drivers/fpga/dfl.h | 54 ++- include/uapi/linux/fpga-dfl.h | 32 ++ 16 files changed, 1777 insertions(+), 80 deletions(-) create mode 100644 drivers/fpga/dfl-afu-error.c create mode 100644 drivers/fpga/dfl-fme-error.c
Signature · 1 line
1.8.3.1
PATCH v4 1/15 fpga: dfl-fme-mgr: fix FME_PR_INTFC_ID register address.
FME_PR_INTFC_ID is used as compat_id for fpga manager and region, but high 64 bits and low 64 bits of the compat_id are swapped by mistake. This patch fixes this problem by fixing register address.
--- drivers/fpga/dfl-fme-mgr.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/fpga/dfl-fme-mgr.c +2 -2
@@ -30,8 +30,8 @@#define FME_PR_STS 0x10#define FME_PR_DATA 0x18#define FME_PR_ERR 0x20 -#define FME_PR_INTFC_ID_H 0xA8 -#define FME_PR_INTFC_ID_L 0xB0 +#define FME_PR_INTFC_ID_L 0xA8 +#define FME_PR_INTFC_ID_H 0xB0/* FME PR Control Register Bitfield */ #define FME_PR_CTRL_PR_RST BIT_ULL(0)/* Reset PR engine */
Signature · 1 line
1.8.3.1
PATCH v4 2/15 fpga: dfl: fme: remove copy_to_user() in ioctl for PR
In reply to Wu HaoThis patch removes copy_to_user() code in partial reconfiguration ioctl, as it's useless as user never needs to read the data structure after ioctl.
---
v2: clean up code split from patch 2 in v1 patchset.
v3: no change.
v4: no change.
--- drivers/fpga/dfl-fme-pr.c | 3 --- 1 file changed, 3 deletions(-)
drivers/fpga/dfl-fme-pr.c +0 -3
@@ -159,9 +159,6 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg)mutex_unlock (&pdata->lock); free_exit:vfree (buf); -if (copy_to_user ((void __user *)arg, &port_pr, minsz)) -return -EFAULT ; -return ret; }
Signature · 1 line
1.8.3.1
PATCH v4 3/15 fpga: dfl: fme: align PR buffer size per PR datawidth
In reply to Wu HaoCurrent driver checks if input bitstream file size is aligned or not per PR data width (default 32bits). It requires one additional step for end user when they generate the bitstream file, padding extra zeros to bitstream file to align its size per PR data width, but they don't have to as hardware will drop extra padding bytes automatically.
In order to simplify the user steps, this patch aligns PR buffer size per PR data width in driver, to allow user to pass unaligned size bitstream files to driver.
--- drivers/fpga/dfl-fme-pr.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-)
drivers/fpga/dfl-fme-pr.c +9 -5
@@ -74,6 +74,7 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg)struct dfl_fme *fme;unsigned long minsz;void *buf =NULL ; +size_t length;int ret =0 ;u64 v;
@@ -85,9 +86,6 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg)if (port_pr.argsz < minsz || port_pr.flags)return -EINVAL ; -if (!IS_ALIGNED (port_pr.buffer_size,4 )) -return -EINVAL ; -/* get fme header region */ fme_hdr =dfl_get_feature_ioaddr_by_id (&pdev->dev,FME_FEATURE_ID_HEADER );
@@ -103,7 +101,13 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg) port_pr.buffer_size))return -EFAULT ; - buf =vmalloc (port_pr.buffer_size); +/* +* align PR buffer per PR bandwidth, as HW ignores the extra padding +* data automatically. +*/ + length =ALIGN (port_pr.buffer_size,4 ); + + buf =vmalloc (length);if (!buf)return -ENOMEM ;
@@ -140,7 +144,7 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg)fpga_image_info_free (region->info); info->buf = buf; - info->count = port_pr.buffer_size; + info->count = length; info->region_id = port_pr.port_id; region->info = info;
Signature · 1 line
1.8.3.1
PATCH v4 4/15 fpga: dfl: fme: support 512bit data width PR
In reply to Wu HaoIn early partial reconfiguration private feature, it only supports 32bit data width when writing data to hardware for PR. 512bit data width PR support is an important optimization for some specific solutions (e.g. XEON with FPGA integrated), it allows driver to use AVX512 instruction to improve the performance of partial reconfiguration. e.g. programming one 100MB bitstream image via this 512bit data width PR hardware only takes ~300ms, but 32bit revision requires ~3s per test result.
Please note now this optimization is only done on revision 2 of this PR private feature which is only used in integrated solution that AVX512 is always supported. This revision 2 hardware doesn't support 32bit PR.
---
v2: check AVX512 support using cpu_feature_enabled()
fix other comments from Scott Wood <[email protected]>
v3: no change.
v4: no change.
--- drivers/fpga/dfl-fme-main.c | 3 ++ drivers/fpga/dfl-fme-mgr.c | 113 +++++++++++++++++++++++++++++++++++++------- drivers/fpga/dfl-fme-pr.c | 43 +++++++++++------ drivers/fpga/dfl-fme.h | 2 + drivers/fpga/dfl.h | 5 ++ 5 files changed, 135 insertions(+), 31 deletions(-)
drivers/fpga/dfl-fme-main.c +3 -0
@@ -21,6 +21,8 @@#include "dfl.h" #include "dfl-fme.h" +#define DRV_VERSION "0.8" +static ssize_t ports_num_show (struct device *dev,struct device_attribute *attr,char *buf) {
@@ -277,3 +279,4 @@ static int fme_remove(struct platform_device *pdev)MODULE_AUTHOR ("Intel Corporation" );MODULE_LICENSE ("GPL v2" );MODULE_ALIAS ("platform:dfl-fme" ); +MODULE_VERSION (DRV_VERSION );
drivers/fpga/dfl-fme-mgr.c +97 -16
178 lines not on this page · raw message
drivers/fpga/dfl-fme-pr.c +28 -15
84 lines not on this page · raw message
drivers/fpga/dfl-fme.h +2 -0
@@ -21,12 +21,14 @@/** * struct dfl_fme - dfl fme private data * +* @pr_datawidth: data width for partial reconfiguration. * @mgr: FME's FPGA manager platform device. * @region_list: linked list of FME's FPGA regions. * @bridge_list: linked list of FME's FPGA bridges. * @pdata: fme platform device's pdata. */ struct dfl_fme { +int pr_datawidth;struct platform_device *mgr;struct list_head region_list;struct list_head bridge_list;
drivers/fpga/dfl.h +5 -0
@@ -331,6 +331,11 @@ static inline bool dfl_feature_is_port(void __iomem *base) (FIELD_GET (DFH_ID , v) ==DFH_ID_FIU_PORT ); } +static inline u8 dfl_feature_revision (void __iomem *base) +{ +return (u8 )FIELD_GET (DFH_REVISION ,readq (base +DFH )); +} +/** * struct dfl_fpga_enum_info - DFL FPGA enumeration information *
Signature · 1 line
1.8.3.1
PATCH v4 5/15 Documentation: fpga: dfl: add descriptions for virtualization and new interfaces.
In reply to Wu HaoThis patch adds virtualization support description for DFL based FPGA devices (based on PCIe SRIOV), and introductions to new interfaces added by new dfl private feature drivers.
--- Documentation/fpga/dfl.txt | 101 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+)
Documentation/fpga/dfl.txt +101 -0
@@ -84,6 +84,8 @@ The following functions are exposed through ioctls: Get driver API version (DFL_FPGA_GET_API_VERSION) Check for extensions (DFL_FPGA_CHECK_EXTENSION) 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) More functions are exposed through sysfs (/sys/class/fpga_region/regionX/dfl-fme.n/):
@@ -99,6 +101,10 @@ More functions are exposed through sysfs one FPGA device may have more than one port, this sysfs interface indicates how many ports the FPGA device has. + Global error reporting management (errors/) + error reporting sysfs interfaces allow user to read errors detected by the + hardware, and clear the logged errors. + FIU - PORT ==========
@@ -139,6 +145,10 @@ More functions are exposed through sysfs: Read Accelerator GUID (afu_id) afu_id indicates which PR bitstream is programmed to this AFU. + Error reporting (errors/) + error reporting sysfs interfaces allow user to read port/afu errors + detected by the hardware, and clear the logged errors. + DFL Framework Overview ======================
@@ -212,6 +222,97 @@ the compat_id exposed by the target FPGA region. This check is usually done by userspace before calling the reconfiguration IOCTL. +FPGA virtualization - PCIe SRIOV +================================ +This section describes the virtualization support on DFL based FPGA device to +enable accessing an accelerator from applications running in a virtual machine +(VM). This section only describes the PCIe based FPGA device with SRIOV support. + +Features supported by the particular FPGA device are exposed through Device +Feature Lists, as illustrated below: + + +-------------------------------+ +-------------+ + | PF | | VF | + +-------------------------------+ +-------------+ + ^ ^ ^ ^ + | | | | ++-----|------------|---------|--------------|-------+ +| | | | | | +| +-----+ +-------+ +-------+ +-------+ | +| | FME | | Port0 | | Port1 | | Port2 | | +| +-----+ +-------+ +-------+ +-------+ | +| ^ ^ ^ | +| | | | | +| +-------+ +------+ +-------+ | +| | AFU | | AFU | | AFU | | +| +-------+ +------+ +-------+ | +| | +| DFL based FPGA PCIe Device | ++---------------------------------------------------+ + +FME is always accessed through the physical function (PF). + +Ports (and related AFUs) are accessed via PF by default, but could be exposed +through virtual function (VF) devices via PCIe SRIOV. Each VF only contains +1 Port and 1 AFU for isolation. Users could assign individual VFs (accelerators) +created via PCIe SRIOV interface, to virtual machines. + +The driver organization in virtualization case is illustrated below: + + +-------++------++------+ | + | FME || FME || FME | | + | FPGA || FPGA || FPGA | | + |Manager||Bridge||Region| | + +-------++------++------+ | + +-----------------------+ +--------+ | +--------+ + | FME | | AFU | | | AFU | + | Module | | Module | | | Module | + +-----------------------+ +--------+ | +--------+ + +-----------------------+ | +-----------------------+ + | FPGA Container Device | | | FPGA Container Device | + | (FPGA Base Region) | | | (FPGA Base Region) | + +-----------------------+ | +-----------------------+ + +------------------+ | +------------------+ + | FPGA PCIE Module | | Virtual | FPGA PCIE Module | + +------------------+ Host | Machine +------------------+ + -------------------------------------- | ------------------------------ + +---------------+ | +---------------+ + | PCI PF Device | | | PCI VF Device | + +---------------+ | +---------------+ + +FPGA PCIe device driver is always loaded first once a FPGA PCIe PF or VF device +is detected. It: + + a) finish enumeration on both FPGA PCIe PF and VF device using common + interfaces from DFL framework. + b) supports SRIOV. + +The FME device driver plays a management role in this driver architecture, it +provides ioctls to release Port from PF and assign Port to PF. After release +a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV +sysfs interface. + +To enable accessing an accelerator from applications running in a VM, the +respective AFU's port needs to be assigned to a VF using the following steps: + + a) The PF owns all AFU ports by default. Any port that needs to be + reassigned to a VF must first be released through the + DFL_FPGA_FME_PORT_RELEASE ioctl on the FME device. + + b) Once N ports are released from PF, then user can use command below + to enable SRIOV and VFs. Each VF owns only one Port with AFU. + + echo N > $PCI_DEVICE_PATH/sriov_numvfs + + c) Pass through the VFs to VMs + + d) The AFU under VF is accessible from applications in VM (using the + same driver inside the VF). + +Note that an FME can't be assigned to a VF, thus PR and other management +functions are only available via the PF. + + Device enumeration ================== This section introduces how applications enumerate the fpga device from
Signature · 1 line
1.8.3.1
Moritz Fischer
maintainerRe: [PATCH v4 05/15] Documentation: fpga: dfl: add descriptions for virtualization and new interfaces.
Hi Wu,
Documentation/fpga/dfl.txt
Quoted 15 lines · Wu Hao
This patch adds virtualization support description for DFL based FPGA devices (based on PCIe SRIOV), and introductions to new interfaces added by new dfl private feature drivers.
Signed-off-by Xu Yilun <[email protected]>Signed-off-by Wu Hao <[email protected]>Acked-by Alan Tull <[email protected]>--- Documentation/fpga/dfl.txt | 101 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+)Documentation/fpga/dfl.txt +0
-0
This got re{named,formatted} in linux-next. I've tried to fix it before sending it to Greg.
Thanks,
Moritz
Re: [PATCH v4 05/15] Documentation: fpga: dfl: add descriptions for virtualization and new interfaces.
Quoted 14 lines · Moritz Fischer
Hi Wu,
Quoted 11 lines · Wu Hao
This patch adds virtualization support description for DFL based FPGA devices (based on PCIe SRIOV), and introductions to new interfaces added by new dfl private feature drivers.
Signed-off-by Xu Yilun <[email protected]>Signed-off-by Wu Hao <[email protected]>Acked-by Alan Tull <[email protected]>--- Documentation/fpga/dfl.txt | 101 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+)
Quoted 7 lines
Documentation/fpga/dfl.txt
Quoted 4 lines
Documentation/fpga/dfl.txt +0
-0This got re{named,formatted} in linux-next. I've tried to fix it before sending it to Greg.
Many Thanks for the help! :)
I think I need rebase thermal/power management (hwmon) and perf support patchsets as they update this documentation file too. But I feel we can go ahead on code review for the other patches, if there are some comments received and something need to fix, i can put fixes together in the next version.
Thanks
Hao
Quoted 3 lines
Thanks,
Moritz
Re: [PATCH v4 05/15] Documentation: fpga: dfl: add descriptions for virtualization and new interfaces.
Quoted 23 lines · Wu Hao
Quoted 14 lines · Moritz Fischer
Hi Wu,
Quoted 11 lines · Wu Hao
This patch adds virtualization support description for DFL based FPGA devices (based on PCIe SRIOV), and introductions to new interfaces added by new dfl private feature drivers.
Signed-off-by Xu Yilun <[email protected]>Signed-off-by Wu Hao <[email protected]>Acked-by Alan Tull <[email protected]>--- Documentation/fpga/dfl.txt | 101 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+)Quoted 7 lines
Documentation/fpga/dfl.txt
Quoted 4 lines
Documentation/fpga/dfl.txt +0
-0This got re{named,formatted} in linux-next. I've tried to fix it before sending it to Greg.
Quoted 7 lines
Many Thanks for the help! :)
I think I need rebase thermal/power management (hwmon) and perf support patchsets as they update this documentation file too. But I feel we can go ahead on code review for the other patches, if there are some comments received and something need to fix, i can put fixes together in the next version.
Hi Moritz,
I found some descriptions are dropped unexpectedly in your patch, so I prepared and sent out a new version (v2) to fix it. Please let me know if you prefer an increamental patch.
Thanks!
Hao
Quoted 7 lines
Thanks
HaoQuoted 3 lines
Thanks,
Moritz
PATCH v4 6/15 fpga: dfl: fme: add DFL_FPGA_FME_PORT_RELEASE/ASSIGN ioctl support.
In reply to Wu HaoIn order to support virtualization usage via PCIe SRIOV, this patch adds two ioctls under FPGA Management Engine (FME) to release and assign back the port device. In order to safely turn Port from PF into VF and enable PCIe SRIOV, it requires user to invoke this PORT_RELEASE ioctl to release port firstly to remove userspace interfaces, and then configure the PF/VF access register in FME. After disable SRIOV, it requires user to invoke this PORT_ASSIGN ioctl to attach the port back to PF.
Ioctl interfaces:
* DFL_FPGA_FME_PORT_RELEASE
Release platform device of given port, it deletes port platform device to remove related userspace interfaces on PF, then configures PF/VF access mode to VF.
* DFL_FPGA_FME_PORT_ASSIGN
Assign platform device of given port back to PF, it configures PF/VF access mode to PF, then adds port platform device back to re-enable related userspace interfaces on PF.
---
v3: code rebase.
v4: no change.
--- drivers/fpga/dfl-fme-main.c | 54 +++++++++++++++++++++ drivers/fpga/dfl.c | 107 +++++++++++++++++++++++++++++++++++++----- drivers/fpga/dfl.h | 10 ++++ include/uapi/linux/fpga-dfl.h | 32 +++++++++++++ 4 files changed, 191 insertions(+), 12 deletions(-)
drivers/fpga/dfl-fme-main.c +54 -0
@@ -16,6 +16,7 @@#include <linux/kernel.h> #include <linux/module.h> +#include <linux/uaccess.h> #include <linux/fpga-dfl.h> #include "dfl.h"
@@ -105,9 +106,62 @@ static void fme_hdr_uinit(struct platform_device *pdev,sysfs_remove_files (&pdev->dev.kobj, fme_hdr_attrs); } +static long fme_hdr_ioctl_release_port (struct dfl_feature_platform_data *pdata, +void __user *arg) +{ +struct dfl_fpga_cdev *cdev = pdata->dfl_cdev; +struct dfl_fpga_fme_port_release release; +unsigned long minsz; + + minsz = offsetofend(struct dfl_fpga_fme_port_release, port_id); + +if (copy_from_user (&release, arg, minsz)) +return -EFAULT ; + +if (release.argsz < minsz || release.flags) +return -EINVAL ; + +return dfl_fpga_cdev_config_port (cdev, release.port_id, true); +} + +static long fme_hdr_ioctl_assign_port (struct dfl_feature_platform_data *pdata, +void __user *arg) +{ +struct dfl_fpga_cdev *cdev = pdata->dfl_cdev; +struct dfl_fpga_fme_port_assign assign; +unsigned long minsz; + + minsz = offsetofend(struct dfl_fpga_fme_port_assign, port_id); + +if (copy_from_user (&assign, arg, minsz)) +return -EFAULT ; + +if (assign.argsz < minsz || assign.flags) +return -EINVAL ; + +return dfl_fpga_cdev_config_port (cdev, assign.port_id, false); +} + +static long fme_hdr_ioctl (struct platform_device *pdev, +struct dfl_feature *feature, +unsigned int cmd,unsigned long arg) +{ +struct dfl_feature_platform_data *pdata =dev_get_platdata (&pdev->dev); + +switch (cmd) { +case DFL_FPGA_FME_PORT_RELEASE : +return fme_hdr_ioctl_release_port (pdata, (void __user *)arg); +case DFL_FPGA_FME_PORT_ASSIGN : +return fme_hdr_ioctl_assign_port (pdata, (void __user *)arg); + } + +return -ENODEV ; +} +static const struct dfl_feature_ops fme_hdr_ops = { .init = fme_hdr_init, .uinit = fme_hdr_uinit, + .ioctl = fme_hdr_ioctl, };static struct dfl_feature_driver fme_feature_drvs[] = {
drivers/fpga/dfl.c +95 -12
148 lines not on this page · raw message
drivers/fpga/dfl.h +10 -0
@@ -183,6 +183,8 @@ struct dfl_feature {#define DEV_STATUS_IN_USE 0 +#define FEATURE_DEV_ID_UNUSED (-1) +/** * struct dfl_feature_platform_data - platform data for feature devices *
@@ -191,6 +193,7 @@ struct dfl_feature {* @cdev: cdev of feature dev. * @dev: ptr to platform device linked with this platform data. * @dfl_cdev: ptr to container device. +* @id: id used for this feature device. * @disable_count: count for port disable. * @num: number for sub features. * @dev_status: dev status (e.g. DEV_STATUS_IN_USE).
@@ -203,6 +206,7 @@ struct dfl_feature_platform_data {struct cdev cdev;struct platform_device *dev;struct dfl_fpga_cdev *dfl_cdev; +int id;unsigned int disable_count;unsigned long dev_status;void *private;
@@ -378,6 +382,7 @@ int dfl_fpga_enum_info_add_dfl(struct dfl_fpga_enum_info *info,* @fme_dev: FME feature device under this container device. * @lock: mutex lock to protect the port device list. * @port_dev_list: list of all port feature devices under this container device. +* @released_port_num: released port number under this container device. */ struct dfl_fpga_cdev {struct device *parent;
@@ -385,6 +390,7 @@ struct dfl_fpga_cdev {struct device *fme_dev;struct mutex lock;struct list_head port_dev_list; +int released_port_num; }; struct dfl_fpga_cdev *
@@ -412,4 +418,8 @@ struct platform_device * return pdev; } + +int dfl_fpga_cdev_config_port (struct dfl_fpga_cdev *cdev, +u32 port_id,bool release); +#endif /* __FPGA_DFL_H */
include/uapi/linux/fpga-dfl.h +32 -0
@@ -176,4 +176,36 @@ struct dfl_fpga_fme_port_pr {#define DFL_FPGA_FME_PORT_PR _IO(DFL_FPGA_MAGIC, DFL_FME_BASE + 0) +/** +* DFL_FPGA_FME_PORT_RELEASE - _IOW(DFL_FPGA_MAGIC, DFL_FME_BASE + 1, +* struct dfl_fpga_fme_port_release) +* +* Driver releases the port per Port ID provided by caller. +* Return: 0 on success, -errno on failure. +*/ +struct dfl_fpga_fme_port_release { +/* Input */ +__u32 argsz;/* Structure length */ +__u32 flags;/* Zero for now */ +__u32 port_id; +}; + +#define DFL_FPGA_FME_PORT_RELEASE _IO(DFL_FPGA_MAGIC, DFL_FME_BASE + 1) + +/** +* DFL_FPGA_FME_PORT_ASSIGN - _IOW(DFL_FPGA_MAGIC, DFL_FME_BASE + 2, +* struct dfl_fpga_fme_port_assign) +* +* Driver assigns the port back per Port ID provided by caller. +* Return: 0 on success, -errno on failure. +*/ +struct dfl_fpga_fme_port_assign { +/* Input */ +__u32 argsz;/* Structure length */ +__u32 flags;/* Zero for now */ +__u32 port_id; +}; + +#define DFL_FPGA_FME_PORT_ASSIGN _IO(DFL_FPGA_MAGIC, DFL_FME_BASE + 2) +#endif /* _UAPI_LINUX_FPGA_DFL_H */
Signature · 1 line
1.8.3.1
PATCH v4 7/15 fpga: dfl: pci: enable SRIOV support.
In reply to Wu HaoThis patch enables the standard sriov support. It allows user to enable SRIOV (and VFs), then user could pass through accelerators (VFs) into virtual machine or use VFs directly in host.
--- drivers/fpga/dfl-pci.c | 40 ++++++++++++++++++++++++++++++++++++++++ drivers/fpga/dfl.c | 41 +++++++++++++++++++++++++++++++++++++++++ drivers/fpga/dfl.h | 1 + 3 files changed, 82 insertions(+)
drivers/fpga/dfl-pci.c +40 -0
@@ -223,8 +223,46 @@ int cci_pci_probe(struct pci_dev *pcidev, const struct pci_device_id *pcidevid)return ret; } +static int cci_pci_sriov_configure (struct pci_dev *pcidev,int num_vfs) +{ +struct cci_drvdata *drvdata =pci_get_drvdata (pcidev); +struct dfl_fpga_cdev *cdev = drvdata->cdev; +int ret =0 ; + +mutex_lock (&cdev->lock); + +if (!num_vfs) { +/* +* disable SRIOV and then put released ports back to default +* PF access mode. +*/ +pci_disable_sriov (pcidev); + +__dfl_fpga_cdev_config_port_vf (cdev, false); + + }else if (cdev->released_port_num == num_vfs) { +/* +* only enable SRIOV if cdev has matched released ports, put +* released ports into VF access mode firstly. +*/ +__dfl_fpga_cdev_config_port_vf (cdev, true); + + ret =pci_enable_sriov (pcidev, num_vfs); +if (ret) +__dfl_fpga_cdev_config_port_vf (cdev, false); + }else { + ret = -EINVAL ; + } + +mutex_unlock (&cdev->lock); +return ret; +} +static void cci_pci_remove (struct pci_dev *pcidev) { +if (dev_is_pf (&pcidev->dev)) +cci_pci_sriov_configure (pcidev,0 ); +cci_remove_feature_devs (pcidev);pci_disable_pcie_error_reporting (pcidev); }
@@ -234,6 +272,7 @@ static void cci_pci_remove(struct pci_dev *pcidev) .id_table = cci_pcie_id_tbl, .probe = cci_pci_probe, .remove = cci_pci_remove, + .sriov_configure = cci_pci_sriov_configure, };module_pci_driver (cci_pci_driver);
@@ -241,3 +280,4 @@ static void cci_pci_remove(struct pci_dev *pcidev)MODULE_DESCRIPTION ("FPGA DFL PCIe Device Driver" );MODULE_AUTHOR ("Intel Corporation" );MODULE_LICENSE ("GPL v2" ); +MODULE_VERSION (DRV_VERSION );
drivers/fpga/dfl.c +41 -0
47 lines not on this page · raw message
drivers/fpga/dfl.h +1 -0
@@ -421,5 +421,6 @@ struct platform_device *int dfl_fpga_cdev_config_port (struct dfl_fpga_cdev *cdev,u32 port_id,bool release); +void __dfl_fpga_cdev_config_port_vf (struct dfl_fpga_cdev *cdev,bool is_vf);#endif /* __FPGA_DFL_H */
Signature · 1 line
1.8.3.1
PATCH v4 8/15 fpga: dfl: afu: add AFU state related sysfs interfaces
In reply to Wu HaoThis patch introduces more sysfs interfaces for Accelerated Function Unit (AFU). These interfaces allow users to read current AFU Power State (APx), read / clear AFU Power (APx) events which are sticky to identify transient APx state, and manage AFU's LTR (latency tolerance reporting).
---
v3: replace scnprintf with sprintf in sysfs interfaces.
update sysfs doc kernel version and date.
v4: update sysfs doc date.
--- Documentation/ABI/testing/sysfs-platform-dfl-port | 30 +++++ drivers/fpga/dfl-afu-main.c | 140 ++++++++++++++++++++++ drivers/fpga/dfl.h | 11 ++ 3 files changed, 181 insertions(+)
Documentation/ABI/testing/sysfs-platform-dfl-port +30 -0
@@ -14,3 +14,33 @@ Description: Read-only. User can program different PR bitstreams to FPGA Accelerator Function Unit (AFU) for different functions. It returns uuid which could be used to identify which PR bitstream is programmed in this AFU. + +What: /sys/bus/platform/devices/dfl-port.0/power_state +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It reports the APx (AFU Power) state, different APx + means different throttling level. When reading this file, it + returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6. + +What: /sys/bus/platform/devices/dfl-port.0/ap1_event +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-write. Read or set 1 to clear AP1 (AFU Power State 1) + event. It's used to indicate transient AP1 state. + +What: /sys/bus/platform/devices/dfl-port.0/ap2_event +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-write. Read or set 1 to clear AP2 (AFU Power State 2) + event. It's used to indicate transient AP2 state. + +What: /sys/bus/platform/devices/dfl-port.0/ltr +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-write. Read and set AFU latency tolerance reporting value. + Set ltr to 1 if the AFU can tolerate latency >= 40us or set it + to 0 if it is latency sensitive.
drivers/fpga/dfl-afu-main.c +140 -0
157 lines not on this page · raw message
drivers/fpga/dfl.h +11 -0
@@ -119,6 +119,7 @@#define PORT_HDR_NEXT_AFU NEXT_AFU#define PORT_HDR_CAP 0x30#define PORT_HDR_CTRL 0x38 +#define PORT_HDR_STS 0x40/* Port Capability Register Bitfield */ #define PORT_CAP_PORT_NUM GENMASK_ULL(1, 0)/* ID of this port */
@@ -130,6 +131,16 @@/* Latency tolerance reporting. '1' >= 40us, '0' < 40us.*/ #define PORT_CTRL_LATENCY BIT_ULL(2)#define PORT_CTRL_SFTRST_ACK BIT_ULL(4)/* HW ack for reset */ + +/* Port Status Register Bitfield */ +#define PORT_STS_AP2_EVT BIT_ULL(13)/* AP2 event detected */ +#define PORT_STS_AP1_EVT BIT_ULL(12)/* AP1 event detected */ +#define PORT_STS_PWR_STATE GENMASK_ULL(11, 8)/* AFU power states */ +#define PORT_STS_PWR_STATE_NORM 0 +#define PORT_STS_PWR_STATE_AP1 1/* 50% throttling */ +#define PORT_STS_PWR_STATE_AP2 2/* 90% throttling */ +#define PORT_STS_PWR_STATE_AP6 6/* 100% throttling */ +/** * struct dfl_fpga_port_ops - port ops *
Signature · 1 line
1.8.3.1
PATCH v4 9/15 fpga: dfl: afu: add userclock sysfs interfaces.
In reply to Wu HaoThis patch introduces userclock sysfs interfaces for AFU, user could use these interfaces for clock setting to AFU.
Please note that, this is only working for port header feature with revision 0, for later revisions, userclock setting is moved to a separated private feature, so one revision sysfs interface is exposed to userspace application for this purpose too.
---
v3: replace scnprintf with sprintf in sysfs interfaces.
update sysfs doc kernel version and date.
v4: update sysfs doc date.
--- Documentation/ABI/testing/sysfs-platform-dfl-port | 35 +++++++ drivers/fpga/dfl-afu-main.c | 113 +++++++++++++++++++++- drivers/fpga/dfl.h | 4 + 3 files changed, 151 insertions(+), 1 deletion(-)
Documentation/ABI/testing/sysfs-platform-dfl-port +35 -0
@@ -44,3 +44,38 @@ Contact: Wu Hao <[email protected]> Description: Read-write. Read and set AFU latency tolerance reporting value. Set ltr to 1 if the AFU can tolerate latency >= 40us or set it to 0 if it is latency sensitive. + +What: /sys/bus/platform/devices/dfl-port.0/revision +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the revision of port header + feature. + +What: /sys/bus/platform/devices/dfl-port.0/userclk_freqcmd +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Write-only. User writes command to this interface to set + userclock to AFU. + +What: /sys/bus/platform/devices/dfl-port.0/userclk_freqsts +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the status of issued command + to userclck_freqcmd. + +What: /sys/bus/platform/devices/dfl-port.0/userclk_freqcntrcmd +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Write-only. User writes command to this interface to set + userclock counter. + +What: /sys/bus/platform/devices/dfl-port.0/userclk_freqcntrsts +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the status of issued command + to userclck_freqcntrcmd.
drivers/fpga/dfl-afu-main.c +112 -1
144 lines not on this page · raw message
drivers/fpga/dfl.h +4 -0
@@ -120,6 +120,10 @@#define PORT_HDR_CAP 0x30#define PORT_HDR_CTRL 0x38#define PORT_HDR_STS 0x40 +#define PORT_HDR_USRCLK_CMD0 0x50 +#define PORT_HDR_USRCLK_CMD1 0x58 +#define PORT_HDR_USRCLK_STS0 0x60 +#define PORT_HDR_USRCLK_STS1 0x68/* Port Capability Register Bitfield */ #define PORT_CAP_PORT_NUM GENMASK_ULL(1, 0)/* ID of this port */
Signature · 1 line
1.8.3.1
PATCH v4 10/15 fpga: dfl: add id_table for dfl private feature driver
In reply to Wu HaoThis patch adds id_table for each dfl private feature driver, it allows to reuse same private feature driver to match and support multiple dfl private features.
--- drivers/fpga/dfl-afu-main.c | 14 ++++++++++++-- drivers/fpga/dfl-fme-main.c | 11 ++++++++--- drivers/fpga/dfl-fme-pr.c | 7 ++++++- drivers/fpga/dfl-fme.h | 3 ++- drivers/fpga/dfl.c | 21 +++++++++++++++++++-- drivers/fpga/dfl.h | 21 +++++++++++++++------ 6 files changed, 62 insertions(+), 15 deletions(-)
drivers/fpga/dfl-afu-main.c +12 -2
@@ -435,6 +435,11 @@ static void port_hdr_uinit(struct platform_device *pdev,return ret; } +static const struct dfl_feature_id port_hdr_id_table[] = { + {.id =PORT_FEATURE_ID_HEADER ,}, + {0 ,} +}; +static const struct dfl_feature_ops port_hdr_ops = { .init = port_hdr_init, .uinit = port_hdr_uinit,
@@ -495,6 +500,11 @@ static void port_afu_uinit(struct platform_device *pdev,sysfs_remove_files (&pdev->dev.kobj, port_afu_attrs); } +static const struct dfl_feature_id port_afu_id_table[] = { + {.id =PORT_FEATURE_ID_AFU ,}, + {0 ,} +}; +static const struct dfl_feature_ops port_afu_ops = { .init = port_afu_init, .uinit = port_afu_uinit,
@@ -502,11 +512,11 @@ static void port_afu_uinit(struct platform_device *pdev,static struct dfl_feature_driver port_feature_drvs[] = { { - .id =PORT_FEATURE_ID_HEADER , + .id_table = port_hdr_id_table, .ops = &port_hdr_ops, }, { - .id =PORT_FEATURE_ID_AFU , + .id_table = port_afu_id_table, .ops = &port_afu_ops, }, {
drivers/fpga/dfl-fme-main.c +8 -3
@@ -158,6 +158,11 @@ static long fme_hdr_ioctl(struct platform_device *pdev,return -ENODEV ; } +static const struct dfl_feature_id fme_hdr_id_table[] = { + {.id =FME_FEATURE_ID_HEADER ,}, + {0 ,} +}; +static const struct dfl_feature_ops fme_hdr_ops = { .init = fme_hdr_init, .uinit = fme_hdr_uinit,
@@ -166,12 +171,12 @@ static long fme_hdr_ioctl(struct platform_device *pdev,static struct dfl_feature_driver fme_feature_drvs[] = { { - .id =FME_FEATURE_ID_HEADER , + .id_table = fme_hdr_id_table, .ops = &fme_hdr_ops, }, { - .id =FME_FEATURE_ID_PR_MGMT , - .ops = &pr_mgmt_ops, + .id_table = fme_pr_mgmt_id_table, + .ops = &fme_pr_mgmt_ops, }, { .ops =NULL ,
drivers/fpga/dfl-fme-pr.c +6 -1
@@ -483,7 +483,12 @@ static long fme_pr_ioctl(struct platform_device *pdev,return ret; } -const struct dfl_feature_ops pr_mgmt_ops = { +const struct dfl_feature_id fme_pr_mgmt_id_table[] = { + {.id =FME_FEATURE_ID_PR_MGMT ,}, + {0 } +}; + +const struct dfl_feature_ops fme_pr_mgmt_ops = { .init = pr_mgmt_init, .uinit = pr_mgmt_uinit, .ioctl = fme_pr_ioctl,
drivers/fpga/dfl-fme.h +2 -1
@@ -35,6 +35,7 @@ struct dfl_fme { struct dfl_feature_platform_data *pdata; }; -extern const struct dfl_feature_ops pr_mgmt_ops; +extern const struct dfl_feature_ops fme_pr_mgmt_ops; +extern const struct dfl_feature_id fme_pr_mgmt_id_table[];#endif /* __DFL_FME_H */
drivers/fpga/dfl.c +19 -2
@@ -14,6 +14,8 @@#include "dfl.h" +#define DRV_VERSION "0.8" +static DEFINE_MUTEX (dfl_id_mutex);/*
@@ -281,6 +283,21 @@ static int dfl_feature_instance_init(struct platform_device *pdev,return ret; } +static bool dfl_feature_drv_match (struct dfl_feature *feature, +struct dfl_feature_driver *driver) +{ +const struct dfl_feature_id *ids = driver->id_table; + +if (ids) { +while (ids->id) { +if (ids->id == feature->id) +return true; + ids++; + } + } +return false; +} +/** * dfl_fpga_dev_feature_init - init for sub features of dfl feature device * @pdev: feature device.
@@ -301,8 +318,7 @@ int dfl_fpga_dev_feature_init(struct platform_device *pdev,while (drv->ops) {dfl_fpga_dev_for_each_feature (pdata, feature) { -/* match feature and drv using id */ -if (feature->id == drv->id) { +if (dfl_feature_drv_match (feature, drv)) { ret =dfl_feature_instance_init (pdev, pdata, feature, drv);if (ret)
@@ -1178,3 +1194,4 @@ static void __exit dfl_fpga_exit(void)MODULE_DESCRIPTION ("FPGA Device Feature List (DFL) Support" );MODULE_AUTHOR ("Intel Corporation" );MODULE_LICENSE ("GPL v2" ); +MODULE_VERSION (DRV_VERSION );
drivers/fpga/dfl.h +15 -6
@@ -30,8 +30,8 @@/* plus one for fme device */ #define MAX_DFL_FEATURE_DEV_NUM (MAX_DFL_FPGA_PORT_NUM + 1) -/* Reserved 0x0 for Header Group Register and 0xff for AFU */ -#define FEATURE_ID_FIU_HEADER 0x0 +/* Reserved 0xfe for Header Group Register and 0xff for AFU */ +#define FEATURE_ID_FIU_HEADER 0xfe#define FEATURE_ID_AFU 0xff#define FME_FEATURE_ID_HEADER FEATURE_ID_FIU_HEADER
@@ -169,13 +169,22 @@ struct dfl_fpga_port_ops {int dfl_fpga_check_port_id (struct platform_device *pdev,void *pport_id);/** -* struct dfl_feature_driver - sub feature's driver +* struct dfl_feature_id - dfl private feature id * -* @id: sub feature id. -* @ops: ops of this sub feature. +* @id: unique dfl private feature id. */ -struct dfl_feature_driver { +struct dfl_feature_id {u64 id; +}; + +/** +* struct dfl_feature_driver - dfl private feature driver +* +* @id_table: id_table for dfl private features supported by this driver. +* @ops: ops of this dfl private feature driver. +*/ +struct dfl_feature_driver { +const struct dfl_feature_id *id_table;const struct dfl_feature_ops *ops; };
Signature · 1 line
1.8.3.1
PATCH v4 11/15 fpga: dfl: afu: export __port_enable/disable function.
In reply to Wu HaoAs these two functions are used by other private features. e.g. in error reporting private feature, it requires to check port status and reset port for error clearing.
--- drivers/fpga/dfl-afu-main.c | 25 ++++++++++++++----------- drivers/fpga/dfl-afu.h | 3 +++ 2 files changed, 17 insertions(+), 11 deletions(-)
drivers/fpga/dfl-afu-main.c +14 -11
@@ -24,14 +24,16 @@#define DRV_VERSION "0.8"/** -* port_enable - enable a port +* __port_enable - enable a port * @pdev: port platform device. * * Enable Port by clear the port soft reset bit, which is set by default. * The AFU is unable to respond to any MMIO access while in reset. -* port_enable function should only be used after port_disable function. +* __port_enable function should only be used after __port_disable function. +* +* The caller needs to hold lock for protection. */ -static void port_enable (struct platform_device *pdev) +void __port_enable (struct platform_device *pdev) {struct dfl_feature_platform_data *pdata =dev_get_platdata (&pdev->dev);void __iomem *base;
@@ -54,13 +56,14 @@ static void port_enable(struct platform_device *pdev)#define RST_POLL_TIMEOUT 1000/* us */ /** -* port_disable - disable a port +* __port_disable - disable a port * @pdev: port platform device. * -* Disable Port by setting the port soft reset bit, it puts the port into -* reset. +* Disable Port by setting the port soft reset bit, it puts the port into reset. +* +* The caller needs to hold lock for protection. */ -static int port_disable (struct platform_device *pdev) +int __port_disable (struct platform_device *pdev) {struct dfl_feature_platform_data *pdata =dev_get_platdata (&pdev->dev);void __iomem *base;
@@ -106,9 +109,9 @@ static int __port_reset(struct platform_device *pdev) {int ret; - ret =port_disable (pdev); + ret =__port_disable (pdev);if (!ret) -port_enable (pdev); +__port_enable (pdev);return ret; }
@@ -805,9 +808,9 @@ static int port_enable_set(struct platform_device *pdev, bool enable)mutex_lock (&pdata->lock);if (enable) -port_enable (pdev); +__port_enable (pdev);else - ret =port_disable (pdev); + ret =__port_disable (pdev);mutex_unlock (&pdata->lock);return ret;
drivers/fpga/dfl-afu.h +3 -0
@@ -79,6 +79,9 @@ struct dfl_afu {struct dfl_feature_platform_data *pdata; }; +void __port_enable (struct platform_device *pdev); +int __port_disable (struct platform_device *pdev); +void afu_mmio_region_init (struct dfl_feature_platform_data *pdata);int afu_mmio_region_add (struct dfl_feature_platform_data *pdata,u32 region_index,u64 region_size,u64 phys,u32 flags);
Signature · 1 line
1.8.3.1
PATCH v4 12/15 fpga: dfl: afu: add error reporting support.
In reply to Wu HaoError reporting is one important private feature, it reports error detected on port and accelerated function unit (AFU). It introduces several sysfs interfaces to allow userspace to check and clear errors detected by hardware.
---
v2: add more error code description for error clear sysfs in doc.
return -EINVAL instead of -EBUSY when input error code doesn't match in error clear sysfs.
v3: replace scnprintf with sprintf in sysfs interfaces.
update sysfs doc kernel version and date.
v4: update sysfs doc date.
--- Documentation/ABI/testing/sysfs-platform-dfl-port | 39 ++++ drivers/fpga/Makefile | 1 + drivers/fpga/dfl-afu-error.c | 225 ++++++++++++++++++++++ drivers/fpga/dfl-afu-main.c | 4 + drivers/fpga/dfl-afu.h | 4 + 5 files changed, 273 insertions(+) create mode 100644 drivers/fpga/dfl-afu-error.c
Documentation/ABI/testing/sysfs-platform-dfl-port +39 -0
@@ -79,3 +79,42 @@ KernelVersion: 5.3 Contact: Wu Hao <[email protected]> Description: Read-only. Read this file to get the status of issued command to userclck_freqcntrcmd. + +What: /sys/bus/platform/devices/dfl-port.0/errors/revision +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the revision of this error + reporting private feature. + +What: /sys/bus/platform/devices/dfl-port.0/errors/errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get errors detected on port and + Accelerated Function Unit (AFU). + +What: /sys/bus/platform/devices/dfl-port.0/errors/first_error +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the first error detected by + hardware. + +What: /sys/bus/platform/devices/dfl-port.0/errors/first_malformed_req +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the first malformed request + captured by hardware. + +What: /sys/bus/platform/devices/dfl-port.0/errors/clear +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Write-only. Write error code to this file to clear errors. + Write fails with -EINVAL if input parsing fails or input error + code doesn't match. + Write fails with -EBUSY or -ETIMEDOUT if error can't be cleared + as hardware is in low power state (-EBUSY) or not responding + (-ETIMEDOUT).
drivers/fpga/Makefile +1 -0
@@ -41,6 +41,7 @@ obj-$(CONFIG_FPGA_DFL_AFU) += dfl-afu.o dfl-fme-objs := dfl-fme-main.o dfl-fme-pr.o dfl-afu-objs := dfl-afu-main.o dfl-afu-region.o dfl-afu-dma-region.o +dfl-afu-objs += dfl-afu-error.o # Drivers for FPGAs which implement DFL obj-$(CONFIG_FPGA_DFL_PCI) += dfl-pci.o
drivers/fpga/dfl-afu-error.c new file +225 -0
225 lines not on this page · raw message
drivers/fpga/dfl-afu-main.c +4 -0
@@ -523,6 +523,10 @@ static void port_afu_uinit(struct platform_device *pdev, .ops = &port_afu_ops, }, { + .id_table = port_err_id_table, + .ops = &port_err_ops, + }, + { .ops = NULL, } };
drivers/fpga/dfl-afu.h +4 -0
@@ -100,4 +100,8 @@ int afu_dma_map_region(struct dfl_feature_platform_data *pdata,struct dfl_afu_dma_region *afu_dma_region_find (struct dfl_feature_platform_data *pdata,u64 iova,u64 size); + +extern const struct dfl_feature_ops port_err_ops; +extern const struct dfl_feature_id port_err_id_table[]; +#endif /* __DFL_AFU_H */
Signature · 1 line
1.8.3.1
PATCH v4 13/15 fpga: dfl: afu: add STP (SignalTap) support
In reply to Wu HaoSTP (SignalTap) is one of the private features under the port for debugging. This patch adds private feature driver support for it to allow userspace applications to mmap related mmio region and provide STP service.
--- drivers/fpga/dfl-afu-main.c | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/fpga/dfl-afu-main.c +34 -0
@@ -513,6 +513,36 @@ static void port_afu_uinit(struct platform_device *pdev, .uinit = port_afu_uinit, }; +static int port_stp_init (struct platform_device *pdev, +struct dfl_feature *feature) +{ +struct resource *res = &pdev->resource[feature->resource_index]; + +dev_dbg (&pdev->dev,"PORT STP Init.\n" ); + +return afu_mmio_region_add (dev_get_platdata (&pdev->dev), +DFL_PORT_REGION_INDEX_STP , +resource_size (res), res->start, +DFL_PORT_REGION_MMAP |DFL_PORT_REGION_READ | +DFL_PORT_REGION_WRITE ); +} + +static void port_stp_uinit (struct platform_device *pdev, +struct dfl_feature *feature) +{ +dev_dbg (&pdev->dev,"PORT STP UInit.\n" ); +} + +static const struct dfl_feature_id port_stp_id_table[] = { + {.id =PORT_FEATURE_ID_STP ,}, + {0 ,} +}; + +static const struct dfl_feature_ops port_stp_ops = { + .init = port_stp_init, + .uinit = port_stp_uinit, +}; +static struct dfl_feature_driver port_feature_drvs[] = { { .id_table = port_hdr_id_table,
@@ -527,6 +557,10 @@ static void port_afu_uinit(struct platform_device *pdev, .ops = &port_err_ops, }, { + .id_table = port_stp_id_table, + .ops = &port_stp_ops, + }, + { .ops = NULL, } };
Signature · 1 line
1.8.3.1
PATCH v4 14/15 fpga: dfl: fme: add capability sysfs interfaces
In reply to Wu HaoThis patch adds 3 read-only sysfs interfaces for FPGA Management Engine (FME) block for capabilities including cache_size, fabric_version and socket_id.
---
v3: replace scnprintf with sprintf in sysfs interfaces.
update sysfs doc kernel version and date.
v4: update sysfs doc date.
--- Documentation/ABI/testing/sysfs-platform-dfl-fme | 23 ++++++++++++ drivers/fpga/dfl-fme-main.c | 48 ++++++++++++++++++++++++ 2 files changed, 71 insertions(+)
Documentation/ABI/testing/sysfs-platform-dfl-fme +23 -0
@@ -21,3 +21,26 @@ Contact: Wu Hao <[email protected]> Description: Read-only. It returns Bitstream (static FPGA region) meta data, which includes the synthesis date, seed and other information of this static FPGA region. + +What: /sys/bus/platform/devices/dfl-fme.0/cache_size +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It returns cache size of this FPGA device. + +What: /sys/bus/platform/devices/dfl-fme.0/fabric_version +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It returns fabric version of this FPGA device. + Userspace applications need this information to select + best data channels per different fabric design. + +What: /sys/bus/platform/devices/dfl-fme.0/socket_id +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It returns socket_id to indicate which socket + this FPGA belongs to, only valid for integrated solution. + User only needs this information, in case standard numa node + can't provide correct information.
drivers/fpga/dfl-fme-main.c +48 -0
58 lines not on this page · raw message
Signature · 1 line
1.8.3.1
PATCH v4 15/15 fpga: dfl: fme: add global error reporting support
In reply to Wu HaoThis patch adds support for global error reporting for FPGA Management Engine (FME), it introduces sysfs interfaces to report different error detected by the hardware, and allow user to clear errors or inject error for testing purpose.
---
v2: fix issues found in sysfs doc.
fix returned error code issues for writable sysfs interfaces. (use -EINVAL if input doesn't match error code) reorder the sysfs groups in code.
v3: code rebase.
replace scnprintf with sprintf in sysfs interfaces. update sysfs doc kernel version and date.
v4: update sysfs doc date.
--- Documentation/ABI/testing/sysfs-platform-dfl-fme | 75 +++++ drivers/fpga/Makefile | 2 +- drivers/fpga/dfl-fme-error.c | 385 +++++++++++++++++++++++ drivers/fpga/dfl-fme-main.c | 4 + drivers/fpga/dfl-fme.h | 2 + drivers/fpga/dfl.h | 2 + 6 files changed, 469 insertions(+), 1 deletion(-) create mode 100644 drivers/fpga/dfl-fme-error.c
Documentation/ABI/testing/sysfs-platform-dfl-fme +75 -0
@@ -44,3 +44,78 @@ Description: Read-only. It returns socket_id to indicate which socket this FPGA belongs to, only valid for integrated solution. User only needs this information, in case standard numa node can't provide correct information. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/revision +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the revision of this global + error reporting private feature. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/pcie0_errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-Write. Read this file for errors detected on pcie0 link. + Write this file to clear errors logged in pcie0_errors. Write + fails with -EINVAL if input parsing fails or input error code + doesn't match. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/pcie1_errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-Write. Read this file for errors detected on pcie1 link. + Write this file to clear errors logged in pcie1_errors. Write + fails with -EINVAL if input parsing fails or input error code + doesn't match. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/nonfatal_errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It returns non-fatal errors detected. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/catfatal_errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. It returns catastrophic and fatal errors detected. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/inject_error +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-Write. Read this file to check errors injected. Write this + file to inject errors for testing purpose. Write fails with + -EINVAL if input parsing fails or input inject error code isn't + supported. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/fme-errors/errors +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get errors detected by hardware. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/fme-errors/first_error +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the first error detected by + hardware. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/fme-errors/next_error +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Read-only. Read this file to get the second error detected by + hardware. + +What: /sys/bus/platform/devices/dfl-fme.0/errors/fme-errors/clear +Date: June 2019 +KernelVersion: 5.3 +Contact: Wu Hao <[email protected]> +Description: Write-only. Write error code to this file to clear all errors + logged in errors, first_error and next_error. Write fails with + -EINVAL if input parsing fails or input error code doesn't + match.
drivers/fpga/Makefile +1 -1
@@ -39,7 +39,7 @@ obj-$(CONFIG_FPGA_DFL_FME_BRIDGE) += dfl-fme-br.o obj-$(CONFIG_FPGA_DFL_FME_REGION) += dfl-fme-region.o obj-$(CONFIG_FPGA_DFL_AFU) += dfl-afu.o -dfl-fme-objs := dfl-fme-main.o dfl-fme-pr.o +dfl-fme-objs := dfl-fme-main.o dfl-fme-pr.o dfl-fme-error.o dfl-afu-objs := dfl-afu-main.o dfl-afu-region.o dfl-afu-dma-region.o dfl-afu-objs += dfl-afu-error.o
drivers/fpga/dfl-fme-error.c new file +385 -0
385 lines not on this page · raw message
drivers/fpga/dfl-fme-main.c +4 -0
@@ -227,6 +227,10 @@ static long fme_hdr_ioctl(struct platform_device *pdev, .ops = &fme_pr_mgmt_ops, }, { + .id_table = fme_global_err_id_table, + .ops = &fme_global_err_ops, + }, + { .ops = NULL, }, };
drivers/fpga/dfl-fme.h +2 -0
@@ -37,5 +37,7 @@ struct dfl_fme {extern const struct dfl_feature_ops fme_pr_mgmt_ops;extern const struct dfl_feature_id fme_pr_mgmt_id_table[]; +extern const struct dfl_feature_ops fme_global_err_ops; +extern const struct dfl_feature_id fme_global_err_id_table[];#endif /* __DFL_FME_H */
drivers/fpga/dfl.h +2 -0
@@ -197,12 +197,14 @@ struct dfl_feature_driver {* feature dev (platform device)'s reources. * @ioaddr: mapped mmio resource address. * @ops: ops of this sub feature. +* @priv: priv data of this feature. */ struct dfl_feature {u64 id;int resource_index;void __iomem *ioaddr;const struct dfl_feature_ops *ops; +void *priv; };#define DEV_STATUS_IN_USE 0
Signature · 1 line
1.8.3.1