From: Mark Brown <broonie@kernel.org>
To: anish kumar <yesanishhere@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: Add max98371 codec driver
Date: Tue, 19 Apr 2016 10:46:29 +0100 [thread overview]
Message-ID: <20160419094629.GP3217@sirena.org.uk> (raw)
In-Reply-To: <CABCoZhDLyT_2xMhOqkiw5+9rOtA9FUqcvxy+1Pz=2QohAZEcHA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
On Mon, Apr 18, 2016 at 01:20:35PM -0700, anish kumar wrote:
> On Mon, Apr 18, 2016 at 9:47 AM, Mark Brown <broonie@kernel.org> wrote:
> > 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.
If it's measured in dB I'd still expect a TLV control.
> It is "Speaker No-Load Output Voltage Maximum". It is
> described here on page 50.
> https://datasheets.maximintegrated.com/en/ds/MAX98371.pdf
Hrm, that looks like the driver may be able to set it automatically
using the regulator API and just have a switch for the guaranteed.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-04-19 9:46 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
2016-04-19 9:46 ` Mark Brown [this message]
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=20160419094629.GP3217@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=yesanishhere@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.