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@linux.intel.com,
mika.westerberg@linux.intel.com
Subject: Re: WM5102 - Help to make baytrail machine driver work
Date: Thu, 5 May 2016 10:11:22 +0100 [thread overview]
Message-ID: <20160505091122.GE1646@localhost.localdomain> (raw)
In-Reply-To: <CAJcYhpZU-6_AO_Gye1VttuvOP0Z2=wLuWGCOP7tBWc6DsuLU1g@mail.gmail.com>
On Wed, May 04, 2016 at 10:21:21PM -0300, Paulo Sergio wrote:
> Hi list,
>
> I've been trying to make Lenovo Yoga 2 (Model 1051F) sound work on
> Android-x86/ Linux. [1]
>
> Based on already discussed info from Christian Hartmann with members (see
> [2] and [3] ) of this list and some efforts (basically patch pxa2xx with
> Mika Westerberg changes, set the correct gpio int values {246 for reset /
> 405 for ldoena and 342 for irq_gpio} and set LDO1 vcc suppliers) we could
> have wm5102 initialized through spi / regmap (arizona code on drivers/mfd)
> and register the DAI's.
>
> I also ported a machine driver code from a kernel Lenovo made available for
> a similar hardware (Lenovo yoga 2 1050 - uses the same baytrail Z3745 and
> wolfson wm5102 audio) [4]
>
> Although machine driver is registered, we still don't have sound. Tried
> some mixer settings / routes used on raspberry pi, but none help.
> Application (in this case alsa / Android players) returns a "Device or
> resource busy" when trying to ioctl pcm device:
A quick look through your machine driver looks like the parts
relating the CODEC look ok.
I am not so sure about the AP side routing but for the CODEC,
'HPOUT1L Input 1' AIF1RX1
'HPOUT1R Input 1' AIF1RX2
'HPOUT1 Digital Switch' 1
Should be enough to route some audio out the headphones, assuming
AIF1 is connected to the AP and HPOUT1L is the headphones (it is
very rare for people to not wire things up that way so its quite
a good bet, and your machine driver suggests this is how it is
connected).
If you provide some kernel logs with the LOG_DEVICE in
drivers/base/regmap/regmap.c set to the CODEC spi device, I am
happy to sanity check what is going to the CODEC. Although at the
moment I think your issue looks mostly like getting through the
AP side.
Thanks,
Charles
next prev parent reply other threads:[~2016-05-05 9:11 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 [this message]
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
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=20160505091122.GE1646@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).