All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Kevin Startup <kevin@awcsl.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA SOC Driver (mxs-wm8753)
Date: Fri, 18 Jul 2014 15:28:30 +0100	[thread overview]
Message-ID: <20140718142830.GC12049@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <f889954bfaf244cab1b9eb096c66fa81@DB4PR07MB252.eurprd07.prod.outlook.com>

On Fri, Jul 18, 2014 at 01:02:41PM +0000, Kevin Startup wrote:
> Hi Charles
> 
> Thanks very much, the pointers you gave me have helped a lot.  I have changed the reference to .codec_dai_name to "wm8753-hifi" in the mxs-wm8753.c program which has made my CPU recognise the WM8753 as a valid ALSA device!
> This makes me very happy as I have been trying to get this to happen for several weeks now!
> 
> I still don't seem to be able to send sound to the device though.
> I am now receiving this message:
> 
> mxs-i2c 80058000.i2c: PIO: Failed to finish WRITE cmd!
> 
> This happens a dozen times or so on bootup and any time that I try to write to one of the PCM devices ....
> I wonder if you could give me any more pointers?
> 
> Many Thanks
> Kevin

Looks like probably the i2c transactions are not being acked,
afraid I don't know much about the i2c driver in question so not
really sure. I assume this is the i2c link to the CODEC, so I
would check the CODECs reset lines and supplies to make sure it
has everything it needs to respond.

Thanks,
Charles

  reply	other threads:[~2014-07-18 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  9:14 ALSA SOC Driver (mxs-wm8753) Kevin Startup
2014-07-18  8:44 ` Charles Keepax
2014-07-18 10:14   ` Kevin Startup
2014-07-18 10:53     ` Charles Keepax
2014-07-18 13:02       ` Kevin Startup
2014-07-18 14:28         ` Charles Keepax [this message]
2014-07-23  8:40           ` Kevin Startup
  -- strict thread matches above, loose matches on Subject: below --
2013-03-04 18:25 John Graham
2013-04-29 20:41 ` Mark Brown

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=20140718142830.GC12049@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kevin@awcsl.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.