alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Paulo Sergio <pstglia@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Christian Hartmann <cornogle@googlemail.com>,
	vinod.koul@intel.com, broonie@opensource.wolfsonmicro.com,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	mika.westerberg@linux.intel.com
Subject: Re: WM5102 - Help to make baytrail machine driver work
Date: Fri, 13 May 2016 12:41:36 +0100	[thread overview]
Message-ID: <20160513114136.GM1646@localhost.localdomain> (raw)
In-Reply-To: <CAJcYhpa8OrxyFxL1L4VQJL=WSEhrKhvfcdLeUj40Hb=N2kDUUQ@mail.gmail.com>

On Thu, May 12, 2016 at 11:54:55PM -0300, Paulo Sergio wrote:
> Hi again
> 
> 2016-05-09 11:22 GMT-03:00 Charles Keepax <ckeepax@opensource.wolfsonmicro.com>:
> > 'HPOUT1R Input 1' 'Tone Generator 1'
> >
> > This will hook the right headphone channel up to the chips
> > internal 1k tone generator. Careful it will be loud, but its
> > a good check to make sure the clocks are all happy inside the
> > chip. If you hear that tone, I would say the CODEC side looks
> > happy, but let me know how you get on.
> 
> We tried, but unfortunatelly no tone when hooking the tone generator.
> Saved dmesg, logcat and alsa_amixer output in case you want to take a look [2]

Hmm... that is really odd, I would very much have expected that
to work or the FLL to have given us a lock timed out error, which
it didn't appear to be from your log.

Could perhaps send through a register dump of the CODEC whilst in
this state? You can do this through the regmap debugfs it would
be good to turn cache_bypass on as well whilst doing it to make
sure we capture the actual hardware status.

> 
> I'm still having this message on logcat:
> "out_write: error -1 - cannot prepare channel: Device or resource busy"
> which happens when trying to ioctl
> SNDRV_PCM_IOCTL_PREPARE to /dev/snd/pcmC0D0p
> 
> Maybe the problem is something wrong/missing on Machine Driver...
> Pierre said It would be good base the code on bytcr_5640...

Yeah this is pretty unlikely to be coming from the CODEC side.

Thanks,
Charles

  reply	other threads:[~2016-05-13 11:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJcYhpZU-6_AO_Gye1VttuvOP0Z2=wLuWGCOP7tBWc6DsuLU1g@mail.gmail.com>
2016-05-05  3:15 ` WM5102 - Help to make baytrail machine driver work Pierre-Louis Bossart
2016-05-07  3:40   ` Paulo Sergio
2016-05-05  9:11 ` Charles Keepax
2016-05-07  3:19   ` Paulo Sergio
2016-05-08 11:44     ` Paulo Sergio
2016-05-09 14:22       ` Charles Keepax
2016-05-13  2:54         ` Paulo Sergio
2016-05-13 11:41           ` Charles Keepax [this message]
2016-05-14 23:14             ` Paulo Sergio
2016-05-15 10:13               ` Charles Keepax
     [not found]                 ` <CAJcYhpaFiDrMYmbS1cUWL=ix-L2crjnNekpCXjjdHVThwp2Xag@mail.gmail.com>
     [not found]                   ` <20170508082422.GJ1594@localhost.localdomain>
2017-05-09  0:57                     ` Paulo Sergio
2017-05-09  3:15                       ` Pierre-Louis Bossart
2017-05-09 14:45                         ` Paulo Sergio
2017-05-09 14:57                           ` Pierre-Louis Bossart
2017-05-10  8:21                             ` Charles Keepax
2017-05-13  5:11                             ` Paulo Sergio
2017-05-15 12:02                               ` Charles Keepax
2017-05-15 12:44                               ` Pierre-Louis Bossart
2017-05-15 13:10                                 ` Paulo Sergio
2017-05-18 12:49                                   ` Paulo Sergio
2017-05-18 14:58                                     ` Pierre-Louis Bossart

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=20160513114136.GM1646@localhost.localdomain \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cornogle@googlemail.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=pstglia@gmail.com \
    --cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).