Documentation/admin-guide/thunderbolt.rst

1 .. SPDX-License-Identifier: GPL-2.0
8 manager is an entity running on the host router (host controller)
22 is expected to be accompanied with an IOMMU based DMA protection.
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
41 vulnerable to DMA attacks.
46 be DMA masters and thus read contents of the host memory without CPU and OS
95 -----------------------------------------------------------------
98   /sys/bus/thunderbolt/devices/0-1/authorized	- 0
99   /sys/bus/thunderbolt/devices/0-1/device	- 0x8004
100   /sys/bus/thunderbolt/devices/0-1/device_name	- Thunderbolt to FireWire Adapter
101   /sys/bus/thunderbolt/devices/0-1/vendor	- 0x1
102   /sys/bus/thunderbolt/devices/0-1/vendor_name	- Apple, Inc.
103   /sys/bus/thunderbolt/devices/0-1/unique_id	- e0376f00-0300-0100-ffff-ffffffffffff
108   # echo 1 > /sys/bus/thunderbolt/devices/0-1/authorized
114 a random 32-byte value used for authorization and challenging the device in
117   /sys/bus/thunderbolt/devices/0-3/authorized	- 0
118   /sys/bus/thunderbolt/devices/0-3/device	- 0x305
119   /sys/bus/thunderbolt/devices/0-3/device_name	- AKiTiO Thunder3 PCIe Box
120   /sys/bus/thunderbolt/devices/0-3/key		-
121   /sys/bus/thunderbolt/devices/0-3/vendor	- 0x41
122   /sys/bus/thunderbolt/devices/0-3/vendor_name	- inXtron
123   /sys/bus/thunderbolt/devices/0-3/unique_id	- dc010000-0000-8508-a22d-32ca6421cb16
134   # key=$(openssl rand -hex 32)
135   # echo $key > /sys/bus/thunderbolt/devices/0-3/key
136   # echo 1 > /sys/bus/thunderbolt/devices/0-3/authorized
144   # echo $key > /sys/bus/thunderbolt/devices/0-3/key
145   # echo 2 > /sys/bus/thunderbolt/devices/0-3/authorized
156 DMA protection utilizing IOMMU
157 ------------------------------
166 The driver does not do anything special in this case but because DMA
171 authorize devices when IOMMU DMA protection is enabled can use the
177 ----------------------------------------------------
198 device - then you need to connect that particular device).
200 Note an OEM-specific method to power the controller up ("force power") may
204 After that we can write the firmware to the non-active parts of the NVM
208   # dd if=KYK_TBT_FW_0018.bin of=/sys/bus/thunderbolt/devices/0-0/nvm_non_active0/nvmem
213   # echo 1 > /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
223   # cat /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
225   # cat /sys/bus/thunderbolt/devices/0-0/nvm_version
237 --------------------------------------------------
248 ---------------------------------
257 ``thunderbolt-net`` driver is loaded automatically. If the other host is
258 also Linux you should load ``thunderbolt-net`` manually on one host (it
261   # modprobe thunderbolt-net
264 is built-in to the kernel image, there is no need to do anything.
272 -------------
278 For example the intel-wmi-thunderbolt driver exposes this attribute in:
279   /sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power