[alsa-devel] Help with wm8731 support for the Utilite (imx6q)

[Jonathan Bennett]

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

>
>
> On Tue, Oct 21, 2014 at 1:12 PM, Fabio Estevam <festevam at gmail.com> wrote:
>
>> On Tue, Oct 21, 2014 at 4:04 PM, Jonathan Bennett <jbscience87 at 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 at 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 at freescale.com>
>>     Signed-off-by: Shawn Guo <shawn.guo at 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.
>