From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Takashi Iwai <tiwai@suse.de>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Gustaw Lewandowski <gustaw.lewandowski@intel.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH v5] ASoC: add RT286 CODEC driver
Date: Fri, 14 Mar 2014 10:16:03 +0000 [thread overview]
Message-ID: <20140314101603.GQ366@sirena.org.uk> (raw)
In-Reply-To: <ABFD875FF5FB574BA706497D987D48D739CDD9@RTITMBSV03.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 518 bytes --]
On Fri, Mar 14, 2014 at 09:38:20AM +0000, Bard Liao wrote:
> What's your suggestion of the I/O part of rt286 codec driver?
> Can I keep using regmap without using its cache?
> Or it is better not using regmap in this driver?
I think we need to understand what the code is actually trying to do -
I'm intending to go through the driver today or before the weekend but
from the quick look at the I/O code I'm just really confused about what
is supposed to be happening. I'll try to follow up before Monday.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-03-14 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 7:11 [PATCH v5] ASoC: add RT286 CODEC driver bardliao
2014-03-12 21:15 ` Lars-Peter Clausen
2014-03-13 5:29 ` Bard Liao
2014-03-13 8:35 ` Lars-Peter Clausen
2014-03-13 8:52 ` Takashi Iwai
2014-03-13 19:29 ` Mark Brown
2014-03-13 20:04 ` Takashi Iwai
2014-03-13 20:43 ` Mark Brown
2014-03-14 9:38 ` Bard Liao
2014-03-14 10:16 ` Mark Brown [this message]
2014-03-14 19:12 ` Mark Brown
2014-03-18 12:41 ` Bard Liao
2014-03-18 13:01 ` Mark Brown
2014-03-21 5:57 ` Bard Liao
2014-03-21 12:12 ` 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=20140314101603.GQ366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=gustaw.lewandowski@intel.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=tiwai@suse.de \
/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.