Add retimer interfaces support for Intel MAX 10 BMC
Xu Yilun
maintainercover Add retimer interfaces support for Intel MAX 10 BMC
This patchset supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
The 2 retimer chips connect to the Intel MAX 10 BMC on the card. They are managed by the BMC firmware. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on the BMC. The driver creates sysfs interfaces for users to query these information.
Xu Yilun (2):
mfd: intel-m10-bmc: specify the retimer sub devices
misc: add support for retimers interfaces on Intel MAX 10 BMC
.../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/mfd/intel-m10-bmc.c | 19 ++- drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ include/linux/mfd/intel-m10-bmc.h | 7 + 6 files changed, 226 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.c
Signature · 1 line
2.7.4
Xu Yilun
maintainerPATCH 1/2 mfd: intel-m10-bmc: specify the retimer sub devices
The patch specifies the 2 retimer sub devices and their resources in the parent driver's mfd_cell. It also adds the register definition of the retimer sub devices.
There are 2 ethernet retimer chips (C827) connected to the Intel MAX 10 BMC. They are managed by the BMC firmware, and host could query them via retimer interfaces (shared registers) on the BMC. The 2 retimers have identical register interfaces in different register addresses or fields, so it is better we define 2 retimer devices and handle them with the same driver.
--- drivers/mfd/intel-m10-bmc.c | 19 ++++++++++++++++++- include/linux/mfd/intel-m10-bmc.h | 7 +++++++ 2 files changed, 25 insertions(+), 1 deletion(-)
drivers/mfd/intel-m10-bmc.c +18 -1
@@ -17,9 +17,26 @@ enum m10bmc_type { M10_N3000, }; +static struct resource retimer0_resources[] = { + {M10BMC_PKVL_A_VER ,M10BMC_PKVL_A_VER ,"version" ,IORESOURCE_REG , }, +}; + +static struct resource retimer1_resources[] = { + {M10BMC_PKVL_B_VER ,M10BMC_PKVL_B_VER ,"version" ,IORESOURCE_REG , }, +}; +static struct mfd_cell m10bmc_pacn3000_subdevs[] = { { .name ="n3000bmc-hwmon" }, - { .name ="n3000bmc-retimer" }, + { + .name ="n3000bmc-retimer" , + .num_resources =ARRAY_SIZE (retimer0_resources), + .resources = retimer0_resources, + }, + { + .name ="n3000bmc-retimer" , + .num_resources =ARRAY_SIZE (retimer1_resources), + .resources = retimer1_resources, + }, { .name ="n3000bmc-secure" }, };
include/linux/mfd/intel-m10-bmc.h +7 -0
@@ -21,6 +21,13 @@#define M10BMC_VER_PCB_INFO_MSK GENMASK(31, 24)#define M10BMC_VER_LEGACY_INVALID 0xffffffff +/* Retimer related registers, in system register region */ +#define M10BMC_PKVL_LSTATUS 0x164 +#define M10BMC_PKVL_A_VER 0x254 +#define M10BMC_PKVL_B_VER 0x258 +#define M10BMC_PKVL_SERDES_VER GENMASK(15, 0) +#define M10BMC_PKVL_SBUS_VER GENMASK(31, 16) +/** * struct intel_m10bmc - Intel MAX 10 BMC parent driver data structure * @dev: this device
Signature · 1 line
2.7.4
Re: [PATCH 1/2] mfd: intel-m10-bmc: specify the retimer sub devices
Quoted 22 lines · Xu Yilun
The patch specifies the 2 retimer sub devices and their resources in the parent driver's
mfd_cell. It also adds the register definition of the retimer sub devices.There are 2 ethernet retimer chips (C827) connected to the Intel MAX 10 BMC. They are managed by the BMC firmware, and host could query them via retimer interfaces (shared registers) on the BMC. The 2 retimers have identical register interfaces in different register addresses or fields, so it is better we define 2 retimer devices and handle them with the same driver.
Signed-off-by Xu Yilun <[email protected]>--- drivers/mfd/intel-m10-bmc.c | 19 ++++++++++++++++++- include/linux/mfd/intel-m10-bmc.h | 7 +++++++ 2 files changed, 25 insertions(+), 1 deletion(-)drivers/mfd/intel-m10-bmc.c +0
-0
drivers/mfd/intel-m10-bmc.c enum m10bmc_type { · line 26
Quoted 10 lines
drivers/mfd/intel-m10-bmc.c +7
-0@@ -17,9 +17,26 @@ enum m10bmc_type { M10_N3000, }; +static struct resource retimer0_resources[] = { + {M10BMC_PKVL_A_VER ,M10BMC_PKVL_A_VER ,"version" ,IORESOURCE_REG , }, +}; + +static struct resource retimer1_resources[] = { + {M10BMC_PKVL_B_VER ,M10BMC_PKVL_B_VER ,"version" ,IORESOURCE_REG , }, +};
Please use the DEFINE_RES_*() helpers for this.
Quoted 34 lines
drivers/mfd/intel-m10-bmc.c +10
-1static struct mfd_cell m10bmc_pacn3000_subdevs[] = { { .name ="n3000bmc-hwmon" }, - { .name ="n3000bmc-retimer" }, + { + .name ="n3000bmc-retimer" , + .num_resources =ARRAY_SIZE (retimer0_resources), + .resources = retimer0_resources, + }, + { + .name ="n3000bmc-retimer" , + .num_resources =ARRAY_SIZE (retimer1_resources), + .resources = retimer1_resources, + }, { .name ="n3000bmc-secure" }, };include/linux/mfd/intel-m10-bmc.h +7
-0@@ -21,6 +21,13 @@#define M10BMC_VER_PCB_INFO_MSK GENMASK(31, 24)#define M10BMC_VER_LEGACY_INVALID 0xffffffff +/* Retimer related registers, in system register region */ +#define M10BMC_PKVL_LSTATUS 0x164 +#define M10BMC_PKVL_A_VER 0x254 +#define M10BMC_PKVL_B_VER 0x258 +#define M10BMC_PKVL_SERDES_VER GENMASK(15, 0) +#define M10BMC_PKVL_SBUS_VER GENMASK(31, 16) +/** * struct intel_m10bmc - Intel MAX 10 BMC parent driver data structure * @dev: this device
Signature · 4 lines
Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog
Xu Yilun
maintainerRe: [PATCH 1/2] mfd: intel-m10-bmc: specify the retimer sub devices
Quoted 27 lines · Lee Jones
Quoted 25 lines · Xu Yilun
The patch specifies the 2 retimer sub devices and their resources in the parent driver's
mfd_cell. It also adds the register definition of the retimer sub devices.There are 2 ethernet retimer chips (C827) connected to the Intel MAX 10 BMC. They are managed by the BMC firmware, and host could query them via retimer interfaces (shared registers) on the BMC. The 2 retimers have identical register interfaces in different register addresses or fields, so it is better we define 2 retimer devices and handle them with the same driver.
Signed-off-by Xu Yilun <[email protected]>--- drivers/mfd/intel-m10-bmc.c | 19 ++++++++++++++++++- include/linux/mfd/intel-m10-bmc.h | 7 +++++++ 2 files changed, 25 insertions(+), 1 deletion(-)drivers/mfd/intel-m10-bmc.c +0
-0@@ -17,9 +17,26 @@ enum m10bmc_type { M10_N3000, };
Quoted 9 lines
drivers/mfd/intel-m10-bmc.c enum m10bmc_type { · line 26
Quoted 7 lines
drivers/mfd/intel-m10-bmc.c +7
-0+static struct resource retimer0_resources[] = { + {M10BMC_PKVL_A_VER ,M10BMC_PKVL_A_VER ,"version" ,IORESOURCE_REG , }, +}; + +static struct resource retimer1_resources[] = { + {M10BMC_PKVL_B_VER ,M10BMC_PKVL_B_VER ,"version" ,IORESOURCE_REG , }, +};Please use the DEFINE_RES_*() helpers for this.
Yes, will change it.
Thanks,
Yilun
Xu Yilun
maintainerPATCH 2/2 misc: add support for retimers interfaces on Intel MAX 10 BMC
In reply to Xu YilunThis driver supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
C827 is an Intel(R) Ethernet serdes transceiver chip that supports up to 100G transfer. On Intel PAC N3000 there are 2 C827 chips managed by the Intel MAX 10 BMC firmware. They are configured in 4 ports 10G/25G retimer mode. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on Intel MAX 10 BMC. The driver creates sysfs interfaces for users to query these information.
--- .../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ 4 files changed, 201 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.c
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +32 -0
@@ -0,0 +1,32 @@ +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/tag +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the tag of the retimer chip. Now there are 2 + retimer chips on Intel PAC N3000, they are tagged as + 'retimer_A' and 'retimer_B'. + Format: "retimer_%c". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/sbus_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the Transceiver bus firmware version of + the retimer chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/serdes_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the SERDES firmware version of the retimer + chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/link_statusX +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the status of each line side link. "1" for + link up, "0" for link down. + Format: "%u".
drivers/misc/Kconfig +10 -0
@@ -466,6 +466,16 @@ config HISI_HIKEY_USB switching between the dual-role USB-C port and the USB-A host ports using only one USB controller. +config INTEL_M10_BMC_RETIMER + tristate "Intel(R) MAX 10 BMC ethernet retimer interface support" + depends on MFD_INTEL_M10_BMC + help + This driver supports the ethernet retimer (C827) on Intel(R) MAX 10 + BMC, which is used by Intel PAC N3000 FPGA based Smart NIC. + + To compile this driver as a module, choose M here: the module will + be called intel-m10-bmc-retimer. + source "drivers/misc/c2port/Kconfig" source "drivers/misc/eeprom/Kconfig" source "drivers/misc/cb710/Kconfig"
drivers/misc/Makefile +1 -0
@@ -57,3 +57,4 @@ obj-$(CONFIG_HABANA_AI) += habanalabs/ obj-$(CONFIG_UACCE) += uacce/ obj-$(CONFIG_XILINX_SDFEC) += xilinx_sdfec.o obj-$(CONFIG_HISI_HIKEY_USB) += hisi_hikey_usb.o +obj-$(CONFIG_INTEL_M10_BMC_RETIMER) += intel-m10-bmc-retimer.o
drivers/misc/intel-m10-bmc-retimer.c new file +158 -0
158 lines not on this page · raw message
Signature · 1 line
2.7.4
Greg KH
maintainerRe: [PATCH 2/2] misc: add support for retimers interfaces on Intel MAX 10 BMC
Quoted 49 lines · Xu Yilun
This driver supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
C827 is an Intel(R) Ethernet serdes transceiver chip that supports up to 100G transfer. On Intel PAC N3000 there are 2 C827 chips managed by the Intel MAX 10 BMC firmware. They are configured in 4 ports 10G/25G retimer mode. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on Intel MAX 10 BMC. The driver creates sysfs interfaces for users to query these information.
Signed-off-by Xu Yilun <[email protected]>--- .../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ 4 files changed, 201 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.cDocumentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +22
-0@@ -0,0 +1,32 @@ +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/tag +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the tag of the retimer chip. Now there are 2 + retimer chips on Intel PAC N3000, they are tagged as + 'retimer_A' and 'retimer_B'. + Format: "retimer_%c". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/sbus_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the Transceiver bus firmware version of + the retimer chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/serdes_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the SERDES firmware version of the retimer
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer line 32
Quoted 10 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +10
-0+ chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/link_statusX +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the status of each line side link. "1" for + link up, "0" for link down. + Format: "%u".
Who is going to use all of these read-only attributes?
And why isn't this information exported in the "normal" way for network devices? Having them as custom sysfs attributes ensures that no existing tools will work with these at all, right? Why not do the standard thing here isntead?
thanks,
greg k-h
Xu Yilun
maintainerRe: [PATCH 2/2] misc: add support for retimers interfaces on Intel MAX 10 BMC
Quoted 54 lines · Greg KH
Quoted 53 lines · Xu Yilun
This driver supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
C827 is an Intel(R) Ethernet serdes transceiver chip that supports up to 100G transfer. On Intel PAC N3000 there are 2 C827 chips managed by the Intel MAX 10 BMC firmware. They are configured in 4 ports 10G/25G retimer mode. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on Intel MAX 10 BMC. The driver creates sysfs interfaces for users to query these information.
Signed-off-by Xu Yilun <[email protected]>--- .../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ 4 files changed, 201 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.cDocumentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +26
-0@@ -0,0 +1,32 @@ +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/tag +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the tag of the retimer chip. Now there are 2 + retimer chips on Intel PAC N3000, they are tagged as + 'retimer_A' and 'retimer_B'. + Format: "retimer_%c". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/sbus_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the Transceiver bus firmware version of + the retimer chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/serdes_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the SERDES firmware version of the retimer + chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/link_statusX
Quoted 8 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer line 32
Quoted 6 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +6
-0+Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the status of each line side link. "1" for + link up, "0" for link down. + Format: "%u".Who is going to use all of these read-only attributes?
The Intel OPAE (Open Programmable Acceleration Engine) lib handles these attrs.
For the version attrs, the OPAE retimer firmware update tool will query them to make sure the update is succeed.
For the link_status attrs, the OPAE net tools handles it.
Quoted 5 lines
And why isn't this information exported in the "normal" way for network devices? Having them as custom sysfs attributes ensures that no existing tools will work with these at all, right? Why not do the standard thing here isntead?
I had sent some RFC patches to expose the Line Side Ether Group + retimer + QSFP as a netdev, and got some comments from netdev Maintainers.
The network part of the N3000 card is like the following:
+----------------------------------------+
| FPGA |
+----+ +-------+ +-----------+ +----------+ +-----------+ +----------+
|QSFP|---|retimer|---|Line Side |--|User logic|--|Host Side |---|XL710 |
+----+ +-------+ |Ether Group| | | |Ether Group| |Ethernet |
|(PHY + MAC)| |wiring & | |(MAC + PHY)| |Controller|
+-----------+ |offloading| +-----------+ +----------+
| +----------+ |
| |
+----------------------------------------+The main concern is that physically the QSFP & retimer is managed by the BMC and host could only get the retimer link states. This is not enough to support some necessary netdev ops. E.g. host cannot realize the type/speed of the SFP by "ethtool -m", then users could not configure the various layers accordingly.
This means the existing net tool can not work with it, so this patch just expose the link states as custom sysfs attrs.
Thanks,
Yilun
Greg KH
maintainerRe: [PATCH 2/2] misc: add support for retimers interfaces on Intel MAX 10 BMC
Quoted 64 lines · Xu Yilun
Quoted 54 lines · Greg KH
Quoted 53 lines · Xu Yilun
This driver supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
C827 is an Intel(R) Ethernet serdes transceiver chip that supports up to 100G transfer. On Intel PAC N3000 there are 2 C827 chips managed by the Intel MAX 10 BMC firmware. They are configured in 4 ports 10G/25G retimer mode. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on Intel MAX 10 BMC. The driver creates sysfs interfaces for users to query these information.
Signed-off-by Xu Yilun <[email protected]>--- .../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ 4 files changed, 201 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.cDocumentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +26
-0@@ -0,0 +1,32 @@ +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/tag +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the tag of the retimer chip. Now there are 2 + retimer chips on Intel PAC N3000, they are tagged as + 'retimer_A' and 'retimer_B'. + Format: "retimer_%c". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/sbus_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the Transceiver bus firmware version of + the retimer chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/serdes_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the SERDES firmware version of the retimer + chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/link_statusXQuoted 8 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer line 32
Quoted 6 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +6
-0+Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the status of each line side link. "1" for + link up, "0" for link down. + Format: "%u".Who is going to use all of these read-only attributes?
Quoted 2 lines
The Intel OPAE (Open Programmable Acceleration Engine) lib handles these attrs.
I have no idea what that is, you should put a pointer to the source for this in either the changelog comment, or here in the sysfs entries to show who is using this.
Quoted 2 lines
For the version attrs, the OPAE retimer firmware update tool will query them to make sure the update is succeed.
Why does anyone care about that? The firmware download logic should handle that properly, right?
Quoted 1 line
For the
link_statusattrs, the OPAE net tools handles it.
So not the normal userspace networking tools?
If not, we need to get an ack from the networking developers as to why you are not following their existing user/kernel apis.
thanks,
greg k-h
Xu Yilun
maintainerRe: [PATCH 2/2] misc: add support for retimers interfaces on Intel MAX 10 BMC
Quoted 65 lines · Greg KH
Quoted 64 lines · Xu Yilun
Quoted 62 lines · Greg KH
Quoted 49 lines · Xu Yilun
This driver supports the ethernet retimers (C827) for the Intel PAC (Programmable Acceleration Card) N3000, which is a FPGA based Smart NIC.
C827 is an Intel(R) Ethernet serdes transceiver chip that supports up to 100G transfer. On Intel PAC N3000 there are 2 C827 chips managed by the Intel MAX 10 BMC firmware. They are configured in 4 ports 10G/25G retimer mode. Host could query their link states and firmware version information via retimer interfaces (Shared registers) on Intel MAX 10 BMC. The driver creates sysfs interfaces for users to query these information.
Signed-off-by Xu Yilun <[email protected]>--- .../ABI/testing/sysfs-driver-intel-m10-bmc-retimer | 32 +++++ drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/intel-m10-bmc-retimer.c | 158 +++++++++++++++++++++ 4 files changed, 201 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer create mode 100644 drivers/misc/intel-m10-bmc-retimer.cDocumentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +22
-0@@ -0,0 +1,32 @@ +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/tag +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the tag of the retimer chip. Now there are 2 + retimer chips on Intel PAC N3000, they are tagged as + 'retimer_A' and 'retimer_B'. + Format: "retimer_%c". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/sbus_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the Transceiver bus firmware version of + the retimer chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/serdes_version +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the SERDES firmware version of the retimerDocumentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer line 32
Quoted 10 lines
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-retimer new file +10
-0+ chip. + Format: "0x%04x". + +What: /sys/bus/platform/devices/n3000bmc-retimer.*.auto/link_statusX +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Xu Yilun <[email protected]> +Description: Read only. Returns the status of each line side link. "1" for + link up, "0" for link down. + Format: "%u".Who is going to use all of these read-only attributes?
Quoted 6 lines
Quoted 2 lines
The Intel OPAE (Open Programmable Acceleration Engine) lib handles these attrs.
I have no idea what that is, you should put a pointer to the source for this in either the changelog comment, or here in the sysfs entries to show who is using this.
This is the source of the OPAE lib.
https://github.com/OPAE/opae-sdk/
Generally it facilitate the development on all the DFL (Device Feature List) based FPGA Cards, including the management of static region & dynamic region reprogramming, accelerators accessing and the board specific peripherals.
I'll add the link in the changelog.
Quoted 6 lines
Quoted 3 lines
For the version attrs, the OPAE retimer firmware update tool will query them to make sure the update is succeed.
Why does anyone care about that? The firmware download logic should handle that properly, right?
Yes, the firmware download tool could always tells the update is succeed or fail. But on another day we may need to check where we are by reading the version numbers. An OPAE tool help collects the versions and users could then check the release notes to see the detailed change.
Quoted 7 lines
Quoted 2 lines
For the
link_statusattrs, the OPAE net tools handles it.So not the normal userspace networking tools?
If not, we need to get an ack from the networking developers as to why you are not following their existing user/kernel apis.
This is the previous thread:
https://lore.kernel.org/netdev/[email protected]/
I'll resend the patch and loop in the netdev maintainers for further discussion.
Thanks,
Yilun
Quoted 4 lines
thanks,
greg k-h