[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241012130124.44c69521@jic23-huawei>
Date: Sat, 12 Oct 2024 13:01:24 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: vamoirid <vassilisamir@...il.com>
Cc: lars@...afoo.de, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, anshulusr@...il.com, gustavograzs@...il.com,
andriy.shevchenko@...ux.intel.com, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 09/13] iio: chemical: bme680: Move ambient
temperature to attributes
On Thu, 10 Oct 2024 23:00:26 +0200
vamoirid <vassilisamir@...il.com> wrote:
> From: Vasileios Amoiridis <vassilisamir@...il.com>
>
> Remove the ambient temperature from being a macro and implement it as
> an attribute. This way, it is possible to dynamically configure the
> ambient temperature of the environment to improve the accuracy of the
> measurements.
>
> Signed-off-by: Vasileios Amoiridis <vassilisamir@...il.com>
New ABI? Would need docs.
However, I 'think' we have a few cases where we handle this via the slightly
odd interface of out_temp_processed / _raw with a label saying it's
ambient temperature.
The tenuous argument is that we have heaters that actually control the
temperature and the affect of either heating the thing or just happening
to know the external temperature ends up being the same. Hence use
an output channel for this control.
Jonathan
Powered by blists - more mailing lists