All of lore.kernel.org
 help / color / mirror / Atom feed
From: lexa@cfotr.com (lexa)
To: linux-arm-kernel@lists.infradead.org
Subject: Debugging missing interrupts
Date: Mon, 25 Feb 2013 12:37:28 +0400	[thread overview]
Message-ID: <1361781448.4640.49.camel@localhost> (raw)
In-Reply-To: <512B1AE6.6070903@atmel.com>

On Mon, 2013-02-25 at 16:03 +0800, Bo Shen wrote:
> Hi Lexa,
> 
> On 2/25/2013 15:34, lexa wrote:
> >
> > Hello.
> >
> > I have a trouble with debugging SSC interface(or maybe with audio
> > codec). I have a board based on Atmel AT91 (at91sam9m10g45) and codec TI
> > tlv320aic3106(using driver tlv320aic3x) connected to SSC interface in
> > I2S mode.
> 
> Which kernel version do you use?

I use 3.2.38

> SSC work as master or slave?
> 

SSC works as slave for playback and for capture(as far as i know there
no difference in configuration SSC controller). Audio codec is
generating bit clock and word clock, and ARM is receiving them.

> > Playback is works well, but the capture cause trouble.
> > The problem is that arecord don't capture any data, he just writes wav
> > header and nothing more.
> 
> Which command do you use for recording? (it will give sample rate, 
> format, and etc)
> 
> > Interrupt counter on ssc0 does not increased during capture.
> > Also i checked data and clock lines by oscilloscope, and clearly see
> > that clock and data transmitting from audio codec during capture.
> > It's seem to me, that cpu somewhat doesn't accept data from codec. But i
> > don't understand why, and how to debug this.
> >
> > I know that provided information is insufficient, but i simply don't
> > know how to get more detailed information about this problem.
> 
> Best Regards,
> Bo Shen
> 

  reply	other threads:[~2013-02-25  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  7:34 Debugging missing interrupts lexa
2013-02-25  8:03 ` Bo Shen
2013-02-25  8:37   ` lexa [this message]
2013-02-25  9:21     ` Bo Shen
     [not found]       ` <1361790127.4640.58.camel@localhost>
     [not found]         ` <512C118D.4060105@atmel.com>
2013-03-04 10:24           ` lexa
2013-03-05  8:09             ` Bo Shen

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=1361781448.4640.49.camel@localhost \
    --to=lexa@cfotr.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.