From: Conor Dooley <conor@kernel.org>
To: Andreas Klinger <ak@it-klinger.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Petre Rodan <petre.rodan@subdimension.ro>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: honeywell,mprls0025pa.yaml: fix function numbering
Date: Thu, 16 Nov 2023 18:34:16 +0000 [thread overview]
Message-ID: <20231116-grudge-hankering-b7a71d831b93@squawk> (raw)
In-Reply-To: <20231116182443.7290-1-ak@it-klinger.de>
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
On Thu, Nov 16, 2023 at 07:24:43PM +0100, Andreas Klinger wrote:
> Fix wrongly documented numbering of transfer functions.
>
> Fixes: a765c985e696 ("dt-bindings: iio: pressure: Support Honeywell mprls0025pa sensor")
>
No blank line here.
> Suggested-by: Petre Rodan <petre.rodan@subdimension.ro>
This should be Reported-by.
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>
> ---
> .../bindings/iio/pressure/honeywell,mprls0025pa.yaml | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml b/Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml
> index b31f8120f14e..61775eff1128 100644
> --- a/Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml
> +++ b/Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml
> @@ -64,9 +64,9 @@ properties:
> description: |
> Transfer function which defines the range of valid values delivered by the
> sensor.
> - 1 - A, 10% to 90% of 2^24 (1677722 .. 15099494)
> - 2 - B, 2.5% to 22.5% of 2^24 (419430 .. 3774874)
> - 3 - C, 20% to 80% of 2^24 (3355443 .. 13421773)
> + 0 - A, 10% to 90% of 2^24 (1677722 .. 15099494)
> + 1 - B, 2.5% to 22.5% of 2^24 (419430 .. 3774874)
> + 2 - C, 20% to 80% of 2^24 (3355443 .. 13421773)
I don't understand. These are arbitrary numbers in a dt-binding, why
does zero or one indexing make any difference here?
Can't you just fix up the driver to correctly map the dt-binding to
whatever needs to be written to registers in the hardware?
Cheers,
Conor.
> $ref: /schemas/types.yaml#/definitions/uint32
>
> vdd-supply:
> --
> 2.39.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-11-16 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 18:24 [PATCH] iio: honeywell,mprls0025pa.yaml: fix function numbering Andreas Klinger
2023-11-16 18:34 ` Conor Dooley [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=20231116-grudge-hankering-b7a71d831b93@squawk \
--to=conor@kernel.org \
--cc=ak@it-klinger.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petre.rodan@subdimension.ro \
--cc=robh+dt@kernel.org \
/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