Display Driver Model - Revision history

Tectu: /* Board Files */

2016-06-23T14:42:56Z

‎Board Files

Tectu: /* Board Files */

2016-06-23T14:42:29Z

‎Board Files

Tectu: /* Board Files */

2016-06-23T14:41:03Z

‎Board Files

Tectu: /* Board Files */

2016-06-23T14:40:55Z

‎Board Files

Tectu: /* Board Files */

2016-06-23T14:39:18Z

‎Board Files

Tectu: /* Point and Block Model */

2016-06-23T14:38:20Z

‎Point and Block Model

Tectu: /* Window Model */

2016-06-23T14:37:54Z

‎Window Model

Tectu: /* Framebuffer Model */

2016-06-23T14:37:20Z

‎Framebuffer Model

Tectu: Whitespaces

2014-08-18T21:27:15Z

Whitespaces

Inmarket: /* Board Files */

2014-08-16T03:30:38Z

‎Board Files

@@ Line 72: / Line 72: @@
 == Board Files ==
-[[Board_File|Board files]] are used as the interface between the display driver (software) and the actual display controller (hardware). The board file implements the functions that are used to generate the electrical/physical signals using the microcontroller's peripherals. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
+[[Board_File|Board files]] are used as the interface between the display driver (software) and the actual display controller (hardware). The board file implements the functions that are used to generate the electrical/physical signals using the microcontroller's peripherals. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''). The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
 The [[Board_File|board file]] API for a '''Window Model''' or '''Point and Block Model''' GDISP driver looks like the following (although it may vary slightly from driver to driver):
 <syntaxhighlight lang=c>

@@ Line 72: / Line 72: @@
 == Board Files ==
-[[Board_File|Board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
+[[Board_File|Board files]] are used as the interface between the display driver (software) and the actual display controller (hardware). The board file implements the functions that are used to generate the electrical/physical signals using the microcontroller's peripherals. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
 The [[Board_File|board file]] API for a '''Window Model''' or '''Point and Block Model''' GDISP driver looks like the following (although it may vary slightly from driver to driver):
 <syntaxhighlight lang=c>

@@ Line 72: / Line 72: @@
 == Board Files ==
-[[Board_File|board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
+[[Board_File|Board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
 The [[Board_File|board file]] API for a '''Window Model''' or '''Point and Block Model''' GDISP driver looks like the following (although it may vary slightly from driver to driver):
 <syntaxhighlight lang=c>

@@ Line 72: / Line 72: @@
 == Board Files ==
-[[Board_File|board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template in the drivers directory.
+[[Board_File|board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template which can be found in the driver directory (''/drivers/gdisp/*''. The user of the driver has to copy the board file template from the driver directory to his project and implement the empty functions accordingly.
 The [[Board_File|board file]] API for a '''Window Model''' or '''Point and Block Model''' GDISP driver looks like the following (although it may vary slightly from driver to driver):
 <syntaxhighlight lang=c>

@@ Line 72: / Line 72: @@
 == Board Files ==
-Board files are used to connect the driver to physical hardware connection. The [[Board_File|board file]] API for a '''Window Model''' or '''Point and Block Model''' GDISP driver looks like the following (although it may vary slightly from driver to driver):
+[[Board_File|board files]] are used to connect the driver to physical hardware connection. Each driver provides its own board file template in the drivers directory.
 <syntaxhighlight lang=c>
 static void     init_board(GDisplay *g);

@@ Line 59: / Line 59: @@
 Required Routines:
-*gdisp_lld_init() - Initialise the controller and display
+*<code>gdisp_lld_init()</code> - Initialise the controller and display
-*gdisp_lld_draw_pixel() - Set a single pixel
+*<code>gdisp_lld_draw_pixel()</code> - Set a single pixel
 Optional Routines:
-*gdisp_lld_fill_area() - Fill a block with a color
+*<code>gdisp_lld_fill_area()</code> - Fill a block with a color
-*gdisp_lld_blit_area() - Fill a block from an array of pixels
+*<code>gdisp_lld_blit_area()</code> - Fill a block from an array of pixels
-*gdisp_lld_vertical_scroll() - Scroll up or down a windowed area of the display
+*<code>gdisp_lld_vertical_scroll()</code> - Scroll up or down a windowed area of the display
-*gdisp_lld_get_pixel_color() - Get the color of a single pixel
+*<code>gdisp_lld_get_pixel_color()</code> - Get the color of a single pixel
-*gdisp_lld_set_clip() - Set a hardware clipping region. All writes are clipped to this area.
+*<code>gdisp_lld_set_clip()</code> - Set a hardware clipping region. All writes are clipped to this area.
-*gdisp_lld_control() - Handle backlight, contrast, screen orientation and any driver specific control commands
+*<code>gdisp_lld_control()</code> - Handle backlight, contrast, screen orientation and any driver specific control commands
-*gdisp_lld_query() - Query some driver specific value
+*<code>gdisp_lld_query()</code> - Query some driver specific value
 == Board Files ==

@@ Line 38: / Line 38: @@
 Required Routines:
-*gdisp_lld_init() - Initialise the controller and display
+*<code>gdisp_lld_init()</code> - Initialise the controller and display
-*gdisp_lld_write_start() - Start a windowed write operation
+*<code>gdisp_lld_write_start()</code> - Start a windowed write operation
-*gdisp_lld_write_color() - Send one pixel to the current window at the current position
+*<code>gdisp_lld_write_color()</code> - Send one pixel to the current window at the current position
-*gdisp_lld_write_stop() - Stop a windowed write operation
+*<code>gdisp_lld_write_stop()</code> - Stop a windowed write operation
 Optional Routines:
-*gdisp_lld_write_pos() - Set the current position within the write window (increases drawing efficiency)
+*<code>gdisp_lld_write_pos()</code> - Set the current position within the write window (increases drawing efficiency)
-*gdisp_lld_read_start() - Start a windowed read operation
+*<code>gdisp_lld_read_start()</code> - Start a windowed read operation
-*gdisp_lld_read_color() - Read one pixel from the current window at the current position
+*<code>gdisp_lld_read_color()</code> - Read one pixel from the current window at the current position
-*gdisp_lld_read_stop() - Stop a windowed read operation
+*<code>gdisp_lld_read_stop()</code> - Stop a windowed read operation
-*gdisp_lld_set_clip() - Set a hardware clipping region. All writes are clipped to this area (regardless of the current window)
+*<code>gdisp_lld_set_clip()</code> - Set a hardware clipping region. All writes are clipped to this area (regardless of the current window)
-*gdisp_lld_control() - Handle backlight, contrast, screen orientation and any driver specific control commands
+*<code>gdisp_lld_control()</code> - Handle backlight, contrast, screen orientation and any driver specific control commands
-*gdisp_lld_query() - Query some driver specific value
+*<code>gdisp_lld_query()</code> - Query some driver specific value
 *Any '''Point and Block Model''' routines as described below.

@@ Line 15: / Line 15: @@
 Required Routines:
-*board_init() - Initialise the framebuffer and return its address and the display properties
+*<code>board_init()</code> - Initialise the framebuffer and return its address and the display properties
 Optional Routines:
-*board_flush() - Flush (sync) the framebuffer to the display
+*<code>board_flush()</code> - Flush (sync) the framebuffer to the display
-*board_backlight() - Adjust the display backlight
+*<code>board_backlight()</code> - Adjust the display backlight
-*board_contrast() - Adjust the display contrast
+*<code>board_contrast()</code> - Adjust the display contrast
-*board_power() - Enter/Leave sleep modes
+*<code>board_power()</code> - Enter/Leave sleep modes
 == Window Model ==

← Older revision		Revision as of 03:30, 16 August 2014
Line 87:		Line 87:
	static uint16_t read_data(GDisplay *g);		static uint16_t read_data(GDisplay *g);
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	The <code>post_init_board()</code> routine is sometimes used to increase the bus speed after successful initialization of the controller by the driver.