57
57
* - Driver appears to be working for Brutus 320x200x8bpp mode. Other
58
58
* resolutions are working, but only the 8bpp mode is supported.
59
59
* Changes need to be made to the palette encode and decode routines
60
- * to support 4 and 16 bpp modes.
60
+ * to support 4 and 16 bpp modes.
61
61
* Driver is not designed to be a module. The FrameBuffer is statically
62
- * allocated since dynamic allocation of a 300k buffer cannot be
63
- * guaranteed.
62
+ * allocated since dynamic allocation of a 300k buffer cannot be
63
+ * guaranteed.
64
64
*
65
65
* 1999/06/17:
66
66
* - FrameBuffer memory is now allocated at run-time when the
67
- * driver is initialized.
67
+ * driver is initialized.
68
68
*
69
69
* 2000/04/10: Nicolas Pitre <nico@fluxnic.net>
70
70
* - Big cleanup for dynamic selection of machine type at run time.
74
74
*
75
75
* 2000/08/07: Tak-Shing Chan <tchan.rd@idthk.com>
76
76
* Jeff Sutherland <jsutherland@accelent.com>
77
- * - Resolved an issue caused by a change made to the Assabet's PLD
78
- * earlier this year which broke the framebuffer driver for newer
77
+ * - Resolved an issue caused by a change made to the Assabet's PLD
78
+ * earlier this year which broke the framebuffer driver for newer
79
79
* Phase 4 Assabets. Some other parameters were changed to optimize
80
80
* for the Sharp display.
81
81
*
102
102
* 2000/11/23: Eric Peng <ericpeng@coventive.com>
103
103
* - Freebird add
104
104
*
105
- * 2001/02/07: Jamey Hicks <jamey.hicks@compaq.com>
105
+ * 2001/02/07: Jamey Hicks <jamey.hicks@compaq.com>
106
106
* Cliff Brake <cbrake@accelent.com>
107
107
* - Added PM callback
108
108
*
@@ -500,7 +500,7 @@ sa1100fb_set_cmap(struct fb_cmap *cmap, int kspc, int con,
500
500
* the shortest recovery time
501
501
* Suspend
502
502
* This refers to a level of power management in which substantial power
503
- * reduction is achieved by the display. The display can have a longer
503
+ * reduction is achieved by the display. The display can have a longer
504
504
* recovery time from this state than from the Stand-by state
505
505
* Off
506
506
* This indicates that the display is consuming the lowest level of power
@@ -522,9 +522,9 @@ sa1100fb_set_cmap(struct fb_cmap *cmap, int kspc, int con,
522
522
*/
523
523
/*
524
524
* sa1100fb_blank():
525
- * Blank the display by setting all palette values to zero. Note, the
525
+ * Blank the display by setting all palette values to zero. Note, the
526
526
* 12 and 16 bpp modes don't really use the palette, so this will not
527
- * blank the display in all modes.
527
+ * blank the display in all modes.
528
528
*/
529
529
static int sa1100fb_blank (int blank , struct fb_info * info )
530
530
{
@@ -603,8 +603,8 @@ static inline unsigned int get_pcd(struct sa1100fb_info *fbi,
603
603
604
604
/*
605
605
* sa1100fb_activate_var():
606
- * Configures LCD Controller based on entries in var parameter. Settings are
607
- * only written to the controller if changes were made.
606
+ * Configures LCD Controller based on entries in var parameter. Settings are
607
+ * only written to the controller if changes were made.
608
608
*/
609
609
static int sa1100fb_activate_var (struct fb_var_screeninfo * var , struct sa1100fb_info * fbi )
610
610
{
@@ -747,7 +747,7 @@ static void sa1100fb_setup_gpio(struct sa1100fb_info *fbi)
747
747
*
748
748
* SA1110 spec update nr. 25 says we can and should
749
749
* clear LDD15 to 12 for 4 or 8bpp modes with active
750
- * panels.
750
+ * panels.
751
751
*/
752
752
if ((fbi -> reg_lccr0 & LCCR0_CMS ) == LCCR0_Color &&
753
753
(fbi -> reg_lccr0 & (LCCR0_Dual |LCCR0_Act )) != 0 ) {
@@ -1020,9 +1020,9 @@ static int sa1100fb_resume(struct platform_device *dev)
1020
1020
1021
1021
/*
1022
1022
* sa1100fb_map_video_memory():
1023
- * Allocates the DRAM memory for the frame buffer. This buffer is
1024
- * remapped into a non-cached, non-buffered, memory region to
1025
- * allow palette and pixel writes to occur without flushing the
1023
+ * Allocates the DRAM memory for the frame buffer. This buffer is
1024
+ * remapped into a non-cached, non-buffered, memory region to
1025
+ * allow palette and pixel writes to occur without flushing the
1026
1026
* cache. Once this area is remapped, all virtual memory
1027
1027
* access to the video memory should occur at the new region.
1028
1028
*/
0 commit comments