From: Felipe Balbi <balbi@ti.com>
To: Andreas Werner <andy@wernerandy.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: regmap different register size
Date: Tue, 26 May 2015 14:00:39 -0500 [thread overview]
Message-ID: <20150526190039.GX26599@saruman.tx.rr.com> (raw)
In-Reply-To: <20150526185425.GA26217@wernerandy.de>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi,
On Tue, May 26, 2015 at 08:54:25PM +0200, Andreas Werner wrote:
> i have a question regarding regmap usage.
>
> I have a i2c multifunction device which does have a register and value
> width of 8bits except the revision register. The revision can only be
> read by a i2c block transfer.
read revision during probe using i2c block transfer, cache the value in
your own driver structure and all subsequent reads just return the
cached value. Everything else should be ok via regmap. This is first
thing that came to mind, maybe there's a better way.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-26 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 18:54 regmap different register size Andreas Werner
2015-05-26 19:00 ` Felipe Balbi [this message]
2015-05-26 19:27 ` Andreas Werner
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=20150526190039.GX26599@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=andy@wernerandy.de \
--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