Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Mert Seftali" <mertsftl@gmail.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jelle van der Waa" <jelle@vdwaa.nl>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE
Date: Sun, 12 Jul 2026 03:11:01 +0100	[thread overview]
Message-ID: <20260712031033.11639ec8@jic23-huawei> (raw)
In-Reply-To: <20260710105109.000047c5@gmail.com>

On Fri, 10 Jul 2026 10:51:09 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:

> On Fri, 10 Jul 2026 10:36:23 +0200
> Mert Seftali <mertsftl@gmail.com> wrote:
> 
> > Reading the in_accel_scale attribute on the DMARD09 has always returned
> > -EINVAL: the channels advertise scale via info_mask_shared_by_type so the
> > IIO core exposes the attribute, but dmard09_read_raw() only handles
> > IIO_CHAN_INFO_RAW, so a SCALE read falls through to 'default: return
> > -EINVAL':
> > 
> >     $ cat .../iio:deviceX/in_accel_scale
> >     cat: in_accel_scale: Invalid argument
> > 
> > leaving userspace with raw counts it cannot convert to m/s^2.
> > 
> > The driver was written from a vendor source [1] without a datasheet, and
> > the scale was declared but never implemented. The vendor source carries
> > the sensitivity: its conversion is
> > 
> >     acc = raw * GRAVITY_EARTH_1000 / sensitivity   (then / 1000 -> m/s^2)
> > 
> > with sensitivity = 32 and GRAVITY_EARTH_1000 = 9807 ("about
> > (9.80665)*1000"), i.e. 32 counts correspond to 1 g.
> > 
> > That sensitivity applies to the value this driver already reports as raw:
> > the vendor reduces each 16-bit sample to a signed 9-bit value, and the
> > preparation in dmard09_read_raw() yields the same value. It is
> > self-consistent: 256 counts / 32 = 8 g full scale, matching the +/-8g
> > range.
> > 
> > Implement the scale derived from that sensitivity using standard gravity:
> > 
> >     scale = 9.80665 / 32 = 0.3064578125 m/s^2 per LSB
> > 
> > Link: https://github.com/minstrelsy/mediatek/blob/1f49d8c87b839651bc89afc870277e8e0f2e2d55/custom/common/kernel/accelerometer/dmard09/dmard09.c [1]
> > Fixes: a4fa6509dda4 ("iio: accel: add support for the Domintech DMARD09 3-axis accelerometer")
> > Signed-off-by: Mert Seftali <mertsftl@gmail.com>
> > ---  
> 
> Good thing that Jelle sent the vendor driver, LGTM.
Indeed
> 
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
> 
Applied to the testing branch of iio.git.  It's been broken
from the start, so whilst it is a fix, I'm not rushing to get
it upstream!

Thanks,

Jonathan



      reply	other threads:[~2026-07-12  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  8:36 [PATCH v2] iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE Mert Seftali
2026-07-10  8:51 ` Joshua Crofts
2026-07-12  2:11   ` 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=20260712031033.11639ec8@jic23-huawei \
    --to=jonathan.cameron@oss.qualcomm.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jelle@vdwaa.nl \
    --cc=joshua.crofts1@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mertsftl@gmail.com \
    --cc=nuno.sa@analog.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