diff options
author | Paul Walmsley <paul@pwsan.com> | 2012-04-13 06:34:30 -0600 |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2012-04-13 06:34:30 -0600 |
commit | bc4d8b5f9f9dfe155f9e007739a5bb90f79db297 (patch) | |
tree | dfb661f213783704ae3e3eb1bcffdb00aec89fd6 /arch/arm/mach-omap1 | |
parent | 7cc0442cf2c2cc0efd117051d20e531f7cb2d604 (diff) | |
download | talos-op-linux-bc4d8b5f9f9dfe155f9e007739a5bb90f79db297.tar.gz talos-op-linux-bc4d8b5f9f9dfe155f9e007739a5bb90f79db297.zip |
ARM: OMAP: DMA: use constant array maximum, drop some LCD DMA code
gcc can apparently handle stack-allocated arrays that use a dynamic
variable as the array maximum. Rather than using a mutable quantity,
simply use a constant maximum possible size. To me, code clarity is
improved; and it also avoids the following sparse warnings:
arch/arm/plat-omap/dma.c:886:40: error: bad constant expression
arch/arm/plat-omap/dma.c:892:17: error: cannot size expression
arch/arm/plat-omap/dma.c:970:40: error: bad constant expression
arch/arm/plat-omap/dma.c:972:17: error: cannot size expression
Also drop some dead code from the OMAP1 LCD DMA code:
arch/arm/mach-omap1/lcd_dma.c:80:6: warning: symbol 'omap_set_lcd_dma_src_port' was not declared. Should it be static?
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Diffstat (limited to 'arch/arm/mach-omap1')
-rw-r--r-- | arch/arm/mach-omap1/lcd_dma.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/arch/arm/mach-omap1/lcd_dma.c b/arch/arm/mach-omap1/lcd_dma.c index 86ace9aaa663..9237576270b2 100644 --- a/arch/arm/mach-omap1/lcd_dma.c +++ b/arch/arm/mach-omap1/lcd_dma.c @@ -77,11 +77,6 @@ void omap_set_lcd_dma_b1(unsigned long addr, u16 fb_xres, u16 fb_yres, } EXPORT_SYMBOL(omap_set_lcd_dma_b1); -void omap_set_lcd_dma_src_port(int port) -{ - lcd_dma.src_port = port; -} - void omap_set_lcd_dma_ext_controller(int external) { lcd_dma.ext_ctrl = external; |