linux-kernel - Re: [alsa-devel] [PATCH v6] sound/soc/codecs: add LAPIS Semiconductor ML26124

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120314174518.GV3133@opensource.wolfsonmicro.com>
Date:	Wed, 14 Mar 2012 17:45:18 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Tomoya MORINAGA <tomoya.rohm@...il.com>,
	alsa-devel@...a-project.org, qi.wang@...el.com,
	Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
	yong.y.wang@...el.com, kok.howg.ewe@...el.com,
	Liam Girdwood <lrg@...com>, joel.clark@...el.com
Subject: Re: [alsa-devel] [PATCH v6] sound/soc/codecs: add LAPIS
 Semiconductor ML26124

On Wed, Mar 14, 2012 at 06:40:20PM +0100, Lars-Peter Clausen wrote:

> If this is for all registers, how does stuff like DAPM work, which uses the
> framework internal update_bits function?

I was assuming that this was just for specific registers which were
weird (frankly I've no idea what the chip designers were thinking if
this is actually needed).

Though based on some of the issues I found on previous versions there's
every chance that there's not been any testing...  if that's the case
it's possible this is a misunderstanding of the I2C read/write handling
with the chip address?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)