On 09/04/2018 09:57 AM, Mark Brown wrote: > 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. > I don't see that happening for any other user of this, we will still have to re-write the cache when the device goes from OFF->STANDBY, and if it stays in standby and never went off, then we are still broken as we switched to using the register cache only, but never turned on real writes again. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
