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: <20140310170524.GN8570@opensource.wolfsonmicro.com>
Date:	Mon, 10 Mar 2014 17:05:24 +0000
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	Mark Brown <broonie@...nel.org>
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 04:49:04PM +0000, Mark Brown wrote:
> On Mon, Mar 10, 2014 at 04:38:11PM +0000, Lee Jones wrote:
> 
> > Can we have a #define for these please?
> 
> 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.

Thanks,
Charles


--
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/