DocBook/drm: Use an itemizedlist for what an encoder needs to provide

	  </para>

	  </para>

	</sect4>

	</sect4>

	<para>

	<para>

	  For each encoder, CRTC, and connector, several functions must

	  Each encoder object needs to provide:

	  be provided, depending on the object type.  Encoder objects

	  <itemizedlist>

	  need to provide a DPMS (basically on/off) function, mode fixup

	    <listitem>

	  (for converting requested modes into native hardware timings),

	      A DPMS (basically on/off) function.

	  and prepare, set and commit functions for use by the core DRM

	    </listitem>

	  helper functions.  Connector helpers need to provide mode fetch and

	    <listitem>

	  validity functions as well as an encoder matching function for

	      A mode-fixup function (for converting requested modes into

	  returning an ideal encoder for a given connector.  The core

	      native hardware timings).

	  connector functions include a DPMS callback, (deprecated)

	    </listitem>

	  save/restore routines, detection, mode probing, property handling,

	    <listitem>

	  and cleanup functions.

	      Functions (prepare, set, and commit) for use by the core DRM

	      helper functions.

	    </listitem>

	  </itemizedlist>

	  Connector helpers need to provide functions (mode-fetch, validity,

	  and encoder-matching) for returning an ideal encoder for a given

	  connector.  The core connector functions include a DPMS callback,

	  save/restore routines (deprecated), detection, mode probing,

	  property handling, and cleanup functions.

	</para>

	</para>

<!--!Edrivers/char/drm/drm_crtc.h-->

<!--!Edrivers/char/drm/drm_crtc.h-->

<!--!Edrivers/char/drm/drm_crtc.c-->

<!--!Edrivers/char/drm/drm_crtc.c-->