From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Joel Holdsworth <joel@airwebreathe.org.uk>, alsa-devel@alsa-project.org
Subject: Re: Broken IRQs on BayTrail devices
Date: Mon, 25 Apr 2016 08:15:15 -0500 [thread overview]
Message-ID: <571E1863.9090202@linux.intel.com> (raw)
In-Reply-To: <571D8633.9050707@airwebreathe.org.uk>
On 4/24/16 9:51 PM, Joel Holdsworth wrote:
> Dear All,
>
> I've been working on a kernel patch for a firmware IRQ quirk issue that
> affects multiple Intel Atom Bay-Trail boards:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=117141
>
> If you have a Bay Trail device with non-functioning sound, can you
> attach the DSDT and dmidecode output to the bug so I can investigate
> whether the quirk affect your device.
The IRQ fix is not enough to get sound on Baytrail-CR devices. You need
to also swap SSP2 with SSP0 due to a package change, which is not
supported with the 'older' byt-rt5640 driver so that's a dead-end -
sorry. There are Intel patching coming for the bytcr-rt5640 to model all
the possible routing and quirks, stay tuned.
prev parent reply other threads:[~2016-04-25 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 2:51 Broken IRQs on BayTrail devices Joel Holdsworth
2016-04-25 13:15 ` Pierre-Louis Bossart [this message]
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=571E1863.9090202@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=joel@airwebreathe.org.uk \
/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).