From alsa-devel-owner@alsa.jcu.cz  Fri Aug 21 13:17:36 1998
Received: from ife.ee.ethz.ch (ife-fast.ee.ethz.ch [129.132.24.193])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id NAA14962
	for <alsa-devel@jcu.cz>; Fri, 21 Aug 1998 13:16:54 +0200
Received: from ife.ee.ethz.ch (eldrich.ee.ethz.ch [129.132.24.203])
	by ife.ee.ethz.ch (8.8.5/8.8.5) with ESMTP id NAA25479
	for <alsa-devel@jcu.cz>; Fri, 21 Aug 1998 13:16:54 +0200 (MET DST)
Message-ID: <35DD5726.64DA8B1D@ife.ee.ethz.ch>
Date: Fri, 21 Aug 1998 13:16:54 +0200
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
MIME-Version: 1.0
To: alsa-devel@jcu.cz
Subject: Re: Detecting ADC Overload
References: <Pine.LNX.3.96.980820194827.231A-100000@phoenix.kawo2.rwth-aachen.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Maximilian Bisani wrote:

>  - Is there a better way to detect ADC overloading, than looking for
>    peak values?

Some codec chips (for example AD184x, CS423x) have a separate overload
bit (which is even somewhat sticky, AFAIR), but I don't know if
ALSA propagates this to user land...

Tom

