aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing
diff options
context:
space:
mode:
authorIan Munsie <imunsie@au1.ibm.com>2015-02-04 03:09:01 -0500
committerMichael Ellerman <mpe@ellerman.id.au>2015-02-05 19:16:56 -0500
commitb087e6190ddcd9ae4e8ff2c788d2b32f193e946b (patch)
treef62802d81710bb9a4c9c8b15ceb5fe4498828383 /Documentation/ABI/testing
parentc2c896bee08e1461fc24f9bf7dd57e2c63f6db70 (diff)
cxl: Export optional AFU configuration record in sysfs
An AFU may optionally contain one or more PCIe like configuration records, which can be used to identify the AFU. This patch adds support for exposing the raw config space and the vendor, device and class code under sysfs. These will appear in a subdirectory of the AFU device corresponding with the configuration record number, e.g. cat /sys/class/cxl/afu0.0/cr0/vendor 0x1014 cat /sys/class/cxl/afu0.0/cr0/device 0x4350 cat /sys/class/cxl/afu0.0/cr0/class 0x120000 hexdump -C /sys/class/cxl/afu0.0/cr0/config 00000000 14 10 50 43 00 00 00 00 06 00 00 12 00 00 00 00 |..PC............| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000100 These files behave in much the same way as the equivalent files for PCI devices, with one exception being that the config file is currently read-only and restricted to the root user. It is not necessarily required to be this strict, but we currently do not have a compelling use-case to make it writable and/or world-readable, so I erred on the side of being restrictive. Signed-off-by: Ian Munsie <imunsie@au1.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'Documentation/ABI/testing')
-rw-r--r--Documentation/ABI/testing/sysfs-class-cxl37
1 files changed, 37 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-class-cxl b/Documentation/ABI/testing/sysfs-class-cxl
index 9ea01068a16c..3680364b4048 100644
--- a/Documentation/ABI/testing/sysfs-class-cxl
+++ b/Documentation/ABI/testing/sysfs-class-cxl
@@ -81,6 +81,43 @@ Description: read only
81 this this kernel supports. 81 this this kernel supports.
82 82
83 83
84AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):
85
86An AFU may optionally export one or more PCIe like configuration records, known
87as AFU configuration records, which will show up here (if present).
88
89What: /sys/class/cxl/<afu>/cr<config num>/vendor
90Date: February 2015
91Contact: linuxppc-dev@lists.ozlabs.org
92Description: read only
93 Hexadecimal value of the vendor ID found in this AFU
94 configuration record.
95
96What: /sys/class/cxl/<afu>/cr<config num>/device
97Date: February 2015
98Contact: linuxppc-dev@lists.ozlabs.org
99Description: read only
100 Hexadecimal value of the device ID found in this AFU
101 configuration record.
102
103What: /sys/class/cxl/<afu>/cr<config num>/vendor
104Date: February 2015
105Contact: linuxppc-dev@lists.ozlabs.org
106Description: read only
107 Hexadecimal value of the class code found in this AFU
108 configuration record.
109
110What: /sys/class/cxl/<afu>/cr<config num>/config
111Date: February 2015
112Contact: linuxppc-dev@lists.ozlabs.org
113Description: read only
114 This binary file provides raw access to the AFU configuration
115 record. The format is expected to match the either the standard
116 or extended configuration space defined by the PCIe
117 specification.
118
119
120
84Master contexts (eg. /sys/class/cxl/afu0.0m) 121Master contexts (eg. /sys/class/cxl/afu0.0m)
85 122
86What: /sys/class/cxl/<afu>m/mmio_size 123What: /sys/class/cxl/<afu>m/mmio_size