From: lamikr <lamikr@cc.jyu.fi>
To: Daniel Petrini <d.pensator@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: omap alsa tsc2101 driver
Date: Tue, 07 Feb 2006 22:40:08 +0200 [thread overview]
Message-ID: <43E905A8.9090307@cc.jyu.fi> (raw)
In-Reply-To: <9268368b0602070634g47a53b15w6492c036166f6cb4@mail.gmail.com>
Daniel Petrini wrote:
>Hi,
>
>On 2/7/06, lamikr <lamikr@cc.jyu.fi> wrote:
>
>
>>>Yes, I am sending it right now (I have just updated my tree). Please
>>>note that it is really work in progress code, with remaining debug
>>>printks and so on. I will clean up soon.
>>>Try to make it work w/ your device, you will have to change the board*
>>>file accordingly H2 or osk in this patch.
>>>
>>>
>>>
>>>
>>Yes, I made the changes. I kind of liked from the idea to codec
>>aic/tsc2101 specific
>>functions in the board, but the side-effect is that I was not able to
>>build the driver anymore
>>as a module. (I got unresolved function errors in the end of build). But
>>when selecting to
>>build the driver in to image, it compiled just fine.
>>
>>
>
>That will be fixed. The idea to have separeted file for alsa generic
>and codecs is that you can work or improve diferent parts of the
>driver indenpendently. And of course reuse code.
>
>
Yes, that seems to be very doable. In my driver I just planned to take
the tsc2101 code
totally separately until I can get it somehow working.
>Humm, Maybe the problems dwells in this function:
>omap_get_dma_src_addr_counter
> (called in alsa-omap driver core file) Please try to analyse its
>behavior for omap1510, the idea is to get the current position of a
>dma transfer. Maybe the registers are diferent in 1510 which has
>different dma engine.
>
>
Thanks for the idea, I will try to investigate it later on today. I just
checked
that the OSS code is not relying to omap_get_dma_src_addr_counter()
function at all
so that might explain the reason why the oss version works for me.
>>Any changes you could also test the playback with my driver version, it
>>could help me to identify the problem
>>
>>
>
>I compiled but I can not play yet, I think that my alsa programs are
>old in my rootfs. I compile them as modules or integrated without
>success. I will update my rfs.
>It says: alsactl: load_state:1236: No soundcards found...
>After I make it run I give you a feedback.
>
>
Hmm, did you remember to change the board code, to register the driver?
I use here:
static struct platform_device h6300_mcbsp1_device = {
.name = "omap_tsc2101_mcbsp",
.id = 1,
};
static struct platform_device *h6300_devices[] __initdata = {
&h6300_mcbsp1_device,
};
If the driver loads correctly, you should be able to use alsamixer with
recent alsa utils.
The version I have tested here is from alsa 1.0.9. In addition you can
turn the debug on from omap-alsa.h
>>Below is the debug from my attempt with your driver...
>>
>>Mika
>>
>>root@h6300:~# aplay 01_the_grudge.mp3
>>Playing raw data '01_the_grudge.mp3' : Unsigned 8 bit, Rate 8000 Hz, Mono
>>
>>
>
>The support for 8Khz is not ok yet although I think that you have
>tested for other frequencies. I can see in the remaining of the debug
>that it seems ok. Maybe the problem is in that function pointed above.
>
>
With speaker-test I have used many frequencies but from wav-files I only
tested
"Signed 16 bit Little Indian with 44100 hz". The madplay I have here
requires me to modprobe
snd-pcm-oss OSS compatibility module.
Mika
next prev parent reply other threads:[~2006-02-07 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 21:24 omap alsa tsc2101 driver lamikr
2006-02-06 19:13 ` Daniel Petrini
2006-02-06 20:17 ` lamikr
2006-02-06 22:01 ` Daniel Petrini
2006-02-07 12:43 ` lamikr
2006-02-07 14:34 ` Daniel Petrini
2006-02-07 20:40 ` lamikr [this message]
2006-02-07 22:29 ` Daniel Petrini
2006-02-07 23:05 ` lamikr
2006-02-07 23:16 ` lamikr
2006-02-08 12:59 ` lamikr
2006-02-07 16:19 ` Anderson Lizardo
2006-02-07 20:43 ` lamikr
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=43E905A8.9090307@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=d.pensator@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.