Lines Matching refs:private
686 * DOC: handling driver private state
694 * such private (since not exposed to userpace) objects as the atomic core and
698 * driver private state objects using struct &drm_private_obj, with the
701 * Similar to userspace-exposed objects, private state structures can be
709 * All private state structures contained in a &drm_atomic_state update can be
712 * Drivers are recommended to wrap these for each type of driver private state
716 * An earlier way to handle driver private state was by subclassing struct
724 * drm_atomic_private_obj_init - initialize private object
726 * @obj: private object
727 * @state: initial private object state
731 * Initialize the private object, which can be embedded into any
732 * driver private object that needs its own atomic state.
751 * drm_atomic_private_obj_fini - finalize private object
752 * @obj: private object
754 * Finalize the private object.
766 * drm_atomic_get_private_obj_state - get private object state
768 * @obj: private object to get the state for
770 * This function returns the private object state for the given private object,
771 * allocating the state if needed. It will also grab the relevant private
817 DRM_DEBUG_ATOMIC("Added new private object %p state %p to %p\n",
829 * This function returns the old private object state for the given private_obj,
851 * This function returns the new private object state for the given private_obj,
1641 struct drm_info_node *node = (struct drm_info_node *) m->private;