drm: Fix typo in comments (0ae865ef) · Commits · EulixOS / Software / Kernel

drivers/gpu/drm/drm_aperture.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -78,7 +78,7 @@
		*
		* Drivers that are susceptible to being removed by other drivers, such as
		* generic EFI or VESA drivers, have to register themselves as owners of their
		* given framebuffer memory. Ownership of the framebuffer memory is achived
		* given framebuffer memory. Ownership of the framebuffer memory is achieved
		* by calling devm_aperture_acquire_from_firmware(). On success, the driver
		* is the owner of the framebuffer range. The function fails if the
		* framebuffer is already by another driver. See below for an example.

drivers/gpu/drm/drm_atomic.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -723,7 +723,7 @@ static void drm_atomic_plane_print_state(struct drm_printer *p,
		* clocks, scaler units, bandwidth and fifo limits shared among a group of
		* planes or CRTCs, and so on) it makes sense to model these as independent
		* objects. Drivers then need to do similar state tracking and commit ordering for
		* such private (since not exposed to userpace) objects as the atomic core and
		* such private (since not exposed to userspace) objects as the atomic core and
		* helpers already provide for connectors, planes and CRTCs.
		*
		* To make this easier on drivers the atomic core provides some support to track

drivers/gpu/drm/drm_atomic_helper.c

+5 −5

Original line number	Diff line number	Diff line
		@@ -634,7 +634,7 @@ drm_atomic_helper_check_modeset(struct drm_device *dev,
		* connectors and a NULL mode.
		*
		* The other way around is true as well. enable != 0
		* iff connectors are attached and a mode is set.
		* implies that connectors are attached and a mode is set.
		*/
		new_crtc_state->mode_changed = true;
		new_crtc_state->connectors_changed = true;
		@@ -1686,7 +1686,7 @@ static void commit_work(struct work_struct *work)
		}

		/**
		* drm_atomic_helper_async_check - check if state can be commited asynchronously
		* drm_atomic_helper_async_check - check if state can be committed asynchronously
		* @dev: DRM device
		* @state: the driver state object
		*
		@@ -1695,7 +1695,7 @@ static void commit_work(struct work_struct *work)
		* but just do in-place changes on the current state.
		*
		* It will return 0 if the commit can happen in an asynchronous fashion or error
		* if not. Note that error just mean it can't be commited asynchronously, if it
		* if not. Note that error just mean it can't be committed asynchronously, if it
		* fails the commit should be treated like a normal synchronous commit.
		*/
		int drm_atomic_helper_async_check(struct drm_device *dev,
		@@ -2583,7 +2583,7 @@ EXPORT_SYMBOL(drm_atomic_helper_commit_planes);
		*
		* This function can only be savely used when planes are not allowed to move
		* between different CRTCs because this function doesn't handle inter-CRTC
		* depencies. Callers need to ensure that either no such depencies exist,
		* dependencies. Callers need to ensure that either no such dependencies exist,
		* resolve them through ordering of commit calls or through some other means.
		*/
		void
		@@ -2720,7 +2720,7 @@ EXPORT_SYMBOL(drm_atomic_helper_cleanup_planes);
		/**
		* drm_atomic_helper_swap_state - store atomic state into current sw state
		* @state: atomic state
		* @stall: stall for preceeding commits
		* @stall: stall for preceding commits
		*
		* This function stores the atomic state into the current state pointers in all
		* driver objects. It should be called after all failing steps have been done

drivers/gpu/drm/drm_atomic_uapi.c

+3 −3

Original line number	Diff line number	Diff line
		@@ -48,7 +48,7 @@
		* in all its forms: The monster ATOMIC IOCTL itself, code for GET_PROPERTY and
		* SET_PROPERTY IOCTLs. Plus interface functions for compatibility helpers and
		* drivers which have special needs to construct their own atomic updates, e.g.
		* for load detect or similiar.
		* for load detect or similar.
		*/

		/**
		@@ -753,7 +753,7 @@ static int drm_atomic_connector_set_property(struct drm_connector *connector,
		* restore the state it wants on VT switch. So if the userspace
		* tries to change the link_status from GOOD to BAD, driver
		* silently rejects it and returns a 0. This prevents userspace
		* from accidently breaking the display when it restores the
		* from accidentally breaking the display when it restores the
		* state.
		*/
		if (state->link_status != DRM_LINK_STATUS_GOOD)
		@@ -1064,7 +1064,7 @@ int drm_atomic_set_property(struct drm_atomic_state *state,
		* DOC: explicit fencing properties
		*
		* Explicit fencing allows userspace to control the buffer synchronization
		* between devices. A Fence or a group of fences are transfered to/from
		* between devices. A Fence or a group of fences are transferred to/from
		* userspace using Sync File fds and there are two DRM properties for that.
		* IN_FENCE_FD on each DRM Plane to send fences to the kernel and
		* OUT_FENCE_PTR on each DRM CRTC to receive fences from the kernel.

drivers/gpu/drm/drm_auth.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -52,7 +52,7 @@
		*
		* In addition only one &drm_master can be the current master for a &drm_device.
		* It can be switched through the DROP_MASTER and SET_MASTER IOCTL, or
		* implicitly through closing/openeing the primary device node. See also
		* implicitly through closing/opening the primary device node. See also
		* drm_is_current_master().
		*
		* Clients can authenticate against the current master (if it matches their own)