From: Mark Brown <broonie@kernel.org>
To: srinivas.kandagatla@linaro.org
Cc: Banajit Goswami <bgoswami@codeaurora.org>,
alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Patrick Lai <plai@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ASoC: codecs: msm8916-wcd-digital: select DMIC source in CIC filter path
Date: Fri, 28 Jul 2017 14:32:06 +0100 [thread overview]
Message-ID: <20170728133206.7ynzrbfvreclltkx@sirena.org.uk> (raw)
In-Reply-To: <20170725234822.18763-4-srinivas.kandagatla@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
On Wed, Jul 26, 2017 at 01:48:22AM +0200, srinivas.kandagatla@linaro.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>
> This patch fixes a missing selection of DMIC in CIC filter source path.
> Without this patch dmic is not functional.
What happens when someone needs this filter connected somewhere else -
shouldn't this be controlled as part of the DAPM routing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2017-07-28 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 23:48 [PATCH v2 0/3] ASoC: codecs: msm8916-wcd-digital: Fix dmic support srinivas.kandagatla
2017-07-25 23:48 ` [PATCH v2 1/3] ASoC: codecs: msm8916-wcd-digital: add support to set_sysclk srinivas.kandagatla
2017-08-02 17:29 ` Applied "ASoC: codecs: msm8916-wcd-digital: add support to set_sysclk" to the asoc tree Mark Brown
2017-08-02 17:30 ` Mark Brown
2017-07-25 23:48 ` [PATCH v2 2/3] ASoC: qcom: apq8016-sbc: set default mclk rate srinivas.kandagatla
2017-08-02 17:29 ` Applied "ASoC: qcom: apq8016-sbc: set default mclk rate" to the asoc tree Mark Brown
2017-07-25 23:48 ` [PATCH v2 3/3] ASoC: codecs: msm8916-wcd-digital: select DMIC source in CIC filter path srinivas.kandagatla
2017-07-28 13:32 ` Mark Brown [this message]
2017-07-28 15:11 ` Srinivas Kandagatla
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=20170728133206.7ynzrbfvreclltkx@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®