From: Mark Brown <broonie@kernel.org>
To: Chih-Chiang Chang <ccchang12@nuvoton.com>
Cc: "mcuos.com@gmail.com" <mcuos.com@gmail.com>,
"tiwai@suse.de" <tiwai@suse.de>,
AP MS30 Linux ALSA <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
AP MS30 Linux Kernel community <linux-kernel@vger.kernel.org>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH] ASoC: Add support for NAU8824 codec to ASoC
Date: Thu, 26 Mar 2015 17:28:01 -0700 [thread overview]
Message-ID: <20150327002801.GA3572@sirena.org.uk> (raw)
In-Reply-To: <5514811D.1060901@nuvoton.com>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On Thu, Mar 26, 2015 at 02:58:53PM -0700, Chih-Chiang Chang wrote:
> On 3/6/2015 1:07 PM, Mark Brown wrote:
> > On Fri, Mar 06, 2015 at 03:28:33PM +0800, Chih-Chiang Chang wrote:
> > Please fix your mailer to word wrap within paragraphs, it makes things a
> > lot easier to read.
> This seems to violate the kernel's rule. I am using the Thunderbird to
> do upstream. And in kernel's documentation, it shows we should set
> "mailnews.wraplength" from "72" to "0". Any way, for your convenience, I
> already modify the "mailnews.wraplength" back to "72".
You should never word wrap code since that corrupts the patches but
always word wrap text.
> > I'd really like to have a better understanding of what this is doing -
> > it can be valid to do this but there are some warning signs here such as
> > the volume of writes being large in comparison with the set of controls
> > the driver exposes which mean I'd like to be sure the use matches
> > expectations. Normally this sort of thing is a small number of fixes
> > for undocumented registers or updates to register defaults changed in
> > later revisions of the chip.
> We have tried to reduce the sequence recently, but it got some issues in
> the tests. We think these large number of register settings are
> necessary to our NAU8824 codec. We will provide the comments of all
> values in source to have a better understanding, is it acceptable to you?
It sounds reasonable but obviously I've not seen the results yet.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-03-27 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 7:49 [PATCH] ASoC: Add support for NAU8824 codec to ASoC Wan Zongshun
2015-02-24 14:13 ` Mark Brown
2015-03-04 12:35 ` Chih-Chiang Chang
2015-03-04 12:55 ` Mark Brown
2015-03-06 7:28 ` Chih-Chiang Chang
2015-03-06 21:07 ` Mark Brown
2015-03-26 21:58 ` Chih-Chiang Chang
2015-03-27 0:28 ` Mark Brown [this message]
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=20150327002801.GA3572@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ccchang12@nuvoton.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuos.com@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox