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: Tue, 7 Jul 2015 23:42:55 +0100	[thread overview]
Message-ID: <20150707224255.GK11162@sirena.org.uk> (raw)
In-Reply-To: <558B17F7.8070401@gmx.de>

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

On Wed, Jun 24, 2015 at 10:49:59PM +0200, Sergej Sawazki wrote:
> On Mon, 15 Jun 2015 15:49:33 +0100, Mark Brown wrote:

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

OK, so what we need to do here is rearrange things so we check the cache
before we check for readability.  That way if there is a cached value
then we'll return it and the readability check will still reflect the
hardware state.

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

      reply	other threads:[~2015-07-07 22:43 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
2015-06-24 20:49       ` Sergej Sawazki
2015-07-07 22:42         ` Mark Brown [this message]

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=20150707224255.GK11162@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®