1 What: /sys/bus/thunderbolt/devices/. 1 What: /sys/bus/thunderbolt/devices/.../domainX/boot_acl
2 Date: Jun 2018 2 Date: Jun 2018
3 KernelVersion: 4.17 3 KernelVersion: 4.17
4 Contact: Mika Westerberg <mika.westerber !! 4 Contact: thunderbolt-software@lists.01.org
5 Description: Holds a comma separated list o 5 Description: Holds a comma separated list of device unique_ids that
6 are allowed to be connected au 6 are allowed to be connected automatically during system
7 startup (e.g boot devices). Th 7 startup (e.g boot devices). The list always contains
8 maximum supported number of un 8 maximum supported number of unique_ids where unused
9 entries are empty. This allows 9 entries are empty. This allows the userspace software
10 to determine how many entries 10 to determine how many entries the controller supports.
11 If there are multiple controll 11 If there are multiple controllers, each controller has
12 its own ACL list and size may 12 its own ACL list and size may be different between the
13 controllers. 13 controllers.
14 14
15 System BIOS may have an option 15 System BIOS may have an option "Preboot ACL" or similar
16 that needs to be selected befo 16 that needs to be selected before this list is taken into
17 consideration. 17 consideration.
18 18
19 Software always updates a full 19 Software always updates a full list in each write.
20 20
21 If a device is authorized auto 21 If a device is authorized automatically during boot its
22 boot attribute is set to 1. 22 boot attribute is set to 1.
23 23
24 What: /sys/bus/thunderbolt/devices/. 24 What: /sys/bus/thunderbolt/devices/.../domainX/deauthorization
25 Date: May 2021 25 Date: May 2021
26 KernelVersion: 5.12 26 KernelVersion: 5.12
27 Contact: Mika Westerberg <mika.westerber 27 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
28 Description: This attribute tells whether t 28 Description: This attribute tells whether the system supports
29 de-authorization of devices. V 29 de-authorization of devices. Value of 1 means user can
30 de-authorize PCIe tunnel by wr 30 de-authorize PCIe tunnel by writing 0 to authorized
31 attribute under each device. 31 attribute under each device.
32 32
33 What: /sys/bus/thunderbolt/devices/. 33 What: /sys/bus/thunderbolt/devices/.../domainX/iommu_dma_protection
34 Date: Mar 2019 34 Date: Mar 2019
35 KernelVersion: 4.21 35 KernelVersion: 4.21
36 Contact: Mika Westerberg <mika.westerber !! 36 Contact: thunderbolt-software@lists.01.org
37 Description: This attribute tells whether t 37 Description: This attribute tells whether the system uses IOMMU
38 for DMA protection. Value of 1 38 for DMA protection. Value of 1 means IOMMU is used 0 means
39 it is not (DMA protection is s 39 it is not (DMA protection is solely based on Thunderbolt
40 security levels). 40 security levels).
41 41
42 What: /sys/bus/thunderbolt/devices/. 42 What: /sys/bus/thunderbolt/devices/.../domainX/security
43 Date: Sep 2017 43 Date: Sep 2017
44 KernelVersion: 4.13 44 KernelVersion: 4.13
45 Contact: Mika Westerberg <mika.westerber !! 45 Contact: thunderbolt-software@lists.01.org
46 Description: This attribute holds current T 46 Description: This attribute holds current Thunderbolt security level
47 set by the system BIOS. Possib 47 set by the system BIOS. Possible values are:
48 48
49 ======= ===================== 49 ======= ==================================================
50 none All devices are autom 50 none All devices are automatically authorized
51 user Devices are only auth 51 user Devices are only authorized based on writing
52 appropriate value to 52 appropriate value to the authorized attribute
53 secure Require devices that 53 secure Require devices that support secure connect at
54 minimum. User needs t 54 minimum. User needs to authorize each device.
55 dponly Automatically tunnel 55 dponly Automatically tunnel Display port (and USB). No
56 PCIe tunnels are crea 56 PCIe tunnels are created.
57 usbonly Automatically tunnel 57 usbonly Automatically tunnel USB controller of the
58 connected Thunderbolt 58 connected Thunderbolt dock (and Display Port). All
59 PCIe links downstream 59 PCIe links downstream of the dock are removed.
60 nopcie USB4 system where PCI 60 nopcie USB4 system where PCIe tunneling is disabled from
61 the BIOS. 61 the BIOS.
62 ======= ===================== 62 ======= ==================================================
63 63
64 What: /sys/bus/thunderbolt/devices/. 64 What: /sys/bus/thunderbolt/devices/.../authorized
65 Date: Sep 2017 65 Date: Sep 2017
66 KernelVersion: 4.13 66 KernelVersion: 4.13
67 Contact: Mika Westerberg <mika.westerber !! 67 Contact: thunderbolt-software@lists.01.org
68 Description: This attribute is used to auth 68 Description: This attribute is used to authorize Thunderbolt devices
69 after they have been connected 69 after they have been connected. If the device is not
70 authorized, no PCIe devices ar 70 authorized, no PCIe devices are available to the system.
71 71
72 Contents of this attribute wil 72 Contents of this attribute will be 0 when the device is not
73 yet authorized. 73 yet authorized.
74 74
75 Possible values are supported: 75 Possible values are supported:
76 76
77 == ========================== 77 == ===================================================
78 0 The device will be de-auth 78 0 The device will be de-authorized (only supported if
79 deauthorization attribute 79 deauthorization attribute under domain contains 1)
80 1 The device will be authori 80 1 The device will be authorized and connected
81 == ========================== 81 == ===================================================
82 82
83 When key attribute contains 32 83 When key attribute contains 32 byte hex string the possible
84 values are: 84 values are:
85 85
86 == ========================== 86 == ========================================================
87 0 The device will be de-auth 87 0 The device will be de-authorized (only supported if
88 deauthorization attribute 88 deauthorization attribute under domain contains 1)
89 1 The 32 byte hex string is 89 1 The 32 byte hex string is added to the device NVM and
90 the device is authorized. 90 the device is authorized.
91 2 Send a challenge based on 91 2 Send a challenge based on the 32 byte hex string. If the
92 challenge response from de 92 challenge response from device is valid, the device is
93 authorized. In case of fai 93 authorized. In case of failure errno will be ENOKEY if
94 the device did not contain 94 the device did not contain a key at all, and
95 EKEYREJECTED if the challe 95 EKEYREJECTED if the challenge response did not match.
96 == ========================== 96 == ========================================================
97 97
98 What: /sys/bus/thunderbolt/devices/. 98 What: /sys/bus/thunderbolt/devices/.../boot
99 Date: Jun 2018 99 Date: Jun 2018
100 KernelVersion: 4.17 100 KernelVersion: 4.17
101 Contact: Mika Westerberg <mika.westerber !! 101 Contact: thunderbolt-software@lists.01.org
102 Description: This attribute contains 1 if T 102 Description: This attribute contains 1 if Thunderbolt device was already
103 authorized on boot and 0 other 103 authorized on boot and 0 otherwise.
104 104
105 What: /sys/bus/thunderbolt/devices/. 105 What: /sys/bus/thunderbolt/devices/.../generation
106 Date: Jan 2020 106 Date: Jan 2020
107 KernelVersion: 5.5 107 KernelVersion: 5.5
108 Contact: Christian Kellner <christian@ke 108 Contact: Christian Kellner <christian@kellner.me>
109 Description: This attribute contains the ge 109 Description: This attribute contains the generation of the Thunderbolt
110 controller associated with the 110 controller associated with the device. It will contain 4
111 for USB4. 111 for USB4.
112 112
113 What: /sys/bus/thunderbolt/devices/. 113 What: /sys/bus/thunderbolt/devices/.../key
114 Date: Sep 2017 114 Date: Sep 2017
115 KernelVersion: 4.13 115 KernelVersion: 4.13
116 Contact: Mika Westerberg <mika.westerber !! 116 Contact: thunderbolt-software@lists.01.org
117 Description: When a devices supports Thunde 117 Description: When a devices supports Thunderbolt secure connect it will
118 have this attribute. Writing 3 118 have this attribute. Writing 32 byte hex string changes
119 authorization to use the secur 119 authorization to use the secure connection method instead.
120 Writing an empty string clears 120 Writing an empty string clears the key and regular connection
121 method can be used again. 121 method can be used again.
122 122
123 What: /sys/bus/thunderbolt/devices/. 123 What: /sys/bus/thunderbolt/devices/.../device
124 Date: Sep 2017 124 Date: Sep 2017
125 KernelVersion: 4.13 125 KernelVersion: 4.13
126 Contact: Mika Westerberg <mika.westerber !! 126 Contact: thunderbolt-software@lists.01.org
127 Description: This attribute contains id of 127 Description: This attribute contains id of this device extracted from
128 the device DROM. 128 the device DROM.
129 129
130 What: /sys/bus/thunderbolt/devices/. 130 What: /sys/bus/thunderbolt/devices/.../device_name
131 Date: Sep 2017 131 Date: Sep 2017
132 KernelVersion: 4.13 132 KernelVersion: 4.13
133 Contact: Mika Westerberg <mika.westerber !! 133 Contact: thunderbolt-software@lists.01.org
134 Description: This attribute contains name o 134 Description: This attribute contains name of this device extracted from
135 the device DROM. 135 the device DROM.
136 136
137 What: /sys/bus/thunderbolt/devices/. 137 What: /sys/bus/thunderbolt/devices/.../maxhopid
138 Date: Jul 2021 138 Date: Jul 2021
139 KernelVersion: 5.13 139 KernelVersion: 5.13
140 Contact: Mika Westerberg <mika.westerber 140 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
141 Description: Only set for XDomains. The max 141 Description: Only set for XDomains. The maximum HopID the other host
142 supports as its input HopID. 142 supports as its input HopID.
143 143
144 What: /sys/bus/thunderbolt/devices/. 144 What: /sys/bus/thunderbolt/devices/.../rx_speed
145 Date: Jan 2020 145 Date: Jan 2020
146 KernelVersion: 5.5 146 KernelVersion: 5.5
147 Contact: Mika Westerberg <mika.westerber 147 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
148 Description: This attribute reports the dev 148 Description: This attribute reports the device RX speed per lane.
149 All RX lanes run at the same s 149 All RX lanes run at the same speed.
150 150
151 What: /sys/bus/thunderbolt/devices/. 151 What: /sys/bus/thunderbolt/devices/.../rx_lanes
152 Date: Jan 2020 152 Date: Jan 2020
153 KernelVersion: 5.5 153 KernelVersion: 5.5
154 Contact: Mika Westerberg <mika.westerber 154 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
155 Description: This attribute reports number 155 Description: This attribute reports number of RX lanes the device is
156 using simultaneously through i 156 using simultaneously through its upstream port.
157 157
158 What: /sys/bus/thunderbolt/devices/. 158 What: /sys/bus/thunderbolt/devices/.../tx_speed
159 Date: Jan 2020 159 Date: Jan 2020
160 KernelVersion: 5.5 160 KernelVersion: 5.5
161 Contact: Mika Westerberg <mika.westerber 161 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
162 Description: This attribute reports the TX 162 Description: This attribute reports the TX speed per lane.
163 All TX lanes run at the same s 163 All TX lanes run at the same speed.
164 164
165 What: /sys/bus/thunderbolt/devices/. 165 What: /sys/bus/thunderbolt/devices/.../tx_lanes
166 Date: Jan 2020 166 Date: Jan 2020
167 KernelVersion: 5.5 167 KernelVersion: 5.5
168 Contact: Mika Westerberg <mika.westerber 168 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
169 Description: This attribute reports number 169 Description: This attribute reports number of TX lanes the device is
170 using simultaneously through i 170 using simultaneously through its upstream port.
171 171
172 What: /sys/bus/thunderbolt/devices/. 172 What: /sys/bus/thunderbolt/devices/.../vendor
173 Date: Sep 2017 173 Date: Sep 2017
174 KernelVersion: 4.13 174 KernelVersion: 4.13
175 Contact: Mika Westerberg <mika.westerber !! 175 Contact: thunderbolt-software@lists.01.org
176 Description: This attribute contains vendor 176 Description: This attribute contains vendor id of this device extracted
177 from the device DROM. 177 from the device DROM.
178 178
179 What: /sys/bus/thunderbolt/devices/. 179 What: /sys/bus/thunderbolt/devices/.../vendor_name
180 Date: Sep 2017 180 Date: Sep 2017
181 KernelVersion: 4.13 181 KernelVersion: 4.13
182 Contact: Mika Westerberg <mika.westerber !! 182 Contact: thunderbolt-software@lists.01.org
183 Description: This attribute contains vendor 183 Description: This attribute contains vendor name of this device extracted
184 from the device DROM. 184 from the device DROM.
185 185
186 What: /sys/bus/thunderbolt/devices/. 186 What: /sys/bus/thunderbolt/devices/.../unique_id
187 Date: Sep 2017 187 Date: Sep 2017
188 KernelVersion: 4.13 188 KernelVersion: 4.13
189 Contact: Mika Westerberg <mika.westerber !! 189 Contact: thunderbolt-software@lists.01.org
190 Description: This attribute contains unique 190 Description: This attribute contains unique_id string of this device.
191 This is either read from hardw 191 This is either read from hardware registers (UUID on
192 newer hardware) or based on UI 192 newer hardware) or based on UID from the device DROM.
193 Can be used to uniquely identi 193 Can be used to uniquely identify particular device.
194 194
195 What: /sys/bus/thunderbolt/devices/. 195 What: /sys/bus/thunderbolt/devices/.../nvm_version
196 Date: Sep 2017 196 Date: Sep 2017
197 KernelVersion: 4.13 197 KernelVersion: 4.13
198 Contact: Mika Westerberg <mika.westerber !! 198 Contact: thunderbolt-software@lists.01.org
199 Description: If the device has upgradeable 199 Description: If the device has upgradeable firmware the version
200 number is available here. Form 200 number is available here. Format: %x.%x, major.minor.
201 If the device is in safe mode 201 If the device is in safe mode reading the file returns
202 -ENODATA instead as the NVM ve 202 -ENODATA instead as the NVM version is not available.
203 203
204 What: /sys/bus/thunderbolt/devices/. 204 What: /sys/bus/thunderbolt/devices/.../nvm_authenticate
205 Date: Sep 2017 205 Date: Sep 2017
206 KernelVersion: 4.13 206 KernelVersion: 4.13
207 Contact: Mika Westerberg <mika.westerber !! 207 Contact: thunderbolt-software@lists.01.org
208 Description: When new NVM image is written 208 Description: When new NVM image is written to the non-active NVM
209 area (through non_activeX NVMe 209 area (through non_activeX NVMem device), the
210 authentication procedure is st 210 authentication procedure is started by writing to
211 this file. 211 this file.
212 If everything goes well, the d 212 If everything goes well, the device is
213 restarted with the new NVM fir 213 restarted with the new NVM firmware. If the image
214 verification fails an error co 214 verification fails an error code is returned instead.
215 215
216 This file will accept writing 216 This file will accept writing values "1", "2" or "3".
217 217
218 - Writing "1" will flush the i 218 - Writing "1" will flush the image to the storage
219 area and authenticate the im 219 area and authenticate the image in one action.
220 - Writing "2" will run some ba 220 - Writing "2" will run some basic validation on the image
221 and flush it to the storage 221 and flush it to the storage area.
222 - Writing "3" will authenticat 222 - Writing "3" will authenticate the image that is
223 currently written in the sto 223 currently written in the storage area. This is only
224 supported with USB4 devices 224 supported with USB4 devices and retimers.
225 225
226 When read holds status of the 226 When read holds status of the last authentication
227 operation if an error occurred 227 operation if an error occurred during the process. This
228 is directly the status value f 228 is directly the status value from the DMA configuration
229 based mailbox before the devic 229 based mailbox before the device is power cycled. Writing
230 0 here clears the status. 230 0 here clears the status.
231 231
232 What: /sys/bus/thunderbolt/devices/. 232 What: /sys/bus/thunderbolt/devices/.../nvm_authenticate_on_disconnect
233 Date: Oct 2020 233 Date: Oct 2020
234 KernelVersion: v5.9 234 KernelVersion: v5.9
235 Contact: Mario Limonciello <mario.limonc 235 Contact: Mario Limonciello <mario.limonciello@outlook.com>
236 Description: For supported devices, automat 236 Description: For supported devices, automatically authenticate the new Thunderbolt
237 image when the device is disco 237 image when the device is disconnected from the host system.
238 238
239 This file will accept writing 239 This file will accept writing values "1" or "2"
240 240
241 - Writing "1" will flush the i 241 - Writing "1" will flush the image to the storage
242 area and prepare the device 242 area and prepare the device for authentication on disconnect.
243 - Writing "2" will run some ba 243 - Writing "2" will run some basic validation on the image
244 and flush it to the storage 244 and flush it to the storage area.
245 245
246 What: /sys/bus/thunderbolt/devices/< 246 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/key
247 Date: Jan 2018 247 Date: Jan 2018
248 KernelVersion: 4.15 248 KernelVersion: 4.15
249 Contact: Mika Westerberg <mika.westerber !! 249 Contact: thunderbolt-software@lists.01.org
250 Description: This contains name of the prop 250 Description: This contains name of the property directory the XDomain
251 service exposes. This entry de 251 service exposes. This entry describes the protocol in
252 question. Following directorie 252 question. Following directories are already reserved by
253 the Apple XDomain specificatio 253 the Apple XDomain specification:
254 254
255 ======== ==================== 255 ======== ===============================================
256 network IP/ethernet over Thu 256 network IP/ethernet over Thunderbolt
257 targetdm Target disk mode pro 257 targetdm Target disk mode protocol over Thunderbolt
258 extdisp External display mod 258 extdisp External display mode protocol over Thunderbolt
259 ======== ==================== 259 ======== ===============================================
260 260
261 What: /sys/bus/thunderbolt/devices/< 261 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/modalias
262 Date: Jan 2018 262 Date: Jan 2018
263 KernelVersion: 4.15 263 KernelVersion: 4.15
264 Contact: Mika Westerberg <mika.westerber !! 264 Contact: thunderbolt-software@lists.01.org
265 Description: Stores the same MODALIAS value 265 Description: Stores the same MODALIAS value emitted by uevent for
266 the XDomain service. Format: t 266 the XDomain service. Format: tbtsvc:kSpNvNrN
267 267
268 What: /sys/bus/thunderbolt/devices/< 268 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcid
269 Date: Jan 2018 269 Date: Jan 2018
270 KernelVersion: 4.15 270 KernelVersion: 4.15
271 Contact: Mika Westerberg <mika.westerber !! 271 Contact: thunderbolt-software@lists.01.org
272 Description: This contains XDomain protocol 272 Description: This contains XDomain protocol identifier the XDomain
273 service supports. 273 service supports.
274 274
275 What: /sys/bus/thunderbolt/devices/< 275 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcvers
276 Date: Jan 2018 276 Date: Jan 2018
277 KernelVersion: 4.15 277 KernelVersion: 4.15
278 Contact: Mika Westerberg <mika.westerber !! 278 Contact: thunderbolt-software@lists.01.org
279 Description: This contains XDomain protocol 279 Description: This contains XDomain protocol version the XDomain
280 service supports. 280 service supports.
281 281
282 What: /sys/bus/thunderbolt/devices/< 282 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcrevs
283 Date: Jan 2018 283 Date: Jan 2018
284 KernelVersion: 4.15 284 KernelVersion: 4.15
285 Contact: Mika Westerberg <mika.westerber !! 285 Contact: thunderbolt-software@lists.01.org
286 Description: This contains XDomain software 286 Description: This contains XDomain software version the XDomain
287 service supports. 287 service supports.
288 288
289 What: /sys/bus/thunderbolt/devices/< 289 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcstns
290 Date: Jan 2018 290 Date: Jan 2018
291 KernelVersion: 4.15 291 KernelVersion: 4.15
292 Contact: Mika Westerberg <mika.westerber !! 292 Contact: thunderbolt-software@lists.01.org
293 Description: This contains XDomain service 293 Description: This contains XDomain service specific settings as
294 bitmask. Format: %x 294 bitmask. Format: %x
295 295
296 What: /sys/bus/thunderbolt/devices/u 296 What: /sys/bus/thunderbolt/devices/usb4_portX/connector
297 Date: April 2022 297 Date: April 2022
298 Contact: Heikki Krogerus <heikki.krogeru 298 Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
299 Description: 299 Description:
300 Symlink to the USB Type-C conn 300 Symlink to the USB Type-C connector. This link is only
301 created when USB Type-C Connec 301 created when USB Type-C Connector Class is enabled,
302 and only if the system firmwar 302 and only if the system firmware is capable of
303 describing the connection betw 303 describing the connection between a port and its
304 connector. 304 connector.
305 305
306 What: /sys/bus/thunderbolt/devices/u 306 What: /sys/bus/thunderbolt/devices/usb4_portX/link
307 Date: Sep 2021 307 Date: Sep 2021
308 KernelVersion: v5.14 308 KernelVersion: v5.14
309 Contact: Mika Westerberg <mika.westerber 309 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
310 Description: Returns the current link mode. 310 Description: Returns the current link mode. Possible values are
311 "usb4", "tbt" and "none". 311 "usb4", "tbt" and "none".
312 312
313 What: /sys/bus/thunderbolt/devices/u 313 What: /sys/bus/thunderbolt/devices/usb4_portX/offline
314 Date: Sep 2021 314 Date: Sep 2021
315 KernelVersion: v5.14 315 KernelVersion: v5.14
316 Contact: Rajmohan Mani <rajmohan.mani@in 316 Contact: Rajmohan Mani <rajmohan.mani@intel.com>
317 Description: Writing 1 to this attribute pu 317 Description: Writing 1 to this attribute puts the USB4 port into
318 offline mode. Only allowed whe 318 offline mode. Only allowed when there is nothing
319 connected to the port (link at 319 connected to the port (link attribute returns "none").
320 Once the port is in offline mo 320 Once the port is in offline mode it does not receive any
321 hotplug events. This is used t 321 hotplug events. This is used to update NVM firmware of
322 on-board retimers. Writing 0 p 322 on-board retimers. Writing 0 puts the port back to
323 online mode. 323 online mode.
324 324
325 This attribute is only visible 325 This attribute is only visible if the platform supports
326 powering on retimers when ther 326 powering on retimers when there is no cable connected.
327 327
328 What: /sys/bus/thunderbolt/devices/u 328 What: /sys/bus/thunderbolt/devices/usb4_portX/rescan
329 Date: Sep 2021 329 Date: Sep 2021
330 KernelVersion: v5.14 330 KernelVersion: v5.14
331 Contact: Rajmohan Mani <rajmohan.mani@in 331 Contact: Rajmohan Mani <rajmohan.mani@intel.com>
332 Description: When the USB4 port is in offli 332 Description: When the USB4 port is in offline mode writing 1 to this
333 attribute forces rescan of the 333 attribute forces rescan of the sideband for on-board
334 retimers. Each retimer appear 334 retimers. Each retimer appear under the USB4 port as if
335 the USB4 link was up. These re 335 the USB4 link was up. These retimers act in the same way
336 as if the cable was connected 336 as if the cable was connected so upgrading their NVM
337 firmware can be done the usual 337 firmware can be done the usual way.
338 338
339 What: /sys/bus/thunderbolt/devices/< 339 What: /sys/bus/thunderbolt/devices/<device>:<port>.<index>/device
340 Date: Oct 2020 340 Date: Oct 2020
341 KernelVersion: v5.9 341 KernelVersion: v5.9
342 Contact: Mika Westerberg <mika.westerber 342 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
343 Description: Retimer device identifier read 343 Description: Retimer device identifier read from the hardware.
344 344
345 What: /sys/bus/thunderbolt/devices/< 345 What: /sys/bus/thunderbolt/devices/<device>:<port>.<index>/nvm_authenticate
346 Date: Oct 2020 346 Date: Oct 2020
347 KernelVersion: v5.9 347 KernelVersion: v5.9
348 Contact: Mika Westerberg <mika.westerber 348 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
349 Description: When new NVM image is written 349 Description: When new NVM image is written to the non-active NVM
350 area (through non_activeX NVMe 350 area (through non_activeX NVMem device), the
351 authentication procedure is st 351 authentication procedure is started by writing 1 to
352 this file. If everything goes 352 this file. If everything goes well, the device is
353 restarted with the new NVM fir 353 restarted with the new NVM firmware. If the image
354 verification fails an error co 354 verification fails an error code is returned instead.
355 355
356 When read holds status of the 356 When read holds status of the last authentication
357 operation if an error occurred 357 operation if an error occurred during the process.
358 Format: %x. 358 Format: %x.
359 359
360 What: /sys/bus/thunderbolt/devices/< 360 What: /sys/bus/thunderbolt/devices/<device>:<port>.<index>/nvm_version
361 Date: Oct 2020 361 Date: Oct 2020
362 KernelVersion: v5.9 362 KernelVersion: v5.9
363 Contact: Mika Westerberg <mika.westerber 363 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
364 Description: Holds retimer NVM version numb 364 Description: Holds retimer NVM version number. Format: %x.%x, major.minor.
365 365
366 What: /sys/bus/thunderbolt/devices/< 366 What: /sys/bus/thunderbolt/devices/<device>:<port>.<index>/vendor
367 Date: Oct 2020 367 Date: Oct 2020
368 KernelVersion: v5.9 368 KernelVersion: v5.9
369 Contact: Mika Westerberg <mika.westerber 369 Contact: Mika Westerberg <mika.westerberg@linux.intel.com>
370 Description: Retimer vendor identifier read 370 Description: Retimer vendor identifier read from the hardware.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.