mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Daniel Mack <zonque@gmail.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, 6 May 2013 20:36:36 +0100	[thread overview]
Message-ID: <20130506193636.GE7478@sirena.org.uk> (raw)
In-Reply-To: <5187DB0C.2060605@gmail.com>

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

On Mon, May 06, 2013 at 06:32:12PM +0200, Daniel Mack wrote:
> On 17.02.2013 17:23, Mark Brown wrote:

> > 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?

There's just no attempt being made in regmap to cater for such devices.
I'm not sure it's worth bothering, sorry, though if you come up with a
non-intrusive way of handling such hardware of course it'd be worth
considering.

Using the no-bus support, having that take a lock and then bypassing it
completely to do the 20 byte writes would probably work.

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

      reply	other threads:[~2013-05-06 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16 17:03 Daniel Mack
2013-02-17 16:23 ` Mark Brown
2013-05-06 16:32   ` Daniel Mack
2013-05-06 19:36     ` 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=20130506193636.GE7478@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zonque@gmail.com \
    /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®