All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [Alsa-user] Master volume control
Date: Thu, 14 Mar 2013 21:08:47 +0100	[thread overview]
Message-ID: <51422E4F.5090803@ladisch.de> (raw)
In-Reply-To: <1D8C99720146460FA33752A5FE614436@PAULD>

Paul D. DeRocco wrote:
>> I'd guess that some driver uses a busy loop for writing the codec
>> registers.
>>
>> Which drivers are you using for your sound hardware?
>
> It's Intel HD Audio.

That driver works fine.

> But the point is that three other processes light up when I move the slider.
> I think they're all monitoring the master volume changes, and not actually
> involved in doing the volume change.

I guess your CPU doesn't have too many cores ...

> What I'm wondering about these processes (pulseaudio, threaded-ml,
> indicator-sound)

PulseAudio has its own virtual volume sliders on top of the hardware
controls.  indicator-sound appears to be an OSD of your desktop
environment.  I don't know what threaded-ml is (maybe part of Chrome?).

> I would expect lots of CPU usage if I had alsamixer open at the time,
> because it monitors these changes, and updates its display.

Well, how much increas in CPU usage do you get wth alsamixer?

> * If I create my own minimal embedded distro (I'm trying to use the Yocto
> project for that), will they simply not be there

If you don't included the relevant packages.


Regards,
Clemens

      reply	other threads:[~2013-03-14 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B3AC1EE66F1142FF99DDC145B8669DDD@PAULD>
     [not found] ` <512F0AF5.3050502@googlemail.com>
2013-03-13 16:47   ` [Alsa-user] Master volume control Paul D. DeRocco
2013-03-13 17:11     ` Daniel Mack
2013-03-13 18:39       ` Paul D. DeRocco
2013-03-13 20:17     ` Paul D. DeRocco
2013-03-14 15:10     ` Clemens Ladisch
2013-03-14 16:38       ` Paul D. DeRocco
2013-03-14 20:08         ` Clemens Ladisch [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=51422E4F.5090803@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pderocco@ix.netcom.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.