From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 7/8] ASoC: codecs: Add AB8500 codec-driver
Date: Fri, 27 Apr 2012 12:11:24 +0100 [thread overview]
Message-ID: <20120427111123.GD18260@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F9A7B03.5040802@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 1526 bytes --]
On Fri, Apr 27, 2012 at 12:54:59PM +0200, Ola Lilja wrote:
> On 04/27/2012 11:35 AM, Mark Brown wrote:
> > What are these regulators? Are they internal PGA supplies or are they
> > microphone biases?
> These are mic-biases.
OK, then why aren't they hooked up in the board anyway (probably fixed to
a specific configuration there, though there are some use cases for
changing)? This is what other CODEC drivers do with their MICBIASes...
> > Normally the clocking control is under the control of the machine driver
> > and if the machine driver wants to offer any options to userspace it'd
> > provide its own control - usually there's way more stuff going on here
> > than just selecting a source and much more coordination needed with the
> > drivers involved.
> Yes, we are only selecting what clock to request to the clock-driver-code, which
> then does its magic and taking decisions related to the whole platform.
> More specifically, in my context (that is audio) we will act upon being in
> voicecall or not, and in these cases requesting these two different clocks. By
> design this request comes from audio-code in userspace down to the audio-driver
> in the kernel. The clock-code will then turn of the clock not needed by us
> (audio) or any other party.
So what one would expect there would be that the machine driver would
figure things out - usually for something like the voice call case the
machine driver would be doing something like switching to the voice call
clock when the baseband DAI comes up.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-04-27 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334914402-27554-1-git-send-email-ola.o.lilja@stericsson.com>
2012-04-23 18:59 ` [PATCH 7/8] ASoC: codecs: Add AB8500 codec-driver Mark Brown
2012-04-27 9:19 ` Ola Lilja
2012-04-27 9:35 ` Mark Brown
2012-04-27 10:54 ` Ola Lilja
2012-04-27 11:11 ` Mark Brown [this message]
2012-04-30 8:50 ` Ola Lilja
2012-04-30 9:56 ` Mark Brown
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=20120427111123.GD18260@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.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;
as well as URLs for NNTP newsgroup(s).