From: "Paller, Kim Seer" <KimSeer.Paller@analog.com>
To: Conor Dooley <conor+dt@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Jonathan Cameron <jic23@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"Nuno Sá" <noname.nuno@gmail.com>
Subject: RE: [PATCH v5 4/6] dt-bindings: iio: dac: Add adi,ltc2664.yaml
Date: Mon, 8 Jul 2024 05:55:05 +0000 [thread overview]
Message-ID: <PH0PR03MB7141B14FAC992C1BA0C95112F9DA2@PH0PR03MB7141.namprd03.prod.outlook.com> (raw)
In-Reply-To: <PH0PR03MB71417A3455B24590982C0716F9DE2@PH0PR03MB7141.namprd03.prod.outlook.com>
...
> > > + adi,manual-span-operation-config:
> > > + description:
> > > + This property must mimic the MSPAN pin configurations. By
> > > + tying the
> > MSPAN
> > > + pins (MSP2, MSP1 and MSP0) to GND and/or VCC, any output
> > > + range can
> > be
> > > + hardware-configured with different mid-scale or zero-scale
> > > + reset
> > options.
> > > + The hardware configuration is latched during power on reset for proper
> > > + operation.
> > > + 0 - MPS2=GND, MPS1=GND, MSP0=GND (+-10V, reset to 0V)
> > > + 1 - MPS2=GND, MPS1=GND, MSP0=VCC (+-5V, reset to 0V)
> > > + 2 - MPS2=GND, MPS1=VCC, MSP0=GND (+-2.5V, reset to 0V)
> > > + 3 - MPS2=GND, MPS1=VCC, MSP0=VCC (0V to 10, reset to 0V)
> > > + 4 - MPS2=VCC, MPS1=GND, MSP0=GND (0V to 10V, reset to 5V)
> > > + 5 - MPS2=VCC, MPS1=GND, MSP0=VCC (0V to 5V, reset to 0V)
> > > + 6 - MPS2=VCC, MPS1=VCC, MSP0=GND (0V to 5V, reset to 2.5V)
> > > + 7 - MPS2=VCC, MPS1=VCC, MSP0=VCC (0V to 5V, reset to 0V,
> > > + enables
> > SoftSpan)
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + enum: [0, 1, 2, 3, 4, 5, 6, 7]
> > > + default: 7
> > > +
> > > + io-channels:
> > > + description:
> > > + ADC channel to monitor voltages and temperature at the MUXOUT pin.
> > > + maxItems: 1
> > > +
> > > + '#address-cells':
> > > + const: 1
> > > +
> > > + '#size-cells':
> > > + const: 0
> > > +
> > > +patternProperties:
> > > + "^channel@[0-3]$":
> > > + $ref: dac.yaml
> > > + type: object
> > > + additionalProperties: false
> > > +
> > > + properties:
> > > + reg:
> > > + description: The channel number representing the DAC output
> channel.
> > > + maximum: 3
> > > +
> > > + adi,toggle-mode:
> > > + description:
> > > + Set the channel as a toggle enabled channel. Toggle operation
> enables
> > > + fast switching of a DAC output between two different DAC
> > > + codes
> > without
> > > + any SPI transaction.
> > > + type: boolean
> > > +
> > > + output-range-microvolt:
> >
> > Could be helpful to add a description that says this property is only
> > allowed when SoftSpan is enabled rather than requiring people to
> > reason through the logic.
> >
> > > + oneOf:
> > > + - items:
> > > + - const: 0
> > > + - enum: [5000000, 10000000]
> > > + - items:
> > > + - const: -5000000
> > > + - const: 5000000
> > > + - items:
> > > + - const: -10000000
> > > + - const: 10000000
> > > + - items:
> > > + - const: -2500000
> > > + - const: 2500000
> >
> > default: [0, 5000000]
>
> Adding a default value directly within the schema causes validation error.
> Given this, is it acceptable documenting the intended default value within the
> description?
Before sending the patch, I would like to confirm if it is acceptable to just
document the intended default value within the description, since adding a default
value directly to the schema causes validation error and considering adding the logic,
- if:
not:
properties:
adi,manual-span-operation-config:
const: 7
then:
patternProperties:
"^channel@[0-3]$":
properties:
output-range-microvolt: false
> >
> > > +
> > > + required:
> > > + - reg
> > > +
> > > + allOf:
> > > + - if:
> > > + properties:
> > > + adi,manual-span-operation-config:
> > > + const: 7
> > > + then:
> > > + patternProperties:
> > > + "^channel@[0-3]$":
> > > + required: [output-range-microvolt]
> >
> >
> > This logic doesn't look right to me. If
> > adi,manual-span-operation-config is not 7, then SoftSpan is disabled, so we
> should have:
> >
> > output-range-microvolt: false
> >
> > In that case since individual channels can't have a per-channel
> > configuration because SoftSpan is not enabled (unless I am
> > misunderstanding the datasheet?).
> >
> > Also, output-range-microvolt should never be required, even when
> > adi,manual-span-operation-config is 7 because there is already a
> > default value range (0V to 5V) specified by the
> > adi,manual-span-operation-config property.
> >
> > I think the correct logic would be:
> >
> > - if:
> > not:
> > properties:
> > adi,manual-span-operation-config:
> > const: 7
> > then:
> > patternProperties:
> > "^channel@[0-3]$":
> > properties:
> > output-range-microvolt: false
next prev parent reply other threads:[~2024-07-08 5:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 3:00 [PATCH v5 0/6] Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-07-02 3:00 ` [PATCH v5 1/6] iio: ABI: Generalize ABI documentation for DAC Kim Seer Paller
2024-07-02 3:00 ` [PATCH v5 2/6] iio: ABI: add DAC 42kohm_to_gnd powerdown mode Kim Seer Paller
2024-07-02 3:00 ` [PATCH v5 3/6] dt-bindings: iio: dac: Generalize DAC common properties Kim Seer Paller
2024-07-02 15:29 ` Conor Dooley
2024-07-03 5:11 ` Paller, Kim Seer
2024-07-02 3:00 ` [PATCH v5 4/6] dt-bindings: iio: dac: Add adi,ltc2664.yaml Kim Seer Paller
2024-07-02 15:08 ` Conor Dooley
2024-07-02 15:36 ` David Lechner
2024-07-04 7:01 ` Paller, Kim Seer
2024-07-08 5:55 ` Paller, Kim Seer [this message]
2024-07-02 3:00 ` [PATCH v5 5/6] dt-bindings: iio: dac: Add adi,ltc2672.yaml Kim Seer Paller
2024-07-02 15:05 ` Conor Dooley
2024-07-02 3:00 ` [PATCH v5 6/6] iio: dac: ltc2664: Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-07-07 16:21 ` Jonathan Cameron
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=PH0PR03MB7141B14FAC992C1BA0C95112F9DA2@PH0PR03MB7141.namprd03.prod.outlook.com \
--to=kimseer.paller@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®