From: Mark Brown <broonie@kernel.org>
To: Cheng-yi Chiang <cychiang@chromium.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>
Subject: Re: [alsa-devel] [PATCH] ASoC: rt1011: export r0 and temperature config
Date: Tue, 8 Oct 2019 12:06:43 +0100 [thread overview]
Message-ID: <20191008110643.GD4382@sirena.co.uk> (raw)
In-Reply-To: <CAFv8NwJ+g+ESJJ5JxaLHADhBASKsjTE7pqY=HhcZZcT2Yy+Ygw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]
On Tue, Oct 08, 2019 at 06:59:57PM +0800, Cheng-yi Chiang wrote:
> 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
So the VPD is not part of the CODEC? One question would be why the
CODEC driver doesn't directly read this information.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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:07 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
2019-10-08 11:06 ` Mark Brown [this message]
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=20191008110643.GD4382@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cychiang@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox