From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Cai, Cliff" <Cliff.Cai@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Drivers <Drivers@analog.com>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>,
Cliff Cai <cliff@analog.com>
Subject: Re: [PATCH RESEND v2]IIO driver for Analog Devices Digital Output Gyroscope ADXRS450
Date: Wed, 23 Mar 2011 11:10:57 +0000 [thread overview]
Message-ID: <4D89D541.8060303@cam.ac.uk> (raw)
In-Reply-To: <DB904C5425BA6F4E8424B3B51A1414D167E0335EA6@NWD2CMBX1.ad.analog.com>
...
>>> +}
>>> +
>> I note there are two versions of this chip (from datasheet).
>> We should probably support changing this axis according to
>> which one we have. Z is out of chip plane. The other two are
>> arbitrary if we only have 1 axis on the chip.
>
> Currently,I don't know the way to tell what kind package the device has.
> So,just keep the Z-axis one.
>
Fine. Only way I can think of doing it would be to use an id_table
and rely on the board file being correct. I guess this is a feature
someone can add when they want it!
As an aside: It is really helpful if you crop the text when responding
to a particular point in an email - keeps a particular branch of a thread
focussed and easy to follow.
Jonathan
...
prev parent reply other threads:[~2011-03-23 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 9:27 [PATCH RESEND v2]IIO driver for Analog Devices Digital Output Gyroscope ADXRS450 cliff.cai
2011-03-21 17:40 ` Jonathan Cameron
2011-03-21 17:40 ` Jonathan Cameron
2011-03-22 7:29 ` Cai, Cliff
2011-03-22 7:29 ` Cai, Cliff
2011-03-22 8:16 ` Hennerich, Michael
2011-03-22 8:16 ` Hennerich, Michael
2011-03-22 10:42 ` Jonathan Cameron
2011-03-22 10:42 ` Jonathan Cameron
2011-03-23 9:34 ` Hennerich, Michael
2011-03-23 9:34 ` Hennerich, Michael
2011-03-23 10:22 ` Cai, Cliff
2011-03-23 10:22 ` Cai, Cliff
2011-03-23 11:10 ` Jonathan Cameron [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=4D89D541.8060303@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Cliff.Cai@analog.com \
--cc=Drivers@analog.com \
--cc=cliff@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--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.