Lines Matching full:topology
57 * protocol. The helpers contain a topology manager and bandwidth manager.
1350 * Topology refcount overview
1355 * two different kinds of refcounts: topology refcounts, and malloc refcounts.
1357 * Topology refcounts are not exposed to drivers, and are handled internally
1359 * in-memory topology state from being changed in the middle of critical
1362 * of the topology until its topology refcount reaches zero. Additionally,
1370 * drm_dp_mst_branch allocated even after all of its topology references have
1372 * branch's last known state before it was disconnected from the topology.
1384 * Refcount relationships in a topology
1387 * Let's take a look at why the relationship between topology and malloc
1390 * .. kernel-figure:: dp-mst/topology-figure-1.dot
1392 * An example of topology and malloc refs in a DP MST topology with two
1393 * active payloads. Topology refcount increments are indicated by solid
1399 * As you can see in the above figure, every branch increments the topology
1406 * topology would start to look like the figure below.
1408 * .. kernel-figure:: dp-mst/topology-figure-2.dot
1413 * Whenever a port or branch device's topology refcount reaches zero, it will
1414 * decrement the topology refcounts of all its children, the malloc refcount
1416 * #4, this means they both have been disconnected from the topology and freed
1418 * #3, port #3 is removed from the topology but its &struct drm_dp_mst_port
1426 * connected to the topology. In this case, we would travel up the topology as
1429 * .. kernel-figure:: dp-mst/topology-figure-3.dot
1615 drm_printf(&p, "%s (%p) topology count reached 0, dumping history:\n", in __dump_topology_ref_history()
1725 * drm_dp_mst_topology_try_get_mstb() - Increment the topology refcount of a
1727 * @mstb: &struct drm_dp_mst_branch to increment the topology refcount of
1729 * Attempts to grab a topology reference to @mstb, if it hasn't yet been
1730 * removed from the topology (e.g. &drm_dp_mst_branch.topology_kref has
1731 * reached 0). Holding a topology reference implies that a malloc reference
1732 * will be held to @mstb as long as the user holds the topology reference.
1735 * reference to @mstb. If you already have a topology reference to @mstb, you
1743 * * 1: A topology reference was grabbed successfully
1744 * * 0: @port is no longer in the topology, no reference was grabbed
1764 * drm_dp_mst_topology_get_mstb() - Increment the topology refcount of a
1766 * @mstb: The &struct drm_dp_mst_branch to increment the topology refcount of
1770 * you are already guaranteed to have at least one active topology reference
1790 * drm_dp_mst_topology_put_mstb() - release a topology reference to a branch
1792 * @mstb: The &struct drm_dp_mst_branch to release the topology reference from
1794 * Releases a topology reference from @mstb by decrementing
1840 * drm_dp_mst_topology_try_get_port() - Increment the topology refcount of a
1842 * @port: &struct drm_dp_mst_port to increment the topology refcount of
1844 * Attempts to grab a topology reference to @port, if it hasn't yet been
1845 * removed from the topology (e.g. &drm_dp_mst_port.topology_kref has reached
1846 * 0). Holding a topology reference implies that a malloc reference will be
1847 * held to @port as long as the user holds the topology reference.
1850 * reference to @port. If you already have a topology reference to @port, you
1858 * * 1: A topology reference was grabbed successfully
1859 * * 0: @port is no longer in the topology, no reference was grabbed
1878 * drm_dp_mst_topology_get_port() - Increment the topology refcount of a port
1879 * @port: The &struct drm_dp_mst_port to increment the topology refcount of
1883 * you are already guaranteed to have at least one active topology reference
1903 * drm_dp_mst_topology_put_port() - release a topology reference to a port
1904 * @port: The &struct drm_dp_mst_port to release the topology reference from
1906 * Releases a topology reference from @port by decrementing
2287 * Drop a topology reference, and unlink the port from the in-memory topology
2961 * topology, but were not seen in this link address. Usually this in drm_dp_send_link_address()
2962 * means that they were removed while the topology was out of sync, in drm_dp_send_link_address()
3071 * Searches upwards in the topology starting from mstb to try to find the
3073 * topology. This can be used in order to perform operations like releasing
3149 * mstb could also be removed from the topology. In the future, this in drm_dp_payload_send_msg()
3152 * timeout if the topology is still connected to the system. in drm_dp_payload_send_msg()
3329 "VCPI %d for port %p not in topology, not creating a payload to remote\n", in drm_dp_add_payload_part1()
3374 drm_dbg_kms(mgr->dev, "Payload for VCPI %d not in topology, not sending remove\n", in drm_dp_remove_payload_part1()
3628 * drm_dp_mst_topology_mgr_set_mst() - Set the MST state for a topology manager
3744 * @sync: whether or not to perform topology reprobing synchronously
3758 * Returns: -1 if the MST topology was removed while we were suspended, 0
3799 * For the final step of resuming the topology, we need to bring the in drm_dp_mst_topology_mgr_resume()
3800 * state of our in-memory topology back into sync with reality. So, in drm_dp_mst_topology_mgr_resume()
3808 "Waiting for link probe work to finish re-syncing topology...\n"); in drm_dp_mst_topology_mgr_resume()
4100 * topology manager will process the sideband messages received
4289 * @mgr: MST topology manager for the port
4297 * atomic state is added whenever the state of payloads in the topology changes.
4380 * @mgr: MST topology manager for the port
4389 * topology.
4465 * currently assigned to an MST topology. Drivers must call this hook from their
4509 * touched CRTCs that were/are on an MST topology to be programmed to hardware and flipped to before
4510 * returning. This is to prevent multiple non-blocking commits affecting an MST topology from racing
4512 * the modeset objects in these commits share are an MST topology.
4557 * @mgr: The MST topology manager for the &drm_connector
4560 * serialize non-blocking commits happening on the real DP connector of an MST topology switching
4562 * MST topology will never share the same &drm_encoder.
4565 * state to determine if it is about to have a modeset - and then pulling in the MST topology state
4852 * drm_dp_mst_dump_topology(): dump topology to seq file.
4854 * @mgr: manager to dump current topology for.
4856 * helper to dump MST topology to a seq file for debugfs.
5181 * @mgr: MST topology manager
5187 * @mgr's topology.
5357 * @mgr: MST topology manager
5359 * Whenever there is a change in mst topology
5362 * CRTCs in that topology
5471 * drm_dp_mst_atomic_check_mgr - Check the atomic state of an MST topology manager
5477 * Checks the given MST manager's topology state for an atomic update to ensure
5533 * drm_dp_mst_atomic_check - Check that the new state of an MST topology in an
5537 * Checks the given topology state for an atomic update to ensure that it's
5580 * drm_atomic_get_mst_topology_state: get MST topology state
5582 * @mgr: MST topology manager, also the private object in this case
5586 * topology object.
5590 * The MST topology state or error pointer.
5600 * drm_atomic_get_old_mst_topology_state: get old MST topology state in atomic state, if any
5602 * @mgr: MST topology manager, also the private object in this case
5606 * topology object.
5610 * The old MST topology state, or NULL if there's no topology state for this MST mgr
5625 * drm_atomic_get_new_mst_topology_state: get new MST topology state in atomic state, if any
5627 * @mgr: MST topology manager, also the private object in this case
5631 * topology object.
5635 * The new MST topology state, or NULL if there's no topology state for this MST mgr
5650 * drm_dp_mst_topology_mgr_init - initialise a topology manager
5683 * requeuing will be also flushed when deiniting the topology manager. in drm_dp_mst_topology_mgr_init()
5719 * drm_dp_mst_topology_mgr_destroy() - destroy topology manager.
5955 * A single physical MST hub object can be represented in the topology