From: Mark Brown <broonie@kernel.org>
To: "Fischer, Christian" <fischerc@swissphone.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"richard.leitner@skidata.com" <richard.leitner@skidata.com>,
"fabio.estevam@nxp.com" <fabio.estevam@nxp.com>,
"bhumirks@gmail.com" <bhumirks@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AW: [PATCH] ASoC: sgtl5000: fix powerup/down of micbias-voltage
Date: Thu, 11 Jan 2018 16:19:47 +0000 [thread overview]
Message-ID: <20180111161947.GD7834@sirena.org.uk> (raw)
In-Reply-To: <DD64F087E8F0B540A1C9216D6716FFBDF9947CB6@defrsexc01.swissphone.de>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Thu, Jan 11, 2018 at 04:14:31PM +0000, Fischer, Christian wrote:
> Hi Mark,
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
> Testing:
> arecord -D "hw:0,1" -c 2 -f S16_LE -t wav test_recording.wav
> Recording WAVE 'test_recording.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Stereo
> ==> no event was fired
Has your board connected the bias to the microphone widget it defines?
Unless your board says that the bias is in use on a given board it won't
be enabled.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-01-11 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:40 [PATCH] ASoC: sgtl5000: fix powerup/down of micbias-voltage fischerc
2018-01-11 15:07 ` Mark Brown
2018-01-11 16:14 ` AW: " Fischer, Christian
2018-01-11 16:19 ` Mark Brown [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=20180111161947.GD7834@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bhumirks@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=fischerc@swissphone.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=richard.leitner@skidata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox