linux-kernel - Re: [BUG ?] regmap: debugfs: WARN

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <558B17F7.8070401@gmx.de>
Date:	Wed, 24 Jun 2015 22:49:59 +0200
From:	Sergej Sawazki <ce3a@....de>
To:	Mark Brown <broonie@...nel.org>
CC:	gregkh@...uxfoundation.org, wsa@...-dreams.de,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG ?] regmap: debugfs: WARN_ON at regmap-debugfs.c:151

On Mon, 15 Jun 2015 15:49:33 +0100, Mark Brown wrote:
> On Mon, Jun 15, 2015 at 02:42:30PM +0200, Sergej Sawazki wrote:
>> Am 15. Juni 2015 11:49:22 MESZ, schrieb Mark Brown <broonie@...nel.org>:
>
>>> We need to change that code to special case write only register maps
>>> like this and just skip having a cache for those devices.  They
>>> normally
>>> have very small register maps anyway so it shouldn't have too big an
>>> impact on performance.
>
>> I'm having this issue with a wm8741 DAC, its register map is not
>> "write only", it has readable and writeable registers.
>
> Are you *sure* there are physically readable registers on the device?
> It's difficult to implement for 7x9 devices given that the top register
> bit is in the byte used to send the register address, I expect you'll
> find that the registers marked as readable are actually those that
> should be cached.
>

You are right, the registers are not physically readable. Sorry for the
confusion.

What I actually was trying to do is to read the cached register values.

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