All of lore.kernel.org
 help / color / mirror / Atom feed
From: jakob.viketoft@bitsim.com (Jakob Viketoft)
To: linux-arm-kernel@lists.infradead.org
Subject: AC97 problems with pxa...
Date: Thu, 08 Apr 2010 11:17:28 +0200	[thread overview]
Message-ID: <4BBD9F28.9080804@bitsim.com> (raw)
In-Reply-To: <20100407095449.GA13576@rakim.wolfsonmicro.main>

Trying to bring two threads down to one.

Mark Brown wrote:
> On Wed, Apr 07, 2010 at 11:37:24AM +0200, Jakob Viketoft wrote:
> 
> Please don't top post...
> 
>> Do you mean mixing the AC97 non-asoc and asoc drivers or the drivers
>> for the WM9712? I can't see the possibility of mixing anything for
>> the WM9712, but I'm unsure of the distinction between the different
>> AC97 pieces.
> 
> ...without context it's hard to work out what you are talking about.
> 
>> Should this make a difference? My module init function gets called,
>> it's just the snd_soc_dai_link[0].init function that doesn't.
> 
> Build soc-core.c with #define DEBUG at the top then look at your logs

I've run with DEBUG defined and seen a bit more specifics. I have also 
created a device in the board init and added a driver in my machine code 
as per the palmtx code. Nothing I've done seem to change the behaviour 
and I can't quite get my head around what's going on. Does anyone run a 
pxa270 board with AC97 sound and can tell me what output they get from 
dmesg?

As I said before, by writing 0 to the AC97_POWERDOWN register (enabling 
everything) I get perfect sound output, so something seems right. It 
just won't go all the way...

The dmesg output:
Registered platform 'pxa2xx-audio'
Error: Driver 'pxa2xx-ac97' is already registered, aborting...
soc-audio soc-audio: DAI pxa2xx-ac97 not registered
soc-audio soc-audio: Registered card 'Colibri 270 v2'
ALSA device list:
   #0: pxa2xx-ac97 (Wolfson WM9711,WM9712,WM9715)

The pxa2xx-ac97 DAI not being registered does seem troublesome because 
the code in soc_core won't continue without this. Any insights?

> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  reply	other threads:[~2010-04-08  9:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 21:50 AC97 problems with pxa Jakob Viketoft
2010-04-07  2:09 ` Eric Miao
2010-04-07  9:13   ` Jakob Viketoft
2010-04-07 19:08     ` Marek Vasut
2010-04-07  7:50 ` Marek Vasut
2010-04-07  9:37   ` Jakob Viketoft
2010-04-07  9:54     ` Mark Brown
2010-04-08  9:17       ` Jakob Viketoft [this message]
2010-04-08  9:54         ` Mark Brown
2010-04-08 13:05           ` Jakob Viketoft
2010-04-08 13:49             ` Mark Brown
2010-04-08 14:05               ` Jakob Viketoft
2010-04-08 14:12                 ` Mark Brown
2010-04-08 14:35                   ` Jakob Viketoft
2010-04-08 14:44                     ` Mark Brown
2010-04-08 15:07                       ` Jakob Viketoft
2010-04-08 14:06               ` Jakob Viketoft

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=4BBD9F28.9080804@bitsim.com \
    --to=jakob.viketoft@bitsim.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.