On 10/05/2023 10:29, Martin Povišer wrote:
On 10. 5. 2023, at 10:23, Krzysztof Kozlowski krzysztof.kozlowski@linaro.org wrote:
On 10/05/2023 10:15, Martin Povišer wrote:
On 10. 5. 2023, at 9:51, Krzysztof Kozlowski krzysztof.kozlowski@linaro.org wrote:
On 09/05/2023 18:38, Martin Povišer wrote:
Add a DT schema for the SSM3515 amp by Analog Devices. It's a simple mono amplifier with digital input.
Signed-off-by: Martin Povišer povik+lin@cutebit.org
+additionalProperties: true
uinevaluatedProperties: false instead, so users can have name-prefix.
I actually tweaked this to have the example passing, which has sound-name-prefix,
true is not allowed anyway - it makes your schema simply not effective almost at all as it allows anything...
That makes sense.
which I guess is what you have in mind. Not that I exactly understand what these options do (both additionalProperties and unevaluatedProperties), the schema docs didn’t enlighten me right away when I looked into it.
The way to go and to start always is to look at example-schema. It tells you explicitly to use additionalProperties:false and switch to unevaluated "If and only if another schema is referenced".
OK. While I have you on the line, what does unevaluated do? In what sense are props unevaluated?
Properties can be evaluated by some other referenced schema (e.g. dai-common.yaml). If nothing evaluated them, they are unevaluated, thus unknown and not allowed.
Best regards, Krzysztof