From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Blockers on IIO usage of regmap.
Date: Wed, 7 Sep 2011 10:57:56 -0700 [thread overview]
Message-ID: <20110907175756.GH2906@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E679770.4090008@cam.ac.uk>
On Wed, Sep 07, 2011 at 05:10:24PM +0100, Jonathan Cameron wrote:
Please fix your mailer to word wrap at less than 80 colums, they're
really quite hard to read as a result of this.
> CS -_______________________-
> TX Ada0...Ada7 Da0....Da7
> RX XXXXXXXXXXXXXXXXXXXXXXXXX
>
> Reads are 16 bit with either of the two 8 bit register addresses given the same value
>
> CS -______________________-_____________________-
> TX Ada0....Ada7 XXXXXXXX
> RX XXXXXXXXXXXXXXXXXXXXX Da0...Da7 Db0....Db7
> Can interpret Da0...Da7 and Db0....Db7 as single 16 bit register and consider this device
> to just have a weird write method and normal read. Might be easier. I'll define Ax<n> as
> 16 bit address for the burst read.
This is starting to seem pretty far off the reservation.
> Perhaps the burst mode thing is better handled by just providing a hook to allow data to be pushed
> into regmap (from 'magic' sources), but the weird write read combination looks to me like something
> that makes sense to have in regmap (be it as another bus variant).
Probably not as a bus, it sounds like a marshalling difference rather
than a bus - the buses should really only understand byte streams. I
don't have any bright ideas on how to deal with this, it's fairly far
away from the problem space I'm worried about.
next prev parent reply other threads:[~2011-09-07 17:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 11:14 Blockers on IIO usage of regmap Jonathan Cameron
2011-09-06 11:32 ` 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 ` Mark Brown [this message]
2011-09-07 18:12 ` Blockers on IIO usage of regmap 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=20110907175756.GH2906@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.