修改led为gpio

hc

2024-10-12 a5969cabbb4660eab42b6ef0412cbbd1200cf14d

 kernel/Documentation/ABI/testing/sysfs-bus-pci
..
..
@@ -7,8 +7,10 @@
7
7
 		this location.	This is useful for overriding default
8
8
 		bindings.  The format for the location is: DDDD:BB:DD.F.
9
9
 		That is Domain:Bus:Device.Function and is the same as
10
-		found in /sys/bus/pci/devices/.  For example:
11
-		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
10
+		found in /sys/bus/pci/devices/.  For example::
11
+
12
+		  # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
13
+
12
14
 		(Note: kernels before 2.6.28 may require echo -n).
13
15
 
14
16
 What:		/sys/bus/pci/drivers/.../unbind
..
..
@@ -20,8 +22,10 @@
20
22
 		this location.	This may be useful when overriding default
21
23
 		bindings.  The format for the location is: DDDD:BB:DD.F.
22
24
 		That is Domain:Bus:Device.Function and is the same as
23
-		found in /sys/bus/pci/devices/. For example:
24
-		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
25
+		found in /sys/bus/pci/devices/. For example::
26
+
27
+		  # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
28
+
25
29
 		(Note: kernels before 2.6.28 may require echo -n).
26
30
 
27
31
 What:		/sys/bus/pci/drivers/.../new_id
..
..
@@ -38,8 +42,9 @@
38
42
 		Class, Class Mask, and Private Driver Data.  The Vendor ID
39
43
 		and Device ID fields are required, the rest are optional.
40
44
 		Upon successfully adding an ID, the driver will probe
41
-		for the device and attempt to bind to it.  For example:
42
-		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
45
+		for the device and attempt to bind to it.  For example::
46
+
47
+		  # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
43
48
 
44
49
 What:		/sys/bus/pci/drivers/.../remove_id
45
50
 Date:		February 2009
..
..
@@ -54,8 +59,9 @@
54
59
 		required, the rest are optional.  After successfully
55
60
 		removing an ID, the driver will no longer support the
56
61
 		device.  This is useful to ensure auto probing won't
57
-		match the driver to the device.  For example:
58
-		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id
62
+		match the driver to the device.  For example::
63
+
64
+		  # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id
59
65
 
60
66
 What:		/sys/bus/pci/rescan
61
67
 Date:		January 2009
..
..
@@ -323,3 +329,40 @@
323
329
 
324
330
 		This is similar to /sys/bus/pci/drivers_autoprobe, but
325
331
 		affects only the VFs associated with a specific PF.
332
+
333
+What:		/sys/bus/pci/devices/.../p2pmem/size
334
+Date:		November 2017
335
+Contact:	Logan Gunthorpe <logang@deltatee.com>
336
+Description:
337
+		If the device has any Peer-to-Peer memory registered, this
338
+	        file contains the total amount of memory that the device
339
+		provides (in decimal).
340
+
341
+What:		/sys/bus/pci/devices/.../p2pmem/available
342
+Date:		November 2017
343
+Contact:	Logan Gunthorpe <logang@deltatee.com>
344
+Description:
345
+		If the device has any Peer-to-Peer memory registered, this
346
+	        file contains the amount of memory that has not been
347
+		allocated (in decimal).
348
+
349
+What:		/sys/bus/pci/devices/.../p2pmem/published
350
+Date:		November 2017
351
+Contact:	Logan Gunthorpe <logang@deltatee.com>
352
+Description:
353
+		If the device has any Peer-to-Peer memory registered, this
354
+	        file contains a '1' if the memory has been published for
355
+		use outside the driver that owns the device.
356
+
357
+What:		/sys/bus/pci/devices/.../link/clkpm
358
+		/sys/bus/pci/devices/.../link/l0s_aspm
359
+		/sys/bus/pci/devices/.../link/l1_aspm
360
+		/sys/bus/pci/devices/.../link/l1_1_aspm
361
+		/sys/bus/pci/devices/.../link/l1_2_aspm
362
+		/sys/bus/pci/devices/.../link/l1_1_pcipm
363
+		/sys/bus/pci/devices/.../link/l1_2_pcipm
364
+Date:		October 2019
365
+Contact:	Heiner Kallweit <hkallweit1@gmail.com>
366
+Description:	If ASPM is supported for an endpoint, these files can be
367
+		used to disable or enable the individual power management
368
+		states. Write y/1/on to enable, n/0/off to disable.