[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210221150907.2161b964@archlinux>
Date: Sun, 21 Feb 2021 15:09:07 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Ivan Mikhaylov <i.mikhaylov@...ro.com>
Cc: Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Rob Herring <robh+dt@...nel.org>, <linux-iio@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: vcnl3020: add proximity rate in hz
On Tue, 16 Feb 2021 17:53:46 +0300
Ivan Mikhaylov <i.mikhaylov@...ro.com> wrote:
> Describe the possible proximity values in herzes for vcnl3020.
Hertz
Why does this belong in DT?
DT bindings should reflect physical characteristics of the device, so how
is wired up, whether there are plastic windows over it that might affect
calibration - that sort of thing. A rate of sampling proximity seems
like a policy decision best left to user space.
Jonathan
>
> Signed-off-by: Ivan Mikhaylov <i.mikhaylov@...ro.com>
> ---
> .../devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml b/Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml
> index fbd3a2e32280..1bb6ca1770f3 100644
> --- a/Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml
> +++ b/Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml
> @@ -43,6 +43,12 @@ properties:
> 180000, 190000, 200000]
> default: 20000
>
> + vishay,proximity-rate-hz:
> + description:
> + The rate of proximity measurement.
> + enum: [1, 3, 7, 16, 31, 62, 125, 500]
> + default: 1
> +
> required:
> - compatible
> - reg
Powered by blists - more mailing lists