1 What: /sys/class/devlink/.../ 1 What: /sys/class/devlink/.../
2 Date: May 2020 2 Date: May 2020
3 Contact: Saravana Kannan <saravanak@goog 3 Contact: Saravana Kannan <saravanak@google.com>
4 Description: 4 Description:
5 Provide a place in sysfs for t 5 Provide a place in sysfs for the device link objects in the
6 kernel at any given time. The 6 kernel at any given time. The name of a device link directory,
7 denoted as ... above, is of th 7 denoted as ... above, is of the form <supplier>--<consumer>
8 where <supplier> is the suppli !! 8 where <supplier> is the supplier device name and <consumer> is
9 is the consumer bus:device nam !! 9 the consumer device name.
10 10
11 What: /sys/class/devlink/.../auto_re 11 What: /sys/class/devlink/.../auto_remove_on
12 Date: May 2020 12 Date: May 2020
13 Contact: Saravana Kannan <saravanak@goog 13 Contact: Saravana Kannan <saravanak@google.com>
14 Description: 14 Description:
15 This file indicates if the dev 15 This file indicates if the device link will ever be
16 automatically removed by the d 16 automatically removed by the driver core when the consumer and
17 supplier devices themselves ar 17 supplier devices themselves are still present.
18 18
19 This will be one of the follow 19 This will be one of the following strings:
20 20
21 - 'consumer unbind' !! 21 'consumer unbind'
22 - 'supplier unbind' !! 22 'supplier unbind'
23 - 'never' !! 23 'never'
24 24
25 'consumer unbind' means the de 25 'consumer unbind' means the device link will be removed when
26 the consumer's driver is unbou 26 the consumer's driver is unbound from the consumer device.
27 27
28 'supplier unbind' means the de 28 'supplier unbind' means the device link will be removed when
29 the supplier's driver is unbou 29 the supplier's driver is unbound from the supplier device.
30 30
31 'never' means the device link 31 'never' means the device link will not be automatically removed
32 when as long as the supplier a 32 when as long as the supplier and consumer devices themselves
33 are still present. 33 are still present.
34 34
35 What: /sys/class/devlink/.../consume 35 What: /sys/class/devlink/.../consumer
36 Date: May 2020 36 Date: May 2020
37 Contact: Saravana Kannan <saravanak@goog 37 Contact: Saravana Kannan <saravanak@google.com>
38 Description: 38 Description:
39 This file is a symlink to the 39 This file is a symlink to the consumer device's sysfs directory.
40 40
41 What: /sys/class/devlink/.../runtime 41 What: /sys/class/devlink/.../runtime_pm
42 Date: May 2020 42 Date: May 2020
43 Contact: Saravana Kannan <saravanak@goog 43 Contact: Saravana Kannan <saravanak@google.com>
44 Description: 44 Description:
45 This file indicates if the dev 45 This file indicates if the device link has any impact on the
46 runtime power management behav 46 runtime power management behavior of the consumer and supplier
47 devices. For example: Making s 47 devices. For example: Making sure the supplier doesn't enter
48 runtime suspend while the cons 48 runtime suspend while the consumer is active.
49 49
50 This will be one of the follow 50 This will be one of the following strings:
51 51
52 === ======================== !! 52 '0' - Does not affect runtime power management
53 '0' Does not affect runtime !! 53 '1' - Affects runtime power management
54 '1' Affects runtime power ma <<
55 === ======================== <<
56 54
57 What: /sys/class/devlink/.../status 55 What: /sys/class/devlink/.../status
58 Date: May 2020 56 Date: May 2020
59 Contact: Saravana Kannan <saravanak@goog 57 Contact: Saravana Kannan <saravanak@google.com>
60 Description: 58 Description:
61 This file indicates the status 59 This file indicates the status of the device link. The status
62 of a device link is affected b 60 of a device link is affected by whether the supplier and
63 consumer devices have been bou 61 consumer devices have been bound to their corresponding
64 drivers. The status of a devic 62 drivers. The status of a device link also affects the binding
65 and unbinding of the supplier 63 and unbinding of the supplier and consumer devices with their
66 drivers and also affects wheth 64 drivers and also affects whether the software state of the
67 supplier device is synced with 65 supplier device is synced with the hardware state of the
68 supplier device after boot up. 66 supplier device after boot up.
69 See also: sysfs-devices-state_ 67 See also: sysfs-devices-state_synced.
70 68
71 This will be one of the follow 69 This will be one of the following strings:
72 70
73 - 'not tracked' !! 71 'not tracked'
74 - 'dormant' !! 72 'dormant'
75 - 'available' !! 73 'available'
76 - 'consumer probing' !! 74 'consumer probing'
77 - 'active' !! 75 'active'
78 - 'supplier unbinding' !! 76 'supplier unbinding'
79 - 'unknown' !! 77 'unknown'
80 78
81 'not tracked' means this devic 79 'not tracked' means this device link does not track the status
82 and has no impact on the bindi 80 and has no impact on the binding, unbinding and syncing the
83 hardware and software device s 81 hardware and software device state.
84 82
85 'dormant' means the supplier a 83 'dormant' means the supplier and the consumer devices have not
86 bound to their driver. 84 bound to their driver.
87 85
88 'available' means the supplier 86 'available' means the supplier has bound to its driver and is
89 available to supply resources 87 available to supply resources to the consumer device.
90 88
91 'consumer probing' means the c 89 'consumer probing' means the consumer device is currently
92 trying to bind to its driver. 90 trying to bind to its driver.
93 91
94 'active' means the supplier an 92 'active' means the supplier and consumer devices have both
95 bound successfully to their dr 93 bound successfully to their drivers.
96 94
97 'supplier unbinding' means the 95 'supplier unbinding' means the supplier devices is currently in
98 the process of unbinding from 96 the process of unbinding from its driver.
99 97
100 'unknown' means the state of t 98 'unknown' means the state of the device link is not any of the
101 above. If this is ever the val 99 above. If this is ever the value, there's a bug in the kernel.
102 100
103 What: /sys/class/devlink/.../supplie 101 What: /sys/class/devlink/.../supplier
104 Date: May 2020 102 Date: May 2020
105 Contact: Saravana Kannan <saravanak@goog 103 Contact: Saravana Kannan <saravanak@google.com>
106 Description: 104 Description:
107 This file is a symlink to the 105 This file is a symlink to the supplier device's sysfs directory.
108 106
109 What: /sys/class/devlink/.../sync_st 107 What: /sys/class/devlink/.../sync_state_only
110 Date: May 2020 108 Date: May 2020
111 Contact: Saravana Kannan <saravanak@goog 109 Contact: Saravana Kannan <saravanak@google.com>
112 Description: 110 Description:
113 This file indicates if the dev 111 This file indicates if the device link is limited to only
114 affecting the syncing of the h 112 affecting the syncing of the hardware and software state of the
115 supplier device. 113 supplier device.
116 114
117 This will be one of the follow 115 This will be one of the following strings:
118 116
119 === ========================= <<
120 '0' 117 '0'
121 '1' Affects runtime power man !! 118 '1' - Affects runtime power management
122 === ========================= <<
123 119
124 '0' means the device link can 120 '0' means the device link can affect other device behaviors
125 like binding/unbinding, suspen 121 like binding/unbinding, suspend/resume, runtime power
126 management, etc. 122 management, etc.
127 123
128 '1' means the device link will 124 '1' means the device link will only affect the syncing of
129 hardware and software state of 125 hardware and software state of the supplier device after boot
130 up and doesn't not affect othe 126 up and doesn't not affect other behaviors of the devices.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.