All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricard Wanderlof <ricard.wanderlof@axis.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Multiple codecs on the same DAI
Date: Wed, 6 Dec 2017 15:26:47 +0100	[thread overview]
Message-ID: <alpine.DEB.2.11.1712061521180.22247@lnxricardw1.se.axis.com> (raw)
In-Reply-To: <20171206130323.GG1827@finisterre>


On Wed, 6 Dec 2017, Mark Brown wrote:

> On Wed, Dec 06, 2017 at 01:54:38PM +0100, Ricard Wanderlof wrote:
> 
> > How about non-sound devices, for instance if there is a chip solely for 
> > managing the microphone power but it's not actually part of the codec. Is 
> > it reasonable to bring it in as an aux device too, even though there's 
> > actually no sound going through it?
> 
> That just sounds like a regulator?  I'd expect that just to be used as a
> supply as normal.

You mean as a DAPM widget?

>  What audio specific control would this device be provdiing?

What it does provide is current sensing if the connected device draws too 
much power, although it does not automatically shut off the connected 
device if that is the case, so a small driver is required to shut down the 
output in the case of overcurrent. There's also a requirement to be able 
to read the overcurrent status. One approach is to implementet the whole 
thing as an auxilliary device, with one ALSA control to control the power, 
and a read only control to read the overcurrent status.

So, no, it's not really audio specific, and furthermore it's not just 
providing a power output the way a regulator would.

It could of course be implemented as a completely separate device, but 
hardware wise it is still an integrated part of the audio solution.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

  reply	other threads:[~2017-12-06 14:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 14:51 Multiple codecs on the same DAI Ricard Wanderlof
2017-11-24 12:39 ` Mark Brown
2017-11-24 14:21   ` Ricard Wanderlof
2017-11-24 18:04     ` Mark Brown
2017-12-06 12:54       ` Ricard Wanderlof
2017-12-06 13:03         ` Mark Brown
2017-12-06 14:26           ` Ricard Wanderlof [this message]
2017-12-06 15:45             ` Mark Brown
2017-12-07  7:47               ` Ricard Wanderlof
2017-12-07 11:20                 ` Mark Brown
2017-12-07 11:31                   ` Ricard Wanderlof
2017-12-07 11:36                     ` 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=alpine.DEB.2.11.1712061521180.22247@lnxricardw1.se.axis.com \
    --to=ricard.wanderlof@axis.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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.