From: Frank Mandarino <fmandarino@endrelia.com>
To: Paul Kavan <pkavan@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: at91 SoC Modifications
Date: Fri, 22 Jun 2007 12:49:25 -0400 [thread overview]
Message-ID: <467BFD95.3080707@endrelia.com> (raw)
In-Reply-To: <61c0054e0706220853x5502066ck8765365df9b3abf0@mail.gmail.com>
Paul Kavan wrote:
> I just don't think it is a hardware problem. I a polling ssc driver that
> works very nicely for this codec. However, it is polling and I do not
> want to rely on it when I have more of a load on the processor.
>
> I have the machine/codec code and at91-ssc.c configured so that the
> registers and gpio should be set up identical to what I had before and
> it is not generating a proper sync signal with arecord. When I do strace
> on arecord it hangs at this first line before finishing.
>
>
> ioctl(4, 0x800c4151, 0xbed9cc34) = -1 EIO (Input/output error)
> write(2, "arecord", 7arecord) = 7
> write(2, ": ", 2: ) = 2
> write(2, "pcm_read", 8pcm_read) = 8
> write(2, ":", 1:) = 1
> write(2, "1346", 41346) = 4
> write(2, ": ", 2: ) = 2
> write(2, "read error: ", 12read error: ) = 12
> write(2, "Input/output error", 18Input/output error) = 18
> write(2, "\n", 1
> ) = 1
> exit(1) = ?
>
>
> Does anyone know what this line is doing? I think it might give a clue.
> The sync line still ripples at about .3V peak to peak with f=256k (Bit
> Clock Rate).
Sorry, I have no idea what that line is doing.
> Frank: I modified the machine code so that RF0 and RK0 are set in the
> gpio. The only differences are that the sync line no longer tri-states
> after going trying to record and instead of seeing the ripple around 3V
> it is now around 200 mV.
Now that I think about, if you are using RK0 as an input and driving it
from TK0, then you should be initializing the RK0 GPIO. On our board,
the RK2 GPIO pin is not used since RK2 is generated internally from the
TK2 clock signal (AT91_SSC_CKS_CLOCK), so there was no need to
initialize it.
Also, the RF2 GPIO is not used on our board, because there is a single
sync signal sent to the codec, and this is supplied by TF2.
Perhaps it would be useful to see a diagram of the connections between
the SSC and codec on your board, including directions.
../fam
--
Frank Mandarino fmandarino(a)endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada
next prev parent reply other threads:[~2007-06-22 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 21:21 at91 SoC Modifications Paul Kavan
2007-06-20 21:46 ` Paul Kavan
2007-06-21 12:07 ` Liam Girdwood
2007-06-21 14:47 ` Paul Kavan
2007-06-21 19:10 ` Paul Kavan
2007-06-21 20:32 ` Paul Kavan
2007-06-21 21:26 ` Liam Girdwood
2007-06-22 15:53 ` Paul Kavan
2007-06-22 16:49 ` Frank Mandarino [this message]
2007-06-22 17:23 ` Paul Kavan
2007-06-22 19:00 ` Frank Mandarino
2007-06-25 20:09 ` Paul Kavan
2007-06-25 20:32 ` Frank Mandarino
2007-06-25 20:45 ` Paul Kavan
2007-06-25 20:47 ` Paul Kavan
2007-06-25 21:51 ` Paul Kavan
2007-06-25 22:43 ` Liam Girdwood
2007-06-26 11:53 ` Frank Mandarino
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=467BFD95.3080707@endrelia.com \
--to=fmandarino@endrelia.com \
--cc=alsa-devel@alsa-project.org \
--cc=pkavan@gmail.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.