public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergej Sawazki <ce3a@gmx.de>
To: Mark Brown <broonie@kernel.org>
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: Wed, 24 Jun 2015 22:49:59 +0200	[thread overview]
Message-ID: <558B17F7.8070401@gmx.de> (raw)
In-Reply-To: <20150615144933.GO18309@sirena.org.uk>

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

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.


  reply	other threads:[~2015-06-24 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 13:21 [BUG ?] regmap: debugfs: WARN_ON at regmap-debugfs.c:151 Sergej Sawazki
2015-06-15  9:49 ` Mark Brown
2015-06-15 12:42   ` Sergej Sawazki
2015-06-15 14:49     ` Mark Brown
2015-06-24 20:49       ` Sergej Sawazki [this message]
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=558B17F7.8070401@gmx.de \
    --to=ce3a@gmx.de \
    --cc=broonie@kernel.org \
    --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