linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, Michael.Hennerich@analog.com,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/6] SPI: add ability to say we want a cs change after every transfer.
Date: Wed, 07 Sep 2011 19:14:15 +0100	[thread overview]
Message-ID: <4E67B477.7060602@cam.ac.uk> (raw)
In-Reply-To: <20110907173515.GF2906@opensource.wolfsonmicro.com>

On 09/07/11 18:35, Mark Brown wrote:
> On Wed, Sep 07, 2011 at 05:19:42PM +0100, Jonathan Cameron wrote:
>> This allows a number of drivers to make use of utility functions
>> such spi_write_then_read as well as making use of regmap possible.
>>
>> Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
> 
> We could add this in regmap if required.
Makes more sense in spi and has been in their 'may be needed comment'
from the first.  Also, lots of other users who don't fit into regmap
(because they don't have any registers to speak of :)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E6600A8.4020101@cam.ac.uk>
     [not found] ` <20110906175435.GA2924@opensource.wolfsonmicro.com>
     [not found]   ` <Prayer.1.3.4.1109062213100.4243@hermes-2.csi.cam.ac.uk>
2011-09-07 16:10     ` Blockers on IIO usage of regmap 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 [this message]
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=4E67B477.7060602@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-iio@vger.kernel.org \
    --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).