From: Mark Brown <broonie@kernel.org>
To: "Tc, Jenny" <jenny.tc@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH 0/2] Introduce dmic mode switch delay parameter
Date: Wed, 24 Oct 2018 14:35:56 +0100 [thread overview]
Message-ID: <20181024133556.GR2103@sirena.org.uk> (raw)
In-Reply-To: <20ADAB092842284E95860F279283C564568C0050@BGSMSX104.gar.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
On Tue, Oct 23, 2018 at 05:11:57PM +0000, Tc, Jenny wrote:
> The driver already exposes another parameter (wakeup-delay-ms) using device tree.
> Enabling ACPI device enumeration provides a way to pass existing parameter
> and also cover the new parameter(modeswitch_delay_ms) introduced in this patch set.
> Isn't it good to adopt ACPI enumeration if the driver has multiple parameters to handle?
If you want to adopt device tree bindings in ACPI systems there is
already the _DSD based mapping for this. However please be aware that
ACPI and DT systems have radically different approaches in a number of
areas, including describing sound cards, and trying to combine the two
in the same system might lead to disappointment.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-10-24 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 5:57 [PATCH 0/2] Introduce dmic mode switch delay parameter Jenny TC
2018-10-02 5:57 ` [PATCH 1/2] ASoC: dmic: Enable ACPI device entry Jenny TC
2018-10-02 15:00 ` Mark Brown
2018-10-02 17:12 ` Matthias Kaehlcke
2018-10-02 5:57 ` [PATCH 2/2] ASoC: dmic: Introduce mode switch delay Jenny TC
2018-10-22 3:42 ` [PATCH 0/2] Introduce dmic mode switch delay parameter Pierre-Louis Bossart
2018-10-22 14:31 ` Pierre-Louis Bossart
2018-10-23 17:11 ` Tc, Jenny
2018-10-23 18:22 ` Pierre-Louis Bossart
2018-10-24 13:40 ` Mark Brown
2018-10-24 13:35 ` Mark Brown [this message]
2018-10-25 16:08 ` Vinod Koul
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=20181024133556.GR2103@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jenny.tc@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=mka@chromium.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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.