linux-kernel - Re: [PATCH] mfd: wm5102: Mark register 0x19 readable

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: <20140310171228.GR28112@sirena.org.uk>
Date:	Mon, 10 Mar 2014 17:12:28 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	Lee Jones <lee.jones@...aro.org>,
	patches@...nsource.wolfsonmicro.com,
	Samuel Ortiz <sameo@...ux.intel.com>,
	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: wm5102: Mark register 0x19 readable

On Mon, Mar 10, 2014 at 05:05:24PM +0000, Charles Keepax wrote:
> On Mon, Mar 10, 2014 at 04:49:04PM +0000, Mark Brown wrote:

> > It'd be nice but you'd need to ask the Wolfson guys to tell us what it's
> > called, all the information I have is the read in the driver source.
> > Meanwile we've got a bug.

> WRITE_SEQUENCER_CTRL_3, seems we should add that in since it is
> required for that 5102 boot stuff. Slightly confused as to how
> that ever worked without the register being readable, but guess
> it has been a while since I have fired up 5102 on mainline.

It just prints an error message, it doesn't actually care if the read
failed and will fall through to polling for boot completion.

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