From: Mark Brown <broonie@kernel.org>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using regmap_update_bits to update a write only register
Date: Fri, 6 Mar 2015 11:21:42 +0000 [thread overview]
Message-ID: <20150306112142.GG21293@sirena.org.uk> (raw)
In-Reply-To: <CAEnQRZCb0k7_W1gt7qCTqbQqDwzJ_bJkDYS1FHthKTA8sP19Qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Thu, Mar 05, 2015 at 08:14:14PM +0200, Daniel Baluta wrote:
> On Mar 5, 2015 7:54 PM, "Mark Brown" <broonie@kernel.org> wrote:
> > Probably, or there's a bug. What should happen is that if the register
> > default appeared successfully then the read will get statisfied from the
> > cache in the manner you describe - presumably that's gone wrong somehow.
> > Have you set num_reg_defaults? That's the obvious thing...
> Did that. I will have a closer look. Thanks for the answer.
OK, the other thing that springs to mind to check is that the register
didn't somehow get marked as volatile.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-06 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:35 Daniel Baluta
2015-03-05 17:53 ` Mark Brown
[not found] ` <CAEnQRZCb0k7_W1gt7qCTqbQqDwzJ_bJkDYS1FHthKTA8sP19Qg@mail.gmail.com>
2015-03-06 11:21 ` Mark Brown [this message]
2015-03-06 12:45 ` Lars-Peter Clausen
2015-03-06 13:27 ` Daniel Baluta
2015-03-06 17:26 ` Daniel Baluta
2015-03-06 17:36 ` Lars-Peter Clausen
2015-03-06 17:39 ` Lars-Peter Clausen
2015-03-06 19:48 ` Daniel Baluta
2015-03-07 11:06 ` Mark Brown
2015-03-07 16:07 ` Lars-Peter Clausen
2015-03-07 11:05 ` 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=20150306112142.GG21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®