From: Christian Hartmann <cornogle@googlemail.com>
To: alsa-devel@alsa-project.org
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
patches@opensource.wolfsonmicro.com
Subject: ASoC : WM5102 Audio Codec needs ACPI support and a baytrail machine driver
Date: Tue, 16 Jun 2015 12:00:04 +0200 [thread overview]
Message-ID: <CAKor6TdbnLuJCsBPykPEmhGk-zBLggKxw4Z+=QuBb6Mz2ThD3g@mail.gmail.com> (raw)
Hi list,
I have a device "Lenovo Yoga 851 F" which have a WM510205 Audio codec
on a Baytrail System.
I have sent already one patch (spi-pxa2xx) raise num_chipselect by one, which
fixes to bind the arizona WM5102 codec as a spi slave attachted on a
pxa2xx spi master device.
I have tried several times and added the ACPI id "WM510205" to
the arizona-spi.c driver.
The ACPI ID is extracted from the DSDT.dsl of this machine.
But unfortunately it fails and I got only a NULL pointer deference error
in arizona_spi_probe().
I want to request ACPI support for this device and I cannot fix
currently the NULL pointer.
I do not know yet, if I have to add this ACPI id to the arizona-spi
driver (sure,
thats what I am trying and failing) or to the NEW baytrail machine driver.
In this case it should be the bytcr_wm5102.c and byt-wm5102.c, which
does not exists yet.
I have a branched tovalds/master and added (my first attempt) the
above mentioned machine driver on a local branch. The result is only
a dsp boot timeout error.
Any help, ideas, hints, patches to try would be appreciate
sincerely yours
Christian Hartmann
a snap of the dsdt
Device (LPEA)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "80860F28" /* Intel SST Audio DSP */) //
_HID: Hardware ID
Name (_CID, "80860F28" /* Intel SST Audio DSP */) //
_CID: Compatible ID
Name (_DDN, "Intel(R) Low Power Audio Controller -
80860F28") // _DDN: DOS Device Name
Name (_SUB, "17AA7004") // _SUB: Subsystem ID
Name (_UID, One) // _UID: Unique ID
Name (_DEP, Package (0x01) // _DEP: Dependencies
{
^SPI1.AUDI
})
...
...
Device (AUDI)
{
Name (_HID, "WM510205") // _HID: Hardware ID
Name (_CID, "WM510205") // _CID: Compatible ID
Name (_DDN, "Wolfson Microelectronics Audio WM5102")
// _DDN: DOS Device Name
Method (_CRS, 0, NotSerialized) // _CRS: Current
Resource Settings
{
Name (SBUF, ResourceTemplate ()
{
SpiSerialBus (0x0001, PolarityLow, FourWireMode, 0x08,
ControllerInitiated, 0x007A1200, ClockPolarityLow,
ClockPhaseFirst, "\\_SB.SPI1",
0x00, ResourceConsumer, ,
)
GpioInt (Edge, ActiveLow, ExclusiveAndWake,
PullNone, 0x0000,
"\\_SB.GPO2", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0004
}
GpioIo (Exclusive, PullDefault, 0x0000,
0x0000, IoRestrictionOutputOnly,
"\\_SB.I2C7.PMIC", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0003
}
GpioIo (Exclusive, PullDefault, 0x0000,
0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO1", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0017
}
})
next reply other threads:[~2015-06-16 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 10:00 Christian Hartmann [this message]
2015-06-16 12:27 ` ASoC : WM5102 Audio Codec needs ACPI support and a baytrail machine driver Christian Hartmann
2015-06-16 13:10 ` Fwd: " Christian Hartmann
2015-06-16 14:47 ` Charles Keepax
2015-06-22 9:55 ` Christian Hartmann
2015-06-22 12:00 ` Charles Keepax
2015-06-24 8:48 ` Charles Keepax
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='CAKor6TdbnLuJCsBPykPEmhGk-zBLggKxw4Z+=QuBb6Mz2ThD3g@mail.gmail.com' \
--to=cornogle@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-acpi@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.