linux-kernel - Re: [PATCH] mfd: arizona: Move chip reset to before register patch

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]

Date:	Wed, 14 Nov 2012 10:20:09 +0900
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	sameo@...ux.intel.com, patches@...nsource.wolfsonmicro.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: arizona: Move chip reset to before register patch

On Tue, Nov 13, 2012 at 01:12:19PM +0000, Charles Keepax wrote:
> On Tue, Nov 13, 2012 at 02:56:20PM +0900, Mark Brown wrote:

> > No, we should never write to the chip until we have successfully
> > identified it.  Do a sync or similar instead (we should be triggering
> > this very soon afterwards via runtime PM anyway).

> In that case I would be inclined to seperate out the chip
> identification and the register patch doing the reset in between.
> Is this something that would sound reasonable or would you rather
> just add a sync after the reset?

Just do a sync, make sure that we mark the map as dirty when we do the
reset via register write and it'll not have any effect anyway.  We
should also check if we've got the LDO and use that for reset too
actually...

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