public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nishant Malpani <nish.malpani25@gmail.com>
Cc: dragos.bogdan@analog.com, darius.berghe@analog.com,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: gyro: Add driver support for ADXRS290
Date: Sun, 26 Jul 2020 13:46:13 +0100	[thread overview]
Message-ID: <20200726134613.6c483a81@archlinux> (raw)
In-Reply-To: <91b82340-832c-6e02-c595-613322926337@gmail.com>

On Wed, 22 Jul 2020 00:25:48 +0530
Nishant Malpani <nish.malpani25@gmail.com> wrote:

> Hello Jonathan,
> 
> Thanks a lot for the detailed review. Comments inline...
> 
...
> 
> >>> +#define ADXRS290_REG_SN0	0x04 /* Serial Number Registers, 4 bytes */
> >>> +#define ADXRS290_REG_DATAX0	0x08 /* Roll Rate o/p Data Regs, 2 bytes */
> >>> +#define ADXRS290_REG_DATAY0	0x0A /* Pitch Rate o/p Data Regs, 2 bytes */  
> > 
> > Are we actually right to map roll and pitch to x and y?
> > If so we should probably add that to the docs somewhere.  We need to document
> > which one maps to x and which to y as that mapping is far from obvious!
> >   
> "The ADXRS290 is an x-axis and y-axis rate sensing device that
> is also called a roll and pitch rate sensing device" (datasheet pg. 4). 
> I think I'm right in marking the DATA X-axis register as the roll rate 
> and similarly the DATA Y-axis register as the pitch rate.
> 
> Also, I thought it is a known convention to use x for roll, y for pitch, 
> etc. [2]. But you're right, its not very obvious. Where do I document it?
> 
> [2] https://en.wikipedia.org/wiki/Aircraft_principal_axes#Principal_axes

Documentation/ABI/testing/sysfs-bus-iio


Thanks,

Jonathan


      reply	other threads:[~2020-07-26 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  9:27 [PATCH 1/2] iio: gyro: Add driver support for ADXRS290 Nishant Malpani
2020-07-15  9:50 ` Nishant Malpani
2020-07-20 11:13   ` Jonathan Cameron
2020-07-21 18:55     ` Nishant Malpani
2020-07-26 12:46       ` 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=20200726134613.6c483a81@archlinux \
    --to=jic23@kernel.org \
    --cc=darius.berghe@analog.com \
    --cc=dragos.bogdan@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nish.malpani25@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