Lines Matching full:thunderbolt
4 USB4 and Thunderbolt
6 USB4 is the public specification based on Thunderbolt 3 protocol with
11 Typically PCs come with a firmware connection manager for Thunderbolt 3
16 The Linux Thunderbolt driver supports both and can detect at runtime which
30 More details about the sysfs interface for Thunderbolt devices can be
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
37 ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1"
43 Starting with Intel Falcon Ridge Thunderbolt controller there are 4
63 ``/sys/bus/thunderbolt/devices``, the user then can make the decision.
88 ``/sys/bus/thunderbolt/devices/domainX/security`` where ``domainX`` is
89 the Thunderbolt domain the host controller manages. There is typically
90 one domain per Thunderbolt host controller.
96 Each Thunderbolt device plugged in will appear in sysfs under
97 ``/sys/bus/thunderbolt/devices``. The device directory carries
105 /sys/bus/thunderbolt/devices/0-1/authorized - 0
106 /sys/bus/thunderbolt/devices/0-1/device - 0x8004
107 /sys/bus/thunderbolt/devices/0-1/device_name - Thunderbolt to FireWire Adapter
108 /sys/bus/thunderbolt/devices/0-1/vendor - 0x1
109 /sys/bus/thunderbolt/devices/0-1/vendor_name - Apple, Inc.
110 /sys/bus/thunderbolt/devices/0-1/unique_id - e0376f00-0300-0100-ffff-ffffffffffff
115 # echo 1 > /sys/bus/thunderbolt/devices/0-1/authorized
124 /sys/bus/thunderbolt/devices/0-3/authorized - 0
125 /sys/bus/thunderbolt/devices/0-3/device - 0x305
126 /sys/bus/thunderbolt/devices/0-3/device_name - AKiTiO Thunder3 PCIe Box
127 /sys/bus/thunderbolt/devices/0-3/key -
128 /sys/bus/thunderbolt/devices/0-3/vendor - 0x41
129 /sys/bus/thunderbolt/devices/0-3/vendor_name - inXtron
130 /sys/bus/thunderbolt/devices/0-3/unique_id - dc010000-0000-8508-a22d-32ca6421cb16
142 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
143 # echo 1 > /sys/bus/thunderbolt/devices/0-3/authorized
151 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
152 # echo 2 > /sys/bus/thunderbolt/devices/0-3/authorized
181 Recent systems from 2018 and forward with Thunderbolt ports may natively
182 support IOMMU. This means that Thunderbolt security is handled by an IOMMU
187 ``/sys/bus/thunderbolt/devices/domainX/iommu_dma_protection`` attribute.
197 …ACTION=="add", SUBSYSTEM=="thunderbolt", ATTRS{iommu_dma_protection}=="1", ATTR{authorized}=="0", …
199 Upgrading NVM on Thunderbolt device, host or retimer
209 `Thunderbolt Updates <https://thunderbolttechnology.net/updates>`_
219 Thunderbolt device so that the host controller appears. It does not
225 Thunderbolt device.
229 Canyon) Thunderbolt controller NVM is upgraded::
231 # dd if=KYK_TBT_FW_0018.bin of=/sys/bus/thunderbolt/devices/0-0/nvm_non_active0/nvmem
236 # echo 1 > /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
246 # cat /sys/bus/thunderbolt/devices/0-0/nvm_authenticate
248 # cat /sys/bus/thunderbolt/devices/0-0/nvm_version
267 # echo 1 > /sys/bus/thunderbolt/devices/0-0/usb4_port1/offline
273 # echo 1 > /sys/bus/thunderbolt/devices/0-0/usb4_port1/rescan
281 # echo 1 > /sys/bus/thunderbolt/devices/0-0/usb4_port1/rescan
286 # echo 0 > /sys/bus/thunderbolt/devices/0-0/usb4_port1/offline
299 Networking over Thunderbolt cable
301 Thunderbolt technology allows software communication between two hosts
302 connected by a Thunderbolt cable.
304 It is possible to tunnel any kind of traffic over a Thunderbolt link but
308 do is to connect a Thunderbolt cable between the two hosts; the
309 ``thunderbolt-net`` driver is loaded automatically. If the other host is
310 also Linux you should load ``thunderbolt-net`` manually on one host (it
313 # modprobe thunderbolt-net
318 The driver will create one virtual ethernet interface per Thunderbolt
326 Thunderbolt controller to an "On" state even if nothing is connected.
330 For example the intel-wmi-thunderbolt driver exposes this attribute in: