From: anish kumar <yesanishhere@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: Add max98371 codec driver
Date: Mon, 18 Apr 2016 13:20:35 -0700 [thread overview]
Message-ID: <CABCoZhDLyT_2xMhOqkiw5+9rOtA9FUqcvxy+1Pz=2QohAZEcHA@mail.gmail.com> (raw)
In-Reply-To: <20160418164727.GI3217@sirena.org.uk>
On Mon, Apr 18, 2016 at 9:47 AM, Mark Brown <broonie@kernel.org> wrote:
> On Wed, Apr 13, 2016 at 01:20:47PM -0700, anish kumar wrote:
>
>> +static const char *const voltage_level_text[] = {
>> + "9.5dB", "10.5dB", "11.5dB", "11.5dB", "12.5dB",
>> + "13.5dB", "14.5dB", "15.5dB", "16.5dB", "17.5dB",
>> + "18.5dB", "19.5dB", "20.5dB"
>> +};
>
> As I said last time I would expect this to be a TLV control. As far as
> I can tell this is basically functioning as a maximum volume. Otherwise
> this looks good.
I responded to your comment earlier but there was no reply so I thought
it is accepted this way. Excuse my understanding. It is not actually a volume
but described as such.
It is "Speaker No-Load Output Voltage Maximum". It is
described here on page 50.
https://datasheets.maximintegrated.com/en/ds/MAX98371.pdf
next prev parent reply other threads:[~2016-04-18 20:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 20:20 [PATCH] ASoC: Add max98371 codec driver anish kumar
2016-04-18 16:47 ` Mark Brown
2016-04-18 20:20 ` anish kumar [this message]
2016-04-19 9:46 ` Mark Brown
2016-04-20 18:14 ` anish kumar
2016-04-22 15:31 ` Mark Brown
2016-04-26 18:16 ` anish kumar
2016-04-27 16:42 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2016-04-27 22:39 anish kumar
2016-03-22 6:53 anish kumar
2016-03-28 19:13 ` Mark Brown
2016-04-07 19:34 ` anish kumar
2016-04-08 3:09 ` Lars-Peter Clausen
2016-04-08 20:04 ` anish kumar
2016-04-10 18:04 ` Mark Brown
2016-03-21 1:59 anish kumar
2016-03-21 14:56 ` Mark Brown
2016-03-21 15:29 ` Micka
2016-03-21 15:56 ` Mark Brown
2016-03-21 16:41 ` Micka
2016-03-21 17:05 ` Mark Brown
2016-03-23 12:45 ` Micka
2016-03-23 16:23 ` Amish Kumar
2016-03-24 10:49 ` Micka
2016-03-24 11:05 ` Mark Brown
2016-03-24 11:19 ` Micka
2016-03-24 11:21 ` 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='CABCoZhDLyT_2xMhOqkiw5+9rOtA9FUqcvxy+1Pz=2QohAZEcHA@mail.gmail.com' \
--to=yesanishhere@gmail.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.