public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Blockers on IIO usage of regmap.
Date: Tue, 06 Sep 2011 12:14:48 +0100	[thread overview]
Message-ID: <4E6600A8.4020101@cam.ac.uk> (raw)

Hi Mark,

Just a quick heads up that the big blocker for
us making more use of regmap is lack of default
control of cs_change for spi buses.  That leads to
a lot of hand crafted spi read / write routines and
is rather tedious.

When I have the time I'll look into sorting that side
out.

Also, we will need a couple of variants of bulk read for
spi. Classic ones are 

TX  Add0...Add7 XXXXXXXXXXX  XXXXXXXXXXX  XXXXXXXX
RX  XXXXXXXXXXX Da0.....Da7  Db0.....Db7  etc

TX  Add0...Add7 XXXXXXXXXXX  XXXXXXXXXXX  XXXXXXXXXX
RX  XXXXXXXXXXX XXXXXXXXXXX  Da0.....Da7  Db0....Db7

TX  Ada0...Ada7  Adb1...Adb7 Adc1...Adc7  etc
RX  XXXXXXXXXXX  Da0.....Da7 Db0.....Db7  etc

Last one is a kind of 'simulated' bulk read where address is simply incremented
(just for complexity that increment may well be by 2 rather than one...)
That one is only sort of a 'bulk' read, but rather common.

So basically we need some bus specific 'mode' hook somewhere.
Given we have separate init functions for the buses could we
add a struct regmap_spi_config to the parameter list?

IIRC IIO has several drivers in each of the above categories so sharing
the code via regmap would be great!

What do you think?

Jonathan

             reply	other threads:[~2011-09-06 11:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 11:14 Jonathan Cameron [this message]
2011-09-06 11:32 ` Blockers on IIO usage of regmap Jonathan Cameron
2011-09-06 17:54 ` Mark Brown
2011-09-06 21:13   ` J.I. Cameron
2011-09-07 16:10     ` Jonathan Cameron
2011-09-07 16:19       ` [RFC PATCH 0/6] Using regmap with ADIS devices Jonathan Cameron
2011-09-07 16:19       ` [PATCH 1/6] SPI: add ability to say we want a cs change after every transfer Jonathan Cameron
2011-09-07 17:35         ` Mark Brown
2011-09-07 18:14           ` Jonathan Cameron
2011-09-07 18:12             ` Mark Brown
2011-09-07 18:28               ` Jonathan Cameron
2011-09-07 16:19       ` [PATCH 2/6] regmap: Add a magic bus type to handle quirks of analog devices ADIS sensors Jonathan Cameron
2011-09-07 17:47         ` Mark Brown
2011-09-07 18:26           ` Jonathan Cameron
2011-09-07 18:32             ` Mark Brown
2011-09-07 18:50               ` Jonathan Cameron
2011-09-07 18:44                 ` Mark Brown
2011-09-07 19:14                   ` Jonathan Cameron
2011-09-07 16:19       ` [PATCH 3/6] staging:iio:imu: adis16400 partial conversion to regmap Jonathan Cameron
2011-09-07 16:23         ` Jonathan Cameron
2011-09-07 16:19       ` [PATCH 4/6] regmap-spi-adi + staging:iio:imu:adis16400 halve register addresses Jonathan Cameron
2011-09-07 16:19       ` [PATCH 5/6] regmap-spi-adi generalize regmap_spi_read Jonathan Cameron
2011-09-07 16:19       ` [PATCH 6/6] staging:iio:imu:adis16400 make use of regmap bulk read capabilities Jonathan Cameron
2011-09-07 17:57       ` Blockers on IIO usage of regmap Mark Brown
2011-09-07 18:12         ` Jonathan Cameron

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=4E6600A8.4020101@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=broonie@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