Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221103094436.2136698-1-demonsingur@gmail.com>
 <20221103094436.2136698-2-demonsingur@gmail.com> <20221106154634.2286faf3@jic23-huawei>
 <c01b0e56563b2b6f8ef48ad90977646706a2c933.camel@gmail.com>
 <20221112154040.54dc5cf2@jic23-huawei> <c54200fb70d638c572a0596a78d956d9f61d89a4.camel@gmail.com>
 <20221115160724.00007460@Huawei.com>
In-Reply-To: <20221115160724.00007460@Huawei.com>
From:   Rob Herring <robh+dt@kernel.org>
Date:   Tue, 15 Nov 2022 12:16:41 -0600
Message-ID: <CAL_JsqLt6B73XSE8dMHMGuw1N9m1v1xwr3sOEEHonGgLAYya=A@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: addac: add AD74115
To:     Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc:     Cosmin Tanislav <demonsingur@gmail.com>,
        Jonathan Cameron <jic23@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Cosmin Tanislav <cosmin.tanislav@analog.com>,
        Lars-Peter Clausen <lars@metafoo.de>,
        Michael Hennerich <Michael.Hennerich@analog.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        William Breathitt Gray <william.gray@linaro.org>,
        linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Nov 15, 2022 at 10:07 AM Jonathan Cameron
<Jonathan.Cameron@huawei.com> wrote:
>
> On Tue, 15 Nov 2022 14:43:53 +0200
> Cosmin Tanislav <demonsingur@gmail.com> wrote:
>
> > On Sat, 2022-11-12 at 15:40 +0000, Jonathan Cameron wrote:
> > > > >
> > > > > > +    $ref: /schemas/types.yaml#/definitions/uint32
> > > > > > +    description: |
> > > > > > +      Conversion range for ADC conversion 2.
> > > > > > +      0 - 0V to 12V
> > > > > > +      1 - -12V to +12V
> > > > > > +      2 - -2.5V to +2.5V
> > > > > > +      3 - -2.5V to 0V
> > > > > > +      4 - 0V to 2.5V
> > > > > > +      5 - 0V to 0.625V
> > > > > > +      6 - -104mV to +104mV
> > > > > > +      7 - 0V to 12V
> > > > >
> > > > > For a lot of similar cases we handle these numerically to give
> > > > > a human readable dts.  Is there a strong reason not to do so here (in mv)
> > > > >
> > > >
> > > > I used this approach mostly because it maps dirrectly to register values
> > > > and because it's easier to parse. dts isn't exactly nice at handling
> > > > negative values. I can switch it to mv array if you insist.
> > >
> > > We have quite a few existing cases of
> > > adi,[output-]range-microvolt so it would be good to copy that style here.
> > >
> >
> > With this:
> >
> >   adi,conv2-range-microvolt:
> >     description: Conversion range for ADC conversion 2.
> >     oneOf:
> >       - items:
> >           - enum: [-2500000, 0]
> >           - const: 2500000
> >       - items:
> >           - enum: [-12000000, 0]
> >           - const: 12000000
> >       - items:
> >           - const: -2500000
> >           - const: 0
> >       - items:
> >           - const: -104000
> >           - const: 104000
> >       - items:
> >           - const: 0
> >           - const: 625000
> >
> > And this:
> >
> > adi,conv2-range-microvolt = <(-12000000) 12000000>;
> >
> > I get this:
> >
> > Documentation/devicetree/bindings/iio/addac/adi,ad74115.example.dtb:
> > addac@0: adi,conv2-range-microvolt: 'oneOf' conditional failed,
> > one must be fixed:
> >         4282967296 is not one of [-2500000, 0]
> >         4282967296 is not one of [-12000000, 0]
> >         -2500000 was expected
> >         -104000 was expected
> >         625000 was expected
> >         From schema: Documentation/devicetree/bindings/iio/addac/adi,ad74115.yaml
> >
> > As I said, negative numbers don't play too nice...
>
> From what I recall we just ignore those warnings :)
>
> Rob, do I remember correctly that there was a plan to make this work longer term?

Yes, but handling signed types is working now (since the move to
validating dtbs directly).

The issue here is -microvolt is defined as unsigned. IIRC, I had some
issue changing it, but I think that was just with the YAML encoding
which I intend to remove. I'll give it another look and update the
type if there's no issues.

Rob