From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regmap cached only when write happen to register
Date: Mon, 14 May 2012 17:47:46 +0100 [thread overview]
Message-ID: <20120514164746.GD25668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FB135BB.2020001@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
On Mon, May 14, 2012 at 10:11:31PM +0530, Laxman Dewangan wrote:
> When debugging on register caching, found that register is getting
> cached only when write happen to the register otherwise it will not
> get cached even any number of read happen.
> Is it by intended or there is opportunity to enhance it so that
> during read also we can cache it.\?
If you check -next you should find that the current code already caches
any single register read.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-14 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:41 Regmap cached only when write happen to register Laxman Dewangan
2012-05-14 16:47 ` 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=20120514164746.GD25668@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.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;
as well as URLs for NNTP newsgroup(s).