fbdev: sa1100fb: Remove trailing whitespaces
Fix coding style. No functional changes. Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> Signed-off-by: Helge Deller <deller@gmx.de>
This commit is contained in:
parent
a124ee3271
commit
6a7be52615
|
@ -57,14 +57,14 @@
|
|||
* - Driver appears to be working for Brutus 320x200x8bpp mode. Other
|
||||
* resolutions are working, but only the 8bpp mode is supported.
|
||||
* Changes need to be made to the palette encode and decode routines
|
||||
* to support 4 and 16 bpp modes.
|
||||
* to support 4 and 16 bpp modes.
|
||||
* Driver is not designed to be a module. The FrameBuffer is statically
|
||||
* allocated since dynamic allocation of a 300k buffer cannot be
|
||||
* guaranteed.
|
||||
* allocated since dynamic allocation of a 300k buffer cannot be
|
||||
* guaranteed.
|
||||
*
|
||||
* 1999/06/17:
|
||||
* - FrameBuffer memory is now allocated at run-time when the
|
||||
* driver is initialized.
|
||||
* driver is initialized.
|
||||
*
|
||||
* 2000/04/10: Nicolas Pitre <nico@fluxnic.net>
|
||||
* - Big cleanup for dynamic selection of machine type at run time.
|
||||
|
@ -74,8 +74,8 @@
|
|||
*
|
||||
* 2000/08/07: Tak-Shing Chan <tchan.rd@idthk.com>
|
||||
* Jeff Sutherland <jsutherland@accelent.com>
|
||||
* - Resolved an issue caused by a change made to the Assabet's PLD
|
||||
* earlier this year which broke the framebuffer driver for newer
|
||||
* - Resolved an issue caused by a change made to the Assabet's PLD
|
||||
* earlier this year which broke the framebuffer driver for newer
|
||||
* Phase 4 Assabets. Some other parameters were changed to optimize
|
||||
* for the Sharp display.
|
||||
*
|
||||
|
@ -102,7 +102,7 @@
|
|||
* 2000/11/23: Eric Peng <ericpeng@coventive.com>
|
||||
* - Freebird add
|
||||
*
|
||||
* 2001/02/07: Jamey Hicks <jamey.hicks@compaq.com>
|
||||
* 2001/02/07: Jamey Hicks <jamey.hicks@compaq.com>
|
||||
* Cliff Brake <cbrake@accelent.com>
|
||||
* - Added PM callback
|
||||
*
|
||||
|
@ -500,7 +500,7 @@ sa1100fb_set_cmap(struct fb_cmap *cmap, int kspc, int con,
|
|||
* the shortest recovery time
|
||||
* Suspend
|
||||
* This refers to a level of power management in which substantial power
|
||||
* reduction is achieved by the display. The display can have a longer
|
||||
* reduction is achieved by the display. The display can have a longer
|
||||
* recovery time from this state than from the Stand-by state
|
||||
* Off
|
||||
* 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,
|
|||
*/
|
||||
/*
|
||||
* sa1100fb_blank():
|
||||
* Blank the display by setting all palette values to zero. Note, the
|
||||
* Blank the display by setting all palette values to zero. Note, the
|
||||
* 12 and 16 bpp modes don't really use the palette, so this will not
|
||||
* blank the display in all modes.
|
||||
* blank the display in all modes.
|
||||
*/
|
||||
static int sa1100fb_blank(int blank, struct fb_info *info)
|
||||
{
|
||||
|
@ -603,8 +603,8 @@ static inline unsigned int get_pcd(struct sa1100fb_info *fbi,
|
|||
|
||||
/*
|
||||
* sa1100fb_activate_var():
|
||||
* Configures LCD Controller based on entries in var parameter. Settings are
|
||||
* only written to the controller if changes were made.
|
||||
* Configures LCD Controller based on entries in var parameter. Settings are
|
||||
* only written to the controller if changes were made.
|
||||
*/
|
||||
static int sa1100fb_activate_var(struct fb_var_screeninfo *var, struct sa1100fb_info *fbi)
|
||||
{
|
||||
|
@ -747,7 +747,7 @@ static void sa1100fb_setup_gpio(struct sa1100fb_info *fbi)
|
|||
*
|
||||
* SA1110 spec update nr. 25 says we can and should
|
||||
* clear LDD15 to 12 for 4 or 8bpp modes with active
|
||||
* panels.
|
||||
* panels.
|
||||
*/
|
||||
if ((fbi->reg_lccr0 & LCCR0_CMS) == LCCR0_Color &&
|
||||
(fbi->reg_lccr0 & (LCCR0_Dual|LCCR0_Act)) != 0) {
|
||||
|
@ -1020,9 +1020,9 @@ static int sa1100fb_resume(struct platform_device *dev)
|
|||
|
||||
/*
|
||||
* sa1100fb_map_video_memory():
|
||||
* Allocates the DRAM memory for the frame buffer. This buffer is
|
||||
* remapped into a non-cached, non-buffered, memory region to
|
||||
* allow palette and pixel writes to occur without flushing the
|
||||
* Allocates the DRAM memory for the frame buffer. This buffer is
|
||||
* remapped into a non-cached, non-buffered, memory region to
|
||||
* allow palette and pixel writes to occur without flushing the
|
||||
* cache. Once this area is remapped, all virtual memory
|
||||
* access to the video memory should occur at the new region.
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue