From: Jonathan Cameron <jic23@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] doc: iio: Document intensity scale as poorly defined
Date: Sun, 10 Dec 2023 11:58:50 +0000 [thread overview]
Message-ID: <20231210115850.63717a3d@jic23-huawei> (raw)
In-Reply-To: <20231207134200.329174-1-marex@denx.de>
On Thu, 7 Dec 2023 14:41:50 +0100
Marek Vasut <marex@denx.de> wrote:
> Add comment about intensity scale being poorly defined and
> having no proper units.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Applied. Thanks for cleaning this up.
Jonathan
> ---
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: linux-iio@vger.kernel.org
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 0d3ec5fc45f2f..94b8d8461b7c7 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -618,7 +618,9 @@ KernelVersion: 2.6.35
> Contact: linux-iio@vger.kernel.org
> Description:
> If a discrete set of scale values is available, they
> - are listed in this attribute.
> + are listed in this attribute. Unlike illumination,
> + multiplying intensity by intensity_scale does not
> + yield value with any standardized unit.
>
> What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
> What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain
next prev parent reply other threads:[~2023-12-10 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 13:41 [PATCH] doc: iio: Document intensity scale as poorly defined Marek Vasut
2023-12-10 11:58 ` Jonathan Cameron [this message]
2023-12-10 15:29 ` Marek Vasut
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=20231210115850.63717a3d@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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