From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 3/8] ASoC: intel: boards: add card for MinnowBoard I2S access
Date: Wed, 6 Jan 2016 14:59:05 -0600 [thread overview]
Message-ID: <568D8019.3050407@linux.intel.com> (raw)
In-Reply-To: <20160106174207.GC6588@sirena.org.uk>
On 1/6/16 11:42 AM, Mark Brown wrote:
> On Tue, Jan 05, 2016 at 08:50:11AM -0600, Pierre-Louis Bossart wrote:
>> On 1/5/16 7:15 AM, Mark Brown wrote:
>
>>> I'm wondering how this is going to get loaded (I don't see what creates
>>> the platform device) and how we handle systems with a CODEC connected on
>>> the expansion headers?
>
>> Good question.
>
>> To solve this audio is disabled by default, and we have an EFI application
>> loaded by the startup.nsh file that sets the relevant codec information in
>> the SSDT table so that you can swap codec cards at will. The EFI application
>> will be open-sourced so that additional codecs can be added as needed with
>> changes in the ASL code. The whole thing was tested with experimental
>> releases in three different setups for now but will be formally released
>> next month.
>
> Sets the relevant codec information by...?
exposing devices and dependencies, setting the _HID, codec I2C address,
Gpio lines, DSD properties if needed. Nothing new compared to a normal
DSDT table except that you only add the audio-related information yourself.
>
>> On probe the sst_acpi part checks for the presence of known codecs and
>> registers the platform driver. For the case where no codec is present I just
>> added an entry at the end of the table that always works (checks for an
>> SOC-side HID) and is selected if no other codec was found. I need to add
>> this patch and submit it, forgot to add it in this batch.
>
> Can we punt on this until we've got the rest of the infrastructure to
> look at? I'd feel safer and it sounds like it's going to need some
> manual hacking to get working anyway until the other bits are lined up.
that's fine, i will provide more documentation to explain the steps
later this month. The 'infrastructure' isn't that bad really - and since
the SSDT update application is open-source for once you can't blame the
BIOS if your audio doesn't work :-)
next prev parent reply other threads:[~2016-01-06 20:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 23:20 [PATCH v2 0/8] Baytrail followup Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 1/8] ASoC: Intel: fix ACPI probe regression with Atom DPCM driver Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 2/8] ASoC: Intel: add bytct-rt5651 machine driver Pierre-Louis Bossart
2016-01-05 17:49 ` Applied "ASoC: Intel: add bytct-rt5651 machine driver" to the asoc tree Mark Brown
2016-01-04 23:20 ` [PATCH v2 3/8] ASoC: intel: boards: add card for MinnowBoard I2S access Pierre-Louis Bossart
2016-01-05 13:15 ` Mark Brown
2016-01-05 14:50 ` Pierre-Louis Bossart
2016-01-06 17:42 ` Mark Brown
2016-01-06 20:59 ` Pierre-Louis Bossart [this message]
2016-01-04 23:20 ` [PATCH v2 4/8] ASoC: rt5640: add ASRC support Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 5/8] ASoC: Intel: bytcr-rt5640: enable ASRC Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 6/8] ASoC: Intel: bytcr_rt5640: fixup DAI codec_name with HID Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 7/8] ASoC: Intel: Atom: add support for RT5642 Pierre-Louis Bossart
2016-01-04 23:20 ` [PATCH v2 8/8] ASoC: Intel: Atom: Add support for HP ElitePad 1000 G2 Pierre-Louis Bossart
2016-01-05 12:43 ` [PATCH v2 0/8] Baytrail followup Mark Brown
2016-01-05 14:41 ` 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=568D8019.3050407@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
/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).