Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Krzysztof Helt <krzysztof.h1@gmail.com>,
	Alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] cs4231: remove two auto-calibrations during chip initialization
Date: Tue, 18 Sep 2007 13:26:49 +0200	[thread overview]
Message-ID: <46EFB5F9.4090909@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0709181305130.8148@tm8103.perex-int.cz>

On 09/18/2007 01:08 PM, Jaroslav Kysela wrote:

> On Tue, 18 Sep 2007, Rene Herman wrote:
> 
>> On 09/18/2007 12:17 PM, Krzysztof Helt wrote:
>>
>>> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>>>
>>> The initialization function did auto-calibration after each
>>> register setting. This patch merges more register changes
>>> before auto-calibration is done.
>> Seems to make sense but am a little uneasy about these -- someone very much
>> did it this way on purpose originally it seems. Jaroslav, that someone was you
>> I believe? Do you remember anything about this?
> 
> If I remember correctly, it was workaround for some CS4231 chips to fix 
> the noise audio issue (the chip was not initialized correctly in some 
> cases). I would make a whitelist for "non-buggy" tested chips to skip 
> double calibration.

Okay thanks. For reference, I have:

AD1848
AD1848KP
AD1845JP
AD1845XP
AD1846JP

CS4248-KL
CS4231
CS4231A-KL
CS4232-KQ
CS4235-XQ3
CS4236B-KQ
CS4237B-XQ3
CS4239-KQ

(Won't be testing right now, but will be generally available).

Rene.

      reply	other threads:[~2007-09-18 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 10:17 [PATCH] cs4231: remove two auto-calibrations during chip initialization Krzysztof Helt
2007-09-18 10:38 ` Rene Herman
2007-09-18 11:08   ` Jaroslav Kysela
2007-09-18 11:26     ` Rene Herman [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=46EFB5F9.4090909@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@gmail.com \
    --cc=perex@suse.cz \
    /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