From: Dan Murphy <dmurphy@ti.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: [RFC] Volume control across multiple registers
Date: Wed, 19 Feb 2020 15:11:47 -0600 [thread overview]
Message-ID: <2f74b971-4a6a-016f-8121-4da941eeccef@ti.com> (raw)
In-Reply-To: <20200219134622.22066-1-dmurphy@ti.com>
Hello!
I am trying to figure out how to control the volume of a speaker device
with full volume control spread out across 4 8bit registers.
The standard TLV calls only allow a single register for volume control.
But I have 4 I need to touch to get a full range of volume from 0dB to
-110dB.
I was looking at using the DAPM calls and use PGA_E and define an event
but there really is no good way to get the current volume setting.
I don't see any example of this in any current driver.
Any guidance is appreciated.
Dan
WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [RFC] Volume control across multiple registers
Date: Wed, 19 Feb 2020 15:11:47 -0600 [thread overview]
Message-ID: <2f74b971-4a6a-016f-8121-4da941eeccef@ti.com> (raw)
In-Reply-To: <20200219134622.22066-1-dmurphy@ti.com>
Hello!
I am trying to figure out how to control the volume of a speaker device
with full volume control spread out across 4 8bit registers.
The standard TLV calls only allow a single register for volume control.
But I have 4 I need to touch to get a full range of volume from 0dB to
-110dB.
I was looking at using the DAPM calls and use PGA_E and define an event
but there really is no good way to get the current volume setting.
I don't see any example of this in any current driver.
Any guidance is appreciated.
Dan
next prev parent reply other threads:[~2020-02-19 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 13:46 [PATCH] ASoC: tas2562: Add support for ISENSE and VSENSE Dan Murphy
2020-02-19 13:46 ` Dan Murphy
2020-02-19 20:57 ` Applied "ASoC: tas2562: Add support for ISENSE and VSENSE" to the asoc tree Mark Brown
2020-02-19 20:57 ` Mark Brown
2020-02-19 21:11 ` Dan Murphy [this message]
2020-02-19 21:11 ` [RFC] Volume control across multiple registers Dan Murphy
2020-02-20 11:59 ` Mark Brown
2020-02-20 11:59 ` 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=2f74b971-4a6a-016f-8121-4da941eeccef@ti.com \
--to=dmurphy@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 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.