public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Ramón Finger Lilienthal" <ramon@instramed.com.br>
Cc: linux-omap@vger.kernel.org
Subject: Re: TLV320AIC23 not patched
Date: Tue, 28 Oct 2008 09:40:31 -0700	[thread overview]
Message-ID: <20081028164030.GF7539@atomide.com> (raw)
In-Reply-To: <490702CC.9070008@instramed.com.br>

Hi,

* Ramón Finger Lilienthal <ramon@instramed.com.br> [081028 05:17]:
> Fellows,
>
> I have just got the v2.6.28-rc2, and errors while compiling still happening.

We're in process of getting rid of all the various old audio drivers
for omap. The new way is to use the ASoC drivers, see sound/soc/omap
and sound/soc/codecs.

Regards,

Tony


> ---
> CHK include/linux/compile.h
> CC drivers/i2c/chips/tlv320aic23.o
> drivers/i2c/chips/tlv320aic23.c: In function ‘omap_mcbsp3_aic23_clock_init’:
> drivers/i2c/chips/tlv320aic23.c:113: error: implicit declaration of  
> function ‘OMAP_MCBSP_WRITE’
> drivers/i2c/chips/tlv320aic23.c:113: error: ‘SPCR1’ undeclared (first  
> use in this function)
> drivers/i2c/chips/tlv320aic23.c:113: error: (Each undeclared identifier  
> is reported only once
> drivers/i2c/chips/tlv320aic23.c:113: error: for each function it appears  
> in.)
> drivers/i2c/chips/tlv320aic23.c:114: error: ‘SPCR2’ undeclared (first  
> use in this function)
> drivers/i2c/chips/tlv320aic23.c:117: error: ‘PCR0’ undeclared (first use  
> in this function)
> drivers/i2c/chips/tlv320aic23.c:120: error: ‘SRGR1’ undeclared (first  
> use in this function)
> drivers/i2c/chips/tlv320aic23.c:121: error: ‘SRGR2’ undeclared (first  
> use in this function)
> drivers/i2c/chips/tlv320aic23.c:124: error: implicit declaration of  
> function ‘OMAP_MCBSP_READ’
> make[3]: *** [drivers/i2c/chips/tlv320aic23.o] Error 1
> make[2]: *** [drivers/i2c/chips] Error 2
> make[1]: *** [drivers/i2c] Error 2
> make: *** [drivers] Error 2
> ---
>
> These errors was solved by some patchs in August. Why these patchs  
> wasn't applied in the kernel tree?
>
>
> -- 
> Regards,
> Eng. Ramon F. Lilienthal
> Project Engineer
> Instramed Ltda. - www.instramed.com.br
> +55 (51) 33344199 ext. 213
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-10-28 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 12:17 TLV320AIC23 not patched Ramón Finger Lilienthal
2008-10-28 16:40 ` Tony Lindgren [this message]

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=20081028164030.GF7539@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ramon@instramed.com.br \
    /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