From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [RFC PATCH 2/3] ASoC: Intel: bdw-rt5677: fix module load/unload issues
Date: Thu, 5 Mar 2020 17:58:43 +0000 [thread overview]
Message-ID: <20200305175843.GI4046@sirena.org.uk> (raw)
In-Reply-To: <20200305142723.GM1224808@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Thu, Mar 05, 2020 at 04:27:23PM +0200, Andy Shevchenko wrote:
> On Thu, Mar 05, 2020 at 07:47:47AM -0600, Pierre-Louis Bossart wrote:
> > I don't fully get the acpi mapping and all.
> This one is easy to explain. ACPI lacks of the proper labeling / mapping GPIO
> resources. _DSD() method helps there, but there are no Wintel firmware that
> supports it (Google basically is the first who utilizes it).
That's not entirely true - the _DSD stuff was also actively being used
by the embedded x86 people since they needed firmware bindings for
things and wanted to import all the work that's been done for DT, or as
much as possible anyway given that there's bits of ACPI that actively
conflict with DT. They were driving this much more actively and doing
much more extensive work than the ChromeOS people. That all seems to
have been abandoned though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-05 17:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 13:06 [RFC PATCH 0/3] ASoC: add dailink .exit() callback Pierre-Louis Bossart
2020-03-05 13:06 ` [RFC PATCH 1/3] ASoC: soc-core: introduce exit() callback for dailinks Pierre-Louis Bossart
2020-03-05 18:15 ` Mark Brown
2020-03-05 13:06 ` [RFC PATCH 2/3] ASoC: Intel: bdw-rt5677: fix module load/unload issues Pierre-Louis Bossart
2020-03-05 13:25 ` Andy Shevchenko
2020-03-05 13:37 ` Pierre-Louis Bossart
2020-03-05 13:36 ` Mark Brown
2020-03-05 13:47 ` Pierre-Louis Bossart
2020-03-05 13:59 ` Mark Brown
2020-03-05 14:51 ` Pierre-Louis Bossart
2020-03-05 17:43 ` Mark Brown
2020-03-05 18:08 ` Pierre-Louis Bossart
2020-03-05 18:33 ` Mark Brown
2020-03-05 19:10 ` Mark Brown
2020-03-05 21:00 ` Curtis Malainey
2020-03-05 21:48 ` Pierre-Louis Bossart
2020-03-06 13:12 ` Mark Brown
2020-03-05 14:06 ` Amadeusz Sławiński
2020-03-05 14:11 ` Mark Brown
2020-03-05 14:27 ` Andy Shevchenko
2020-03-05 17:58 ` Mark Brown [this message]
2020-03-05 13:06 ` [RFC PATCH 3/3] ASoC: Intel: kbl-rt5660: use .exit() dailink callback to release gpiod Pierre-Louis Bossart
2020-03-05 13:27 ` Andy Shevchenko
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=20200305175843.GI4046@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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).