linux-kernel - Re: [RFC][PATCH] ASoC: Suppress restore of default register values for lzo cache sync

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: <20111013105747.GE5193@opensource.wolfsonmicro.com>
Date:	Thu, 13 Oct 2011 11:57:48 +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>,
	alsa-devel@...a-project.org
Subject: Re: [RFC][PATCH] ASoC: Suppress restore of default register values
 for lzo cache sync

On Thu, Oct 13, 2011 at 05:28:33PM +0800, Axel Lin wrote:
> Currently we do suppress restore of default register values for rbtree
> and flat cache sync.
> A couple users use this trick to avoid writing reset register while resume.
> Thus make lzo cache sync suppress restore of default register values,
> so we have consistent behavior for all types of cache sync.

Given that we never acquired any in tree users for the LZO cache it'd
probably be as well to just work on the regmap version and deprecate
this one - there's no users to move over and it'll save effort.
--
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/