All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, ang.iglesiasg@gmail.com,
	linus.walleij@linaro.org, biju.das.jz@bp.renesas.com,
	javier.carrasco.cruz@gmail.com, semen.protsenko@linaro.org,
	579lpy@gmail.com, ak@it-klinger.de, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v6 1/4] iio: pressure: bmp280: Use sleep and forced mode for oneshot captures
Date: Fri, 13 Sep 2024 12:51:55 +0300	[thread overview]
Message-ID: <ZuQLOwjQUTjo1nPg@smile.fi.intel.com> (raw)
In-Reply-To: <20240912233234.45519-2-vassilisamir@gmail.com>

On Fri, Sep 13, 2024 at 01:32:31AM +0200, Vasileios Amoiridis wrote:
> Add forced mode support in sensors BMP28x, BME28x, BMP3xx and BMP58x.
> Sensors BMP18x and BMP085 are old and do not support this feature so
> their operation is not affected at all.
> 
> Essentially, up to now, the rest of the sensors were used in normal mode
> all the time. This means that they are continuously doing measurements
> even though these measurements are not used. Even though the sensor does
> provide PM support, to cover all the possible use cases, the sensor needs
> to go into sleep mode and wake up whenever necessary.
> 
> The idea is that the sensor is by default in sleep mode, wakes up in
> forced mode when a oneshot capture is requested, or in normal mode
> when the buffer is enabled. The difference lays in the fact that in
> forced mode, the sensor does only one conversion and goes back to sleep
> while in normal mode, the sensor does continuous measurements with the
> frequency that was set in the ODR registers.
> 
> The bmpX_chip_config() functions which are responsible for applying
> the requested configuration to the sensor, are modified accordingly
> in order to set the sensor by default in sleep mode.
> 
> DEEP STANDBY, Low Power NORMAL and CONTINUOUS modes, supported only by
> the BMP58x version, are not added.

...

> +	if (!((reg & BMP380_STATUS_DRDY_PRESS_MASK) &&
> +	    (reg & BMP380_STATUS_DRDY_TEMP_MASK))) {

I would add one more space to make the indentation follow the logic.

(no need to resend until Jonathan asks for it, otherwise I believe
 he can amend this whilst applying)

> +		dev_err(data->dev, "Measurement cycle didn't complete.\n");
> +		return -EBUSY;
> +	}

...

> +		/*
> +		 * According to the BMP3 Sensor API, the sensor needs 5000us

Can we use 5ms...

> +		 * in order to go to the sleep mode.
> +		 */
> +		fsleep(5000);

...and 5 * USEC_PER_MSEC here respectively?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-09-13  9:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 23:32 [PATCH v6 0/4] pressure: bmp280: Minor cleanup and interrupt support Vasileios Amoiridis
2024-09-12 23:32 ` [PATCH v6 1/4] iio: pressure: bmp280: Use sleep and forced mode for oneshot captures Vasileios Amoiridis
2024-09-13  9:51   ` Andy Shevchenko [this message]
2024-09-13 23:58     ` Vasileios Amoiridis
2024-09-12 23:32 ` [PATCH v6 2/4] dt-bindings: iio: pressure: bmp085: Add interrupts for BMP3xx and BMP5xx devices Vasileios Amoiridis
2024-09-13 18:27   ` Conor Dooley
2024-09-13 23:59     ` Vasileios Amoiridis
2024-09-14 22:24       ` Conor Dooley
2024-09-12 23:32 ` [PATCH v6 3/4] iio: pressure: bmp280: Add data ready trigger support Vasileios Amoiridis
2024-09-12 23:32 ` [PATCH v6 4/4] iio: pressure: bmp280: Move bmp085 interrupt to new configuration Vasileios Amoiridis
2024-09-13  9:54 ` [PATCH v6 0/4] pressure: bmp280: Minor cleanup and interrupt support Andy Shevchenko
2024-09-14  0:30   ` Vasileios Amoiridis

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=ZuQLOwjQUTjo1nPg@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=579lpy@gmail.com \
    --cc=ak@it-klinger.de \
    --cc=ang.iglesiasg@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=vassilisamir@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 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.