delta/linux.git/include/linux/thunderbolt.h, branch proc-cmdline

thunderbolt: Introduce USB only (SL4) security level

2018-03-09T09:54:11+00:00

This new security level works so that it creates one PCIe tunnel to the
connected Thunderbolt dock, removing PCIe links downstream of the dock.
This leaves only the internal USB controller visible.

Display Port tunnels are created normally.

While there make sure security sysfs attribute returns "unknown" for any
future security level.

Signed-off-by: Mika Westerberg 
Reviewed-by: Andy Shevchenko

thunderbolt: Add support for preboot ACL

2018-03-09T09:54:11+00:00

Preboot ACL is a mechanism that allows connecting Thunderbolt devices
boot time in more secure way than the legacy Thunderbolt boot support.
As with the legacy boot option, this also needs to be enabled from the
BIOS before booting is allowed. Difference to the legacy mode is that
the userspace software explicitly adds device UUIDs by sending a special
message to the ICM firmware. Only the devices listed in the boot ACL are
connected automatically during the boot. This works in both "user" and
"secure" security levels.

We implement this in Linux by exposing a new sysfs attribute (boot_acl)
below each Thunderbolt domain. The userspace software can then update
the full list as needed.

Signed-off-by: Mika Westerberg 
Reviewed-by: Andy Shevchenko

thunderbolt: Add tb_xdomain_find_by_route()

2018-03-09T09:54:10+00:00

This is needed by the new ICM interface to find xdomains by route string
instead of link and depth.

While there update existing tb_xdomain_find_* functions to use
tb_xdomain_get() instead of open-coding the same.

Signed-off-by: Radion Mirchevsky 
Signed-off-by: Mika Westerberg 
Reviewed-by: Andy Shevchenko

thunderbolt: Add function to retrieve DMA device for the ring

2017-10-02T18:24:41+00:00

This is needed when Thunderbolt service drivers need to DMA map memory
before it is passed down to the ring.

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Add polling mode for rings

2017-10-02T18:24:41+00:00

In order to support things like networking over Thunderbolt cable, there
needs to be a way to switch the ring to a mode where it can be polled
with the interrupt masked. We implement such mode so that the caller can
allocate a ring by passing pointer to a function that is then called
when an interrupt is triggered. Completed frames can be fetched using
tb_ring_poll() and the interrupt can be re-enabled when the caller is
finished with polling by using tb_ring_poll_complete().

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Use spinlock in NHI serialization

2017-10-02T18:24:41+00:00

This is needed because ring polling functionality can be called from
atomic contexts when networking and other high-speed traffic is
transferred over a Thunderbolt cable.

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Use spinlock in ring serialization

2017-10-02T18:24:41+00:00

This makes it possible to enqueue frames also from atomic context which
is needed for example, when networking packets are sent over a
Thunderbolt cable.

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Move ring descriptor flags to thunderbolt.h

2017-10-02T18:24:41+00:00

A Thunderbolt service driver might need to check if there was an error
with the descriptor when in frame mode. We also add two Rx specific
error flags RING_DESC_CRC_ERROR and RING_DESC_BUFFER_OVERRUN.

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Export ring handling functions to modules

2017-10-02T18:24:41+00:00

These are used by Thunderbolt services to send and receive frames over
the high-speed DMA rings.

We also put the functions to tb_ namespace to make sure we do not
collide with others and add missing kernel-doc comments for the exported
functions.

Signed-off-by: Mika Westerberg 
Reviewed-by: Michael Jamet 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller

thunderbolt: Add support for XDomain discovery protocol

2017-10-02T18:24:41+00:00

When two hosts are connected over a Thunderbolt cable, there is a
protocol they can use to communicate capabilities supported by the host.
The discovery protocol uses automatically configured control channel
(ring 0) and is build on top of request/response transactions using
special XDomain primitives provided by the Thunderbolt base protocol.

The capabilities consists of a root directory block of basic properties
used for identification of the host, and then there can be zero or more
directories each describing a Thunderbolt service and its capabilities.

Once both sides have discovered what is supported the two hosts can
setup high-speed DMA paths and transfer data to the other side using
whatever protocol was agreed based on the properties. The software
protocol used to communicate which DMA paths to enable is service
specific.

This patch adds support for the XDomain discovery protocol to the
Thunderbolt bus. We model each remote host connection as a Linux XDomain
device. For each Thunderbolt service found supported on the XDomain
device, we create Linux Thunderbolt service device which Thunderbolt
service drivers can then bind to based on the protocol identification
information retrieved from the property directory describing the
service.

This code is based on the work done by Amir Levy and Michael Jamet.

Signed-off-by: Michael Jamet 
Signed-off-by: Mika Westerberg 
Reviewed-by: Yehezkel Bernat 
Reviewed-by: Andy Shevchenko 
Signed-off-by: David S. Miller