public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Subject: Re: regmap: Question about devices with unequal register sizes
Date: Mon, 06 May 2013 18:32:12 +0200	[thread overview]
Message-ID: <5187DB0C.2060605@gmail.com> (raw)
In-Reply-To: <20130217162337.GB1583@opensource.wolfsonmicro.com>

On 17.02.2013 17:23, Mark Brown wrote:
> On Sat, Feb 16, 2013 at 06:03:51PM +0100, Daniel Mack wrote:
> 
>> The register layout is described on page 26, and they call their
>> registers 'subaddresses'. Up to sub-address 0x1c, I see no problem
>> mapping that to a simple 8-bit regmap layout, but above that, access
>> gets trickier because registers change their sizes, which breaks the cache.
> 
> The regmap I/O code isn't making any effort to support such devices, the
> hardware is just too crazy to worry about.  The best you can do is use
> the no-bus support and open code your physical I/O so you can still use
> the cache.

So it turns out I need to write these registers now on the TAS5086
codec, which has such a strange layout. I wonder how I can possibly open
code the physical I/O with registers that are up to 20 bytes in size,
while the reg_write callback in struct regmap_config assumes an unsigned
int suffices for the data? Any example you can point me to?


Thanks,
Daniel


  reply	other threads:[~2013-05-06 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16 17:03 regmap: Question about devices with unequal register sizes Daniel Mack
2013-02-17 16:23 ` Mark Brown
2013-05-06 16:32   ` Daniel Mack [this message]
2013-05-06 19:36     ` 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=5187DB0C.2060605@gmail.com \
    --to=zonque@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dp@opensource.wolfsonmicro.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