Lines Matching full:topology
55 * protocol. The helpers contain a topology manager and bandwidth manager.
1387 * Topology refcount overview
1392 * two different kinds of refcounts: topology refcounts, and malloc refcounts.
1394 * Topology refcounts are not exposed to drivers, and are handled internally
1396 * in-memory topology state from being changed in the middle of critical
1399 * of the topology until its topology refcount reaches zero. Additionally,
1407 * drm_dp_mst_branch allocated even after all of its topology references have
1409 * branch's last known state before it was disconnected from the topology.
1421 * Refcount relationships in a topology
1424 * Let's take a look at why the relationship between topology and malloc
1427 * .. kernel-figure:: dp-mst/topology-figure-1.dot
1429 * An example of topology and malloc refs in a DP MST topology with two
1430 * active payloads. Topology refcount increments are indicated by solid
1436 * As you can see in the above figure, every branch increments the topology
1443 * topology would start to look like the figure below.
1445 * .. kernel-figure:: dp-mst/topology-figure-2.dot
1450 * Whenever a port or branch device's topology refcount reaches zero, it will
1451 * decrement the topology refcounts of all its children, the malloc refcount
1453 * #4, this means they both have been disconnected from the topology and freed
1455 * #3, port #3 is removed from the topology but its &struct drm_dp_mst_port
1463 * connected to the topology. In this case, we would travel up the topology as
1466 * .. kernel-figure:: dp-mst/topology-figure-3.dot
1652 drm_printf(&p, "%s (%p) topology count reached 0, dumping history:\n", in __dump_topology_ref_history()
1751 * drm_dp_mst_topology_try_get_mstb() - Increment the topology refcount of a
1753 * @mstb: &struct drm_dp_mst_branch to increment the topology refcount of
1755 * Attempts to grab a topology reference to @mstb, if it hasn't yet been
1756 * removed from the topology (e.g. &drm_dp_mst_branch.topology_kref has
1757 * reached 0). Holding a topology reference implies that a malloc reference
1758 * will be held to @mstb as long as the user holds the topology reference.
1761 * reference to @mstb. If you already have a topology reference to @mstb, you
1769 * * 1: A topology reference was grabbed successfully
1770 * * 0: @port is no longer in the topology, no reference was grabbed
1791 * drm_dp_mst_topology_get_mstb() - Increment the topology refcount of a
1793 * @mstb: The &struct drm_dp_mst_branch to increment the topology refcount of
1797 * you are already guaranteed to have at least one active topology reference
1817 * drm_dp_mst_topology_put_mstb() - release a topology reference to a branch
1819 * @mstb: The &struct drm_dp_mst_branch to release the topology reference from
1821 * Releases a topology reference from @mstb by decrementing
1868 * drm_dp_mst_topology_try_get_port() - Increment the topology refcount of a
1870 * @port: &struct drm_dp_mst_port to increment the topology refcount of
1872 * Attempts to grab a topology reference to @port, if it hasn't yet been
1873 * removed from the topology (e.g. &drm_dp_mst_port.topology_kref has reached
1874 * 0). Holding a topology reference implies that a malloc reference will be
1875 * held to @port as long as the user holds the topology reference.
1878 * reference to @port. If you already have a topology reference to @port, you
1886 * * 1: A topology reference was grabbed successfully
1887 * * 0: @port is no longer in the topology, no reference was grabbed
1907 * drm_dp_mst_topology_get_port() - Increment the topology refcount of a port
1908 * @port: The &struct drm_dp_mst_port to increment the topology refcount of
1912 * you are already guaranteed to have at least one active topology reference
1932 * drm_dp_mst_topology_put_port() - release a topology reference to a port
1933 * @port: The &struct drm_dp_mst_port to release the topology reference from
1935 * Releases a topology reference from @port by decrementing
2319 * Drop a topology reference, and unlink the port from the in-memory topology
3017 * topology, but were not seen in this link address. Usually this in drm_dp_send_link_address()
3018 * means that they were removed while the topology was out of sync, in drm_dp_send_link_address()
3127 * Searches upwards in the topology starting from mstb to try to find the
3129 * topology. This can be used in order to perform operations like releasing
3205 * mstb could also be removed from the topology. In the future, this in drm_dp_payload_send_msg()
3208 * timeout if the topology is still connected to the system. in drm_dp_payload_send_msg()
3664 * drm_dp_mst_topology_mgr_set_mst() - Set the MST state for a topology manager
3795 * @sync: whether or not to perform topology reprobing synchronously
3809 * Returns: -1 if the MST topology was removed while we were suspended, 0
3852 * For the final step of resuming the topology, we need to bring the in drm_dp_mst_topology_mgr_resume()
3853 * state of our in-memory topology back into sync with reality. So, in drm_dp_mst_topology_mgr_resume()
3860 DRM_DEBUG_KMS("Waiting for link probe work to finish re-syncing topology...\n"); in drm_dp_mst_topology_mgr_resume()
4152 * topology manager will process the sideband messages received as a result
4316 * @mgr: MST topology manager for the port
4415 * @mgr: MST topology manager for the port
4759 * drm_dp_mst_dump_topology(): dump topology to seq file.
4761 * @mgr: manager to dump current topology for.
4763 * helper to dump MST topology to a seq file for debugfs.
5179 * @mgr: MST topology manager
5181 * Whenever there is a change in mst topology
5184 * CRTCs in that topology
5299 * drm_dp_mst_atomic_check - Check that the new state of an MST topology in an
5303 * Checks the given topology state for an atomic update to ensure that it's
5354 * drm_atomic_get_mst_topology_state: get MST topology state
5357 * @mgr: MST topology manager, also the private object in this case
5361 * topology object. Also, drm_atomic_get_private_obj_state() expects the caller
5366 * The MST topology state or error pointer.
5376 * drm_dp_mst_topology_mgr_init - initialise a topology manager
5409 * requeuing will be also flushed when deiniting the topology manager. in drm_dp_mst_topology_mgr_init()
5452 * drm_dp_mst_topology_mgr_destroy() - destroy topology manager.
5696 * A single physical MST hub object can be represented in the topology