From: Lars-Peter Clausen <lars@metafoo.de>
To: Bard Liao <bardliao.rtk@gmail.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Bard Liao <bardliao@realtek.com>,
Gustaw Lewandowski <gustaw.lewandowski@intel.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH v6] ASoC: add RT286 CODEC driver
Date: Mon, 12 May 2014 16:51:53 +0200 [thread overview]
Message-ID: <5370E009.5070503@metafoo.de> (raw)
In-Reply-To: <CAFOFQBaoYpXCfroxfZX+7yf-ua71dav5kfUytyJLzUs_FCMg8g@mail.gmail.com>
On 05/12/2014 01:08 PM, Bard Liao wrote:
> 2014-05-08 16:57 GMT+08:00 Lars-Peter Clausen <lars@metafoo.de>:
>> On 05/08/2014 10:00 AM, Mark Brown wrote:
>
> [...]
>
> Just for confirm.
> From the mail thread, what I need to to are:
> 1. Don't present register map to alsa, use virtrul controls instead.
> I may need to extend the APIs to accomplish the goal.
To avoid confusion we should not call them virtual controls, but controls
with custom put/get handlers.
> 2. I can (or should?) use regmap internal to codec driver to set the
> codec physically.
> Did I miss anything?
There are essentially two options.
a) Have custom put/get handlers for different types of verbs. This means
you'll re-implement things like caching.
b) Have a mapping that maps the hierarchical HDA register addressing
structure onto a linear address map and use regmap.
- Lars
next prev parent reply other threads:[~2014-05-12 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 5:59 [PATCH v6] ASoC: add RT286 CODEC driver bardliao
2014-04-15 12:04 ` Mark Brown
2014-04-16 13:26 ` Bard Liao
2014-04-16 21:11 ` Mark Brown
2014-04-17 5:39 ` Bard Liao
2014-04-18 10:37 ` Mark Brown
2014-05-06 12:04 ` Bard Liao
2014-05-07 17:21 ` Mark Brown
2014-05-07 17:46 ` Lars-Peter Clausen
2014-05-07 18:07 ` Mark Brown
2014-05-07 18:21 ` Lars-Peter Clausen
2014-05-07 19:49 ` Mark Brown
2014-05-08 7:05 ` Lars-Peter Clausen
2014-05-08 8:00 ` Mark Brown
2014-05-08 8:57 ` Lars-Peter Clausen
2014-05-12 11:08 ` Bard Liao
2014-05-12 14:51 ` Lars-Peter Clausen [this message]
2014-05-12 20:29 ` Mark Brown
2014-06-04 12:08 ` Bard Liao
2014-06-04 12:37 ` 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=5370E009.5070503@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao.rtk@gmail.com \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=flove@realtek.com \
--cc=gustaw.lewandowski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@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.