mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ionut Nicu <ioan.nicu.ext@nsn.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] regmap: flat: use the cache_present bitmap
Date: Fri, 9 Aug 2013 12:44:26 +0100	[thread overview]
Message-ID: <20130809114426.GZ6427@sirena.org.uk> (raw)
In-Reply-To: <5204BFC7.4090106@nsn.com>

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

On Fri, Aug 09, 2013 at 12:09:11PM +0200, Ionut Nicu wrote:
> As opposed to the other regmap cache implementations,
> regcache_flat didn't use the cache_present bitmap for
> figuring out whether a register was cached or not, nor
> did it mark a register as present in the cache when
> regcache_flat_write() was called.

> This caused incorrect behaviour, such as returning
> value 0 for non-volatile registers without first reading
> their value from the device and storing it in the cache.

The goal with the flat cache is to do as little work as possible for
things like memory mapped devices where the cache operations are
actually noticable in comparison with the I/O costs.  I would therefore
exapect that anything using the flat cache would want to ensure that the
cache is fully populated at init time, reading back from the device if
nothing else (by setting num_reg_defaults_raw but not providing values),
rather than do additional operations in the data path.

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

  reply	other threads:[~2013-08-09 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 10:09 Ionut Nicu
2013-08-09 11:44 ` Mark Brown [this message]
2013-08-09 17:16   ` Ionut Nicu
2013-08-13  7:17     ` Ionut Nicu
2013-08-13 11:06       ` Mark Brown
     [not found]     ` <5211D68C.1070608@nsn.com>
2013-08-19 11:18       ` Fwd: " Alexander Sverdlin

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=20130809114426.GZ6427@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ioan.nicu.ext@nsn.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®