public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Syed Mohammed, Khasim" <x0khasim@ti.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 8/11] Compiling dsp-common if DSP is enabled.
Date: Tue, 29 May 2007 09:55:28 -0700	[thread overview]
Message-ID: <20070529165528.GC26322@atomide.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C47FF0E34@dlee13.ent.ti.com>

* Syed Mohammed, Khasim <x0khasim@ti.com> [070528 23:22]:
> 
> Compile dsp_common only if DSP is enabled.
> 
> Signed-off-by: Syed Mohammed Khasim  <x0khasim@ti.com>
> 
> Files Changed:
>  Makefile |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> =======================================================================
> diff -purN linux-omap/arch/arm/plat-omap/dsp/Makefile val_3430_GIT/arch/arm/plat-omap/dsp/Makefile
> --- linux-omap/arch/arm/plat-omap/dsp/Makefile	2006-11-20 21:54:05.000000000 -0600
> +++ val_3430_GIT/arch/arm/plat-omap/dsp/Makefile	2007-05-28 13:30:09.000000000 -0500
> @@ -4,7 +4,7 @@
>  
>  # The target object and module list name.
>  
> -obj-y := dsp_common.o
> +obj-$(CONFIG_OMAP_DSP) := dsp_common.o
>  
>  obj-$(CONFIG_OMAP_DSP) += dsp.o

We should compile DSP for omap1 (and aybe 24xx?) to keep
audio McBSP clock functioning. And eventually we should have common
dsp init that works for all of them.

What if you just add an early return to dsp init code for now with
a revisit comment?

Regards,

Tony

  reply	other threads:[~2007-05-29 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  6:22 [PATCH 8/11] Compiling dsp-common if DSP is enabled Syed Mohammed, Khasim
2007-05-29 16:55 ` Tony Lindgren [this message]
2007-05-29 17:02   ` Woodruff, Richard
2007-05-29 17:08     ` Tony Lindgren

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=20070529165528.GC26322@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=x0khasim@ti.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