public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] ARM: OMAP: Fix compilation of dsp_mem.c
Date: Sat, 19 May 2007 16:48:51 +0200	[thread overview]
Message-ID: <464F0E53.50007@googlemail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 281 bytes --]


Fix compilation of dsp_mem.c. omapfb_ready is only available if 
CONFIG_FB_OMAP_LCDC_EXTERNAL is set, else compiler stops with error. 
status is only used in case CONFIG_FB_OMAP_LCDC_EXTERNAL is set. 
Compiler warns about this.

Signed-off-by: Dirk Behme <dirk.behme@gmail.com>



[-- Attachment #2: fix_error_omapfb_ready_undeclared.txt --]
[-- Type: text/plain, Size: 854 bytes --]

Index: linux-osk/arch/arm/plat-omap/dsp/dsp_mem.c
===================================================================
--- linux-osk.orig/arch/arm/plat-omap/dsp/dsp_mem.c
+++ linux-osk/arch/arm/plat-omap/dsp/dsp_mem.c
@@ -210,11 +210,13 @@ void mbox_fbctl_upd(void)
 	win.format = buf[4];
 	release_ipbuf_pvt(ipbuf_sys_da);
 
+#ifdef CONFIG_FB_OMAP_LCDC_EXTERNAL
 	if (!omapfb_ready) {
 		printk(KERN_WARNING
 		       "omapdsp: fbupd() called while HWA742 is not ready!\n");
 		return;
 	}
+#endif
 	omapfb_update_window_async(registered_fb[0], &win, fbupd_cb, NULL);
 }
 
@@ -237,7 +239,10 @@ static int dsp_fbexport(dsp_long_t *dspa
 {
 	dsp_long_t dspadr_actual;
 	unsigned long padr_sys, padr, fbsz_sys, fbsz;
-	int cnt, status;
+	int cnt;
+#ifdef CONFIG_FB_OMAP_LCDC_EXTERNAL
+	int status;
+#endif
 
 	pr_debug( "omapdsp: frame buffer export\n");
 

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



                 reply	other threads:[~2007-05-19 14:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=464F0E53.50007@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox