From: Cheng-yi Chiang <cychiang@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Derek [方德義]" <derek.fang@realtek.com>,
"Shuming [范書銘]" <shumingf@realtek.com>,
"Flove(HsinFu)" <flove@realtek.com>,
"Cheng-Yi Chiang" <cychiang@chromium.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: rt1011: export r0 and temperature config
Date: Tue, 8 Oct 2019 18:59:57 +0800 [thread overview]
Message-ID: <CAFv8NwJ+g+ESJJ5JxaLHADhBASKsjTE7pqY=HhcZZcT2Yy+Ygw@mail.gmail.com> (raw)
In-Reply-To: <20191008105138.GC4382@sirena.co.uk>
On Tue, Oct 8, 2019 at 6:51 PM Mark Brown <broonie@kernel.org> wrote:
>
> On Tue, Oct 08, 2019 at 09:33:24AM +0000, Shuming [范書銘] wrote:
>
> > In chromebook case, the machine driver will get the
> > r0 calibration data and temperature from VPD.
> > Therefore, the codec exports r0 and temperature config API for it.
>
> Why will the machine driver do this?
Hi Mark,
The calibration data (R0 values and temperature) were measured and
written to VPD in the factory. When machine driver initializes sound
card, it reads the value from VPD and uses the exported API to set
calibration value for codec. The purpose is to protect speaker. This
needs to be done before sound card is initialized. If, alternatively,
this process is done in user space through mixer control after the
sound card is initialized, user space may use audio before calibration
is done, and this will allow the possibility to damage speakers.
Hope this clarifies the intention of this patch.
Thanks!
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-08 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 9:33 [alsa-devel] [PATCH] ASoC: rt1011: export r0 and temperature config Shuming [范書銘]
2019-10-08 10:51 ` Mark Brown
2019-10-08 10:59 ` Cheng-yi Chiang [this message]
2019-10-08 11:06 ` Mark Brown
2019-10-08 11:22 ` Cheng-yi Chiang
2019-10-08 12:38 ` Mark Brown
2019-10-14 3:28 ` Cheng-yi Chiang
2019-10-10 14:20 ` Mark Brown
2019-10-14 1:46 ` Shuming [范書銘]
2019-10-14 2:47 ` Jimmy Cheng-Yi Chiang
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='CAFv8NwJ+g+ESJJ5JxaLHADhBASKsjTE7pqY=HhcZZcT2Yy+Ygw@mail.gmail.com' \
--to=cychiang@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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.