mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Sergej Sawazki <ce3a@gmx.de>
Cc: gregkh@linuxfoundation.org, wsa@the-dreams.de,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG ?] regmap: debugfs: WARN_ON at regmap-debugfs.c:151
Date: Mon, 15 Jun 2015 15:49:33 +0100	[thread overview]
Message-ID: <20150615144933.GO18309@sirena.org.uk> (raw)
In-Reply-To: <B1FC1740-086A-4869-9D97-88B0B742EDE8@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

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@kernel.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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-06-15 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 13:21 Sergej Sawazki
2015-06-15  9:49 ` Mark Brown
2015-06-15 12:42   ` Sergej Sawazki
2015-06-15 14:49     ` Mark Brown [this message]
2015-06-24 20:49       ` Sergej Sawazki
2015-07-07 22:42         ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150615144933.GO18309@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ce3a@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®