ALSA support for H2 board

Hello,

I tried adding ALSA support for the H2 board using a recent kernel (2.6.24.3, from the montavista git tree) and got the following errors:

$ make omap_h2_1610_defconfig (ran ok)
$ make menuconfig (ran ok)
$ make modules
 ...
  CC [M]  sound/sound_core.o
  LD [M]  sound/soundcore.o
  CC [M]  sound/arm/omap/omap-alsa.o
  CC [M]  sound/arm/omap/omap-alsa-dma.o
  CC [M]  sound/arm/omap/omap-alsa-tsc2101.o
sound/arm/omap/omap-alsa-tsc2101.c: In function
`tsc2101_audio_write':
sound/arm/omap/omap-alsa-tsc2101.c:146: error:
implicit declaration of function `omap_tsc2101_write'
sound/arm/omap/omap-alsa-tsc2101.c: In function
tsc2101_audio_read':
sound/arm/omap/omap-alsa-tsc2101.c:154: error:
implicit declaration of function `omap_tsc2101_read'
make[3]: *** [sound/arm/omap/omap-alsa-tsc2101.o]
Error 1
make[2]: *** [sound/arm/omap] Error 2
make[1]: *** [sound/arm] Error 2
make: *** [sound] Error 2

I found an earlier post describing a similar error here:
http://linux.omap.com/pipermail/linux-omap-open-source/2007-October/011765.html
and was wondering if anyone has any suggestions on how to get this to work or if I should go back to an earlier version of the kernel that does work.

Thanks and regards,
Carlos

Better IMO to get the tsc210x core working on tsc2101 chips...

OK understood, I'll use OSS then.

Thanks,
cd

David Brownell <[email protected]> wrote:

Better IMO to get the tsc210x core working on tsc2101 chips...

You seem to have leaped from "use a more modern SPI framework" to "use old sound framework" ... how does that happen??

David,

I understood from your previous message: "Better IMO to get the tsc210x core working on tsc2101 chips" that there are bugs in the tsc2101 drivers used by ALSA...which leaves me no choice but to use OSS, since I know nothing about debugging/writing device drivers.

Am I completely off the mark? Would appreciate any suggestions you may have.

Best,
Carlos

David Brownell <[email protected]> wrote:

You seem to have leaped from "use a more modern SPI framework" to "use old sound framework" ... how does that happen??

No, it's just that the driver you referenced is using old driver infrastructure. That's not "bugs", it's just "this code needs updating".

- Dave