From: nicoleotsuka@gmail.com (Nicolin Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6qdl-sabresd.dtsi: Fix the microphone route
Date: Thu, 6 Nov 2014 20:47:34 -0800 [thread overview]
Message-ID: <20141107044733.GA31643@Alpha> (raw)
In-Reply-To: <CAOMZO5ChyTM2_AnSCbi3R9QXzrCYix_wFHP-5FA-6baBSXVgsA@mail.gmail.com>
On Wed, Nov 05, 2014 at 10:16:40AM -0200, Fabio Estevam wrote:
> On Tue, Nov 4, 2014 at 11:08 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > On Tue, Nov 04, 2014 at 10:56:09AM -0200, Fabio Estevam wrote:
> >> Since commit e409dfbfccf9a49 ("ASoC: dapm: Add a few supply widget sanity
> >> checks") the following error is seen:
> >>
> >> imx-wm8962 sound: wm8962 <-> 202c000.ssi mapping ok
> >> imx-wm8962 sound: Connecting non-supply widget to supply widget is not supported (AMIC -> MICBIAS)
> >> imx-wm8962 sound: ASoC: no dapm match for AMIC --> (null) --> MICBIAS
> >> imx-wm8962 sound: ASoC: Failed to add route AMIC -> direct -> MICBIAS
> >
> > Any regression behind that error message?
>
> Playback works fine, but I am having issues with arecord with or
> without this patch, so I haven't seen any regression.
>
> Will investigate the arecord problem I am having (maybe it is a
> alsamixer config issue).
I just took a test on imx6sx-sdb with the identical AMIC route
as SabreSD does, but the microphone actually still works even
if the same link error occurs.
So I think the error doesn't break the function on Sabre SD
either...and the reason should be the dts connecting 'IN3R'
directly to MICBIAS, which isn't so accurate.
For the patch, I think the configuration on imx6sx-sdb would
be better.
120 "AMIC", "MICBIAS",
121 "IN3R", "AMIC";
Thanks
Nicolin
prev parent reply other threads:[~2014-11-07 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 12:56 [PATCH] ARM: dts: imx6qdl-sabresd.dtsi: Fix the microphone route Fabio Estevam
2014-11-04 13:08 ` Shawn Guo
2014-11-05 12:16 ` Fabio Estevam
2014-11-07 4:47 ` Nicolin Chen [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=20141107044733.GA31643@Alpha \
--to=nicoleotsuka@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).