linux-kernel - Re: [PATCH] ASoC: tlv320aic31xx: Remove regulator notification handling

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: <20180904145740.GE12993@sirena.org.uk>
Date:   Tue, 4 Sep 2018 15:57:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     "Andrew F. Davis" <afd@...com>
Cc:     Liam Girdwood <lgirdwood@...il.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: tlv320aic31xx: Remove regulator notification
 handling

On Tue, Sep 04, 2018 at 09:50:50AM -0500, Andrew F. Davis wrote:
> On 09/03/2018 06:30 AM, Mark Brown wrote:
> > On Fri, Aug 31, 2018 at 01:17:37PM -0500, Andrew F. Davis wrote:
> >> The notification handler sets the reset line but never re-enables it
> >> as no one is listening for an enable event, this is certainly broken
> >> and was most likely just copied from other CODECs, remove this code.

> > Why not fix it?  The usual pattern would be to take the CODEC out of
> > reset when bringing the bias back to standby.

> The only time this code gets called outside of the normal power on/off
> path is regulator_force_disable(). And the enable event is only called
> inside regulator_enable() which would already be part of the normal
> power up path.

It's there to save us having to rewrite the register cache if we asked
for the device to be powered down but that didn't actually happen due to
other constraints, we know all the registers are still as we left them.

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