public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: jic23@kernel.org, nvaccaro@google.com, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: cros_ec: Allow enabling/disabling calibration mode
Date: Wed, 21 Jan 2026 10:15:52 +0000	[thread overview]
Message-ID: <aXCnWIkTLauLbBKa@google.com> (raw)
In-Reply-To: <20260119074928.1334489-1-gwendal@chromium.org>

On Sun, Jan 18, 2026 at 11:49:28PM -0800, Gwendal Grignou wrote:
> calibration was a one-shot event sent to the sensor to calibrate itself.
  ^ C

> It is used on Bosch sensors (BMI160, BMA254).
> For light sensor, we need to stay in calibration mode to run tests.
> Accept boolean true and false (not just true) to enter/exit calibration.
> 
> Check "echo 0 > calibrate" is supported.

I can somehow understand because the patch is small.  But I believe the
commit message should be rephrased.  For example, if we only need to "stay"
in calibration mode to run tests, why do we need to add the patch for
disabling calibration?

> diff --git a/include/linux/platform_data/cros_ec_commands.h b/include/linux/platform_data/cros_ec_commands.h
> index 69294f79cc88a..d363d60bb8a36 100644
> --- a/include/linux/platform_data/cros_ec_commands.h
> +++ b/include/linux/platform_data/cros_ec_commands.h
> @@ -2598,13 +2598,19 @@ struct ec_params_motion_sense {
>  
>  		/*
>  		 * Used for MOTIONSENSE_CMD_INFO, MOTIONSENSE_CMD_DATA
> -		 * and MOTIONSENSE_CMD_PERFORM_CALIB.

Missed a period here but that's also what current ec_commands.h [1] has.
It should be fine.

[1] https://chromium.googlesource.com/chromiumos/platform/ec/+/refs/heads/main/include/ec_commands.h#3158

  reply	other threads:[~2026-01-21 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19  7:49 [PATCH] iio: cros_ec: Allow enabling/disabling calibration mode Gwendal Grignou
2026-01-21 10:15 ` Tzung-Bi Shih [this message]
2026-01-22 19:43 ` 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=aXCnWIkTLauLbBKa@google.com \
    --to=tzungbi@kernel.org \
    --cc=gwendal@chromium.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nvaccaro@google.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