Lines Matching full:topology
57 * protocol. The helpers contain a topology manager and bandwidth manager.
1351 * Topology refcount overview
1356 * two different kinds of refcounts: topology refcounts, and malloc refcounts.
1358 * Topology refcounts are not exposed to drivers, and are handled internally
1360 * in-memory topology state from being changed in the middle of critical
1363 * of the topology until its topology refcount reaches zero. Additionally,
1371 * drm_dp_mst_branch allocated even after all of its topology references have
1373 * branch's last known state before it was disconnected from the topology.
1385 * Refcount relationships in a topology
1388 * Let's take a look at why the relationship between topology and malloc
1391 * .. kernel-figure:: dp-mst/topology-figure-1.dot
1393 * An example of topology and malloc refs in a DP MST topology with two
1394 * active payloads. Topology refcount increments are indicated by solid
1400 * As you can see in the above figure, every branch increments the topology
1407 * topology would start to look like the figure below.
1409 * .. kernel-figure:: dp-mst/topology-figure-2.dot
1414 * Whenever a port or branch device's topology refcount reaches zero, it will
1415 * decrement the topology refcounts of all its children, the malloc refcount
1417 * #4, this means they both have been disconnected from the topology and freed
1419 * #3, port #3 is removed from the topology but its &struct drm_dp_mst_port
1427 * connected to the topology. In this case, we would travel up the topology as
1430 * .. kernel-figure:: dp-mst/topology-figure-3.dot
1617 drm_printf(&p, "%s (%p) topology count reached 0, dumping history:\n", in __dump_topology_ref_history()
1727 * drm_dp_mst_topology_try_get_mstb() - Increment the topology refcount of a
1729 * @mstb: &struct drm_dp_mst_branch to increment the topology refcount of
1731 * Attempts to grab a topology reference to @mstb, if it hasn't yet been
1732 * removed from the topology (e.g. &drm_dp_mst_branch.topology_kref has
1733 * reached 0). Holding a topology reference implies that a malloc reference
1734 * will be held to @mstb as long as the user holds the topology reference.
1737 * reference to @mstb. If you already have a topology reference to @mstb, you
1745 * * 1: A topology reference was grabbed successfully
1746 * * 0: @port is no longer in the topology, no reference was grabbed
1766 * drm_dp_mst_topology_get_mstb() - Increment the topology refcount of a
1768 * @mstb: The &struct drm_dp_mst_branch to increment the topology refcount of
1772 * you are already guaranteed to have at least one active topology reference
1792 * drm_dp_mst_topology_put_mstb() - release a topology reference to a branch
1794 * @mstb: The &struct drm_dp_mst_branch to release the topology reference from
1796 * Releases a topology reference from @mstb by decrementing
1842 * drm_dp_mst_topology_try_get_port() - Increment the topology refcount of a
1844 * @port: &struct drm_dp_mst_port to increment the topology refcount of
1846 * Attempts to grab a topology reference to @port, if it hasn't yet been
1847 * removed from the topology (e.g. &drm_dp_mst_port.topology_kref has reached
1848 * 0). Holding a topology reference implies that a malloc reference will be
1849 * held to @port as long as the user holds the topology reference.
1852 * reference to @port. If you already have a topology reference to @port, you
1860 * * 1: A topology reference was grabbed successfully
1861 * * 0: @port is no longer in the topology, no reference was grabbed
1880 * drm_dp_mst_topology_get_port() - Increment the topology refcount of a port
1881 * @port: The &struct drm_dp_mst_port to increment the topology refcount of
1885 * you are already guaranteed to have at least one active topology reference
1905 * drm_dp_mst_topology_put_port() - release a topology reference to a port
1906 * @port: The &struct drm_dp_mst_port to release the topology reference from
1908 * Releases a topology reference from @port by decrementing
2293 * Drop a topology reference, and unlink the port from the in-memory topology
2966 * topology, but were not seen in this link address. Usually this in drm_dp_send_link_address()
2967 * means that they were removed while the topology was out of sync, in drm_dp_send_link_address()
3076 * Searches upwards in the topology starting from mstb to try to find the
3078 * topology. This can be used in order to perform operations like releasing
3154 * mstb could also be removed from the topology. In the future, this in drm_dp_payload_send_msg()
3157 * timeout if the topology is still connected to the system. in drm_dp_payload_send_msg()
3334 "VCPI %d for port %p not in topology, not creating a payload to remote\n", in drm_dp_add_payload_part1()
3379 drm_dbg_kms(mgr->dev, "Payload for VCPI %d not in topology, not sending remove\n", in drm_dp_remove_payload_part1()
3637 * drm_dp_mst_topology_mgr_set_mst() - Set the MST state for a topology manager
3727 * drm_dp_mst_topology_queue_probe - Queue a topology probe
3730 * Queue a work to probe the MST topology. Driver's should call this only to
3731 * sync the topology's HW->SW state after the MST link's parameters have
3780 * @sync: whether or not to perform topology reprobing synchronously
3794 * Returns: -1 if the MST topology was removed while we were suspended, 0
3838 * For the final step of resuming the topology, we need to bring the in drm_dp_mst_topology_mgr_resume()
3839 * state of our in-memory topology back into sync with reality. So, in drm_dp_mst_topology_mgr_resume()
3847 "Waiting for link probe work to finish re-syncing topology...\n"); in drm_dp_mst_topology_mgr_resume()
4117 drm_dbg_kms(mgr->dev, "Got CSN before finish topology probing. Skip it."); in drm_dp_mst_handle_up_req()
4150 * topology manager will process the sideband messages received
4339 * @mgr: MST topology manager for the port
4347 * atomic state is added whenever the state of payloads in the topology changes.
4430 * @mgr: MST topology manager for the port
4439 * topology.
4515 * currently assigned to an MST topology. Drivers must call this hook from their
4559 * touched CRTCs that were/are on an MST topology to be programmed to hardware and flipped to before
4560 * returning. This is to prevent multiple non-blocking commits affecting an MST topology from racing
4562 * the modeset objects in these commits share are an MST topology.
4607 * @mgr: The MST topology manager for the &drm_connector
4610 * serialize non-blocking commits happening on the real DP connector of an MST topology switching
4612 * MST topology will never share the same &drm_encoder.
4615 * state to determine if it is about to have a modeset - and then pulling in the MST topology state
4902 * drm_dp_mst_dump_topology(): dump topology to seq file.
4904 * @mgr: manager to dump current topology for.
4906 * helper to dump MST topology to a seq file for debugfs.
5231 * @mgr: MST topology manager
5237 * @mgr's topology.
5407 * @mgr: MST topology manager
5409 * Whenever there is a change in mst topology
5412 * CRTCs in that topology
5521 * drm_dp_mst_atomic_check_mgr - Check the atomic state of an MST topology manager
5527 * Checks the given MST manager's topology state for an atomic update to ensure
5583 * drm_dp_mst_atomic_check - Check that the new state of an MST topology in an
5587 * Checks the given topology state for an atomic update to ensure that it's
5629 * drm_atomic_get_mst_topology_state: get MST topology state
5631 * @mgr: MST topology manager, also the private object in this case
5635 * topology object.
5638 * The MST topology state or error pointer.
5648 * drm_atomic_get_old_mst_topology_state: get old MST topology state in atomic state, if any
5650 * @mgr: MST topology manager, also the private object in this case
5654 * topology object.
5657 * The old MST topology state, or NULL if there's no topology state for this MST mgr
5672 * drm_atomic_get_new_mst_topology_state: get new MST topology state in atomic state, if any
5674 * @mgr: MST topology manager, also the private object in this case
5678 * topology object.
5681 * The new MST topology state, or NULL if there's no topology state for this MST mgr
5696 * drm_dp_mst_topology_mgr_init - initialise a topology manager
5729 * requeuing will be also flushed when deiniting the topology manager. in drm_dp_mst_topology_mgr_init()
5765 * drm_dp_mst_topology_mgr_destroy() - destroy topology manager.
6001 * A single physical MST hub object can be represented in the topology