From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Paulo Sergio <pstglia@gmail.com>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
broonie@opensource.wolfsonmicro.com,
Android-x86 development <android-x86-devel@googlegroups.com>,
Chih-Wei Huang <cwhuang@android-x86.org>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
mika.westerberg@linux.intel.com
Subject: Re: WM5102 - Help to make baytrail machine driver work
Date: Mon, 15 May 2017 07:44:48 -0500 [thread overview]
Message-ID: <bdaae069-fc68-af1d-8e40-a3e0654fa4cc@linux.intel.com> (raw)
In-Reply-To: <CAJcYhpatsrYyC0CRu-0quA0=NYOObMC2nro5sDE-2ssTTu83rA@mail.gmail.com>
On 5/13/17 12:11 AM, Paulo Sergio wrote:
> * This device (Lenovo Yoga 2 1051F) is a bytcr device. However bios
> status returned by iosf_mbi_read is
> 1000000001000000000000101000000 (bits 26:27 disabled).
> Had to force bytcr flag to be true in order to apply correct MCLK
> frequency (25Mhz) and use SSP0
Are you sure it's Baytrail-CR? where does this information come from?
Those fields are tied to which PMIC is used and it would be extremely
surprising to have a disconnect.
next prev parent reply other threads:[~2017-05-15 12:44 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
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 [this message]
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=bdaae069-fc68-af1d-8e40-a3e0654fa4cc@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=android-x86-devel@googlegroups.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cwhuang@android-x86.org \
--cc=mika.westerberg@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).