linux-kernel - Re: [PATCH] ASoC: sta32x: Write the register default value to cache for reserved registers

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] [day] [month] [year] [list]

Message-ID: <20111013105158.GD5193@opensource.wolfsonmicro.com>
Date:	Thu, 13 Oct 2011 11:51:58 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Axel Lin <axel.lin@...il.com>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Johannes Stezenbach <js@...21.net>, alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: sta32x: Write the register default value to cache
 for reserved registers

On Thu, Oct 13, 2011 at 02:57:31PM +0800, Axel Lin wrote:
> Chip documentation explicitly requires that the reset values
> of reserved register bits are left untouched.

Applied, but this seems really wierd - shouldn't we just be getting this
stuff from the cache defaults?  Why do we explicitly need to write to
the cache?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/