From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Adds dB gain to alsa-driver, alsa-lib.
Date: Fri, 16 Dec 2005 10:49:01 +0000 [thread overview]
Message-ID: <1134730142.3137.17.camel@scooper.cruach> (raw)
In-Reply-To: <43A1C89D.90200@superbug.co.uk>
On Thu, 2005-12-15 at 19:48 +0000, James Courtier-Dutton wrote:
> Problems with your approach were:
> 1) Control with non-linear dB steps. E.g. attenuation using a different
> scale than gain.
In my experience, the majority of controls (certainly in the embedded
space) use a linear dB scale to adjust the gain/attenuation and would be
better served by a value rather than a hint. A hint would still be
required for the non linear controls.
How do you feel about adding a further field called db_hint. This way
the hint method could be used for the more complex and non linear
controls whilst the value method could be used for the simple ones.
This would save a lot effort, as driver developers wouldn't need to add
any hints to alsa-lib for simple controls.
> 2) Complicates controls where only a lookup table will do.
>
I agree, but with both fields this isn't an issue.
Further to this, I realised this code could also be used for other
controls that are unitised. i.e. some ALC controls use ms for timeouts.
This hint and scale could also be used to describe them.
Liam
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
prev parent reply other threads:[~2005-12-16 10:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 18:34 [PATCH] Adds dB gain to alsa-driver, alsa-lib James Courtier-Dutton
2005-12-15 18:58 ` Lee Revell
2005-12-15 19:06 ` James Courtier-Dutton
2005-12-15 19:16 ` Lee Revell
2005-12-15 19:13 ` Jaroslav Kysela
2005-12-15 19:45 ` James Courtier-Dutton
2005-12-16 10:27 ` Takashi Iwai
2005-12-16 10:47 ` James Courtier-Dutton
2005-12-16 12:05 ` Takashi Iwai
2005-12-16 12:14 ` Jaroslav Kysela
2005-12-16 12:43 ` James Courtier-Dutton
2005-12-16 13:27 ` Takashi Iwai
2005-12-16 13:47 ` James Courtier-Dutton
2005-12-16 14:11 ` Takashi Iwai
2005-12-16 14:11 ` Jaroslav Kysela
2005-12-16 14:55 ` Liam Girdwood
2005-12-16 11:09 ` Liam Girdwood
2005-12-16 12:37 ` Jaroslav Kysela
2005-12-16 13:08 ` James Courtier-Dutton
2005-12-16 14:05 ` Jaroslav Kysela
2005-12-16 14:24 ` Takashi Iwai
2005-12-15 19:32 ` Liam Girdwood
2005-12-15 19:48 ` James Courtier-Dutton
2005-12-16 10:49 ` Liam Girdwood [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=1134730142.3137.17.camel@scooper.cruach \
--to=liam.girdwood@wolfsonmicro.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.