alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Bennett <jbscience87@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Aaron Kling <webgeek1234@gmail.com>,
	Igor Grinberg <grinberg@compulab.co.il>,
	Valentin Raevsky <valentin@compulab.co.il>
Subject: Re: Help with wm8731 support for the Utilite (imx6q)
Date: Tue, 21 Oct 2014 17:37:39 -0500	[thread overview]
Message-ID: <CAB-pspcZ8bhLMPDS2NbDOEugfzO+TZfOnA_h05pvkU5ZPv6qVQ@mail.gmail.com> (raw)
In-Reply-To: <CAB-pspcmxQAzR=jX1_fp06UUgNbC_LXFDN4g6RnOn6vTTvJjTw@mail.gmail.com>

On Tue, Oct 21, 2014 at 1:49 PM, Jonathan Bennett <jbscience87@gmail.com>
wrote:

>
>
> On Tue, Oct 21, 2014 at 1:12 PM, Fabio Estevam <festevam@gmail.com> wrote:
>
>> On Tue, Oct 21, 2014 at 4:04 PM, Jonathan Bennett <jbscience87@gmail.com>
>> wrote:
>>
>> > I realized something just last night. I was grabbing changes from the
>> devel
>> > branch of github.com/utilite-computer, thinking that those changes were
>> > based off the vanilla 3.10 kernel. Those changes are actually based on
>> the
>> > Freescale 3.10 kernel. I pulled a Freescale patch that is obviously
>> missing:
>> > "ENGR00276249-1 ARM: imx6q: Add missing baud clock for ssi" I also
>> switched
>>
>> The baud clock patch is present in 3.18-rc1:
>>
>> commit 935632e9938e3e286b9c62a7e54d35c428533cc9
>> Author: Shengjiu Wang <shengjiu.wang@freescale.com>
>> Date:   Tue Sep 9 17:13:26 2014 +0800
>>
>>     ARM: dts: imx6qdl: add baud clock and clock-names for ssi
>>
>>     Baud clock is used for bit clock generation in master mode. Ipg clock
>>     is peripheral clock and peripheral access clock.
>>
>>     Signed-off-by: Shengjiu Wang <shengjiu.wang@freescale.com>
>>     Signed-off-by: Shawn Guo <shawn.guo@freescale.c
>>
>  Awesome!
> It's great to see this stuff go mainline.
>

I have rebased to 3.18 rc-1. It has simplified the patch set a bit, as more
of  the Freescale things have hit mainline. http://pastebin.com/C652GKe3 is
my patchset.
Again, the card registers and thinks it plays, but there is no actual
output.


>> > back to imx-wm8731.c for the driver. With this setup, the driver
>> registers,
>> > and speaker-test thinks it plays, however there is no actual sound
>> output. I
>> > call it progress.
>>
>> Great progress: some things to check :
>>
>> 1. audmux settings
>>
> Well, the imx-wm8731 driver (It's really just glue for loading wm8731)
> does have audmux settings in it. These get called during the module probe.
> Not sure what might need to change there. My thoughts are that they should
> be correct.
>
>
>>
>> 2. Can you try to run 'alsamixer' and make sure that the volume is not
>> at the lowest level?
>>
> Yeah, I've made sure to check alsamixer and turn the volume up. Still no
> joy.
>

  reply	other threads:[~2014-10-21 22:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 16:57 Help with wm8731 support for the Utilite (imx6q) Jonathan Bennett
2014-10-18 19:13 ` Fabio Estevam
2014-10-19  5:35   ` Jonathan Bennett
2014-10-19  5:58     ` Jonathan Bennett
2014-10-20 12:06       ` Fabio Estevam
2014-10-20 16:29         ` Fabio Estevam
2014-10-20 19:59           ` Jonathan Bennett
2014-10-21 12:06             ` Valentin Raevsky
2014-10-21 18:04               ` Jonathan Bennett
2014-10-21 18:12                 ` Fabio Estevam
2014-10-21 18:49                   ` Jonathan Bennett
2014-10-21 22:37                     ` Jonathan Bennett [this message]
2014-10-22  8:04                       ` Valentin Raevsky
2014-10-22 12:13                         ` Jonathan Bennett
2014-10-22 12:17                           ` Fabio Estevam
2014-10-22 13:32                             ` Jonathan Bennett
2014-10-22 14:29                               ` Fabio Estevam
2014-10-22 16:02                                 ` Fabio Estevam
2014-10-22 17:43                                   ` Jonathan Bennett
2016-04-06  8:25                                     ` Karolina

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=CAB-pspcZ8bhLMPDS2NbDOEugfzO+TZfOnA_h05pvkU5ZPv6qVQ@mail.gmail.com \
    --to=jbscience87@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=festevam@gmail.com \
    --cc=grinberg@compulab.co.il \
    --cc=valentin@compulab.co.il \
    --cc=webgeek1234@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 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).