From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>, Linux-ALSA <alsa-devel@alsa-project.org>, devicetree@vger.kernel.org Subject: Re: [PATCH] ASoC: dt-bindings: renesas: adjust to R-Car Gen4 Date: Mon, 6 Feb 2023 02:41:17 +0000 [thread overview] Message-ID: <87k00vqzw2.wl-kuninori.morimoto.gx@renesas.com> (raw) In-Reply-To: <46974ae7-5f7f-8fc1-4ea8-fe77b58f5bfb@linaro.org> Hi Krzysztof Thank you for your review > This does not make sense - you just require it always. (snip) > Please do not embed if within another if, unless strictly necessary. It > gets unmanageable. (snip) > minItems (snip) > Drop OK, thanks. Will fix in v2 > > The "required" with if - then - else on "rcar_sound,ssi" is > > always match to "then" even though it is checking "renesas,rcar_sound-gen4" or not. > > Why ?? Is it my fault ?? I'm not sure why but some "if - then - else" doesn't work correctly for me. One concern is that it is under "patternProperties". Non "patternProperties" case is works well. This is just sample case. In below case, only gen4 case requires "foo/bar" if my understanding was correct. But I get error "foo/bar are required" on *all* compatible. It is my fault ? --- sample ----------- rcar_sound,ssi: ... patternProperties: "^ssi-[0-9]$": ... allOf: - if: properties: compatible: contains: => const: renesas,rcar_sound-gen4 then: required: => - foo => - bar ----------------------- Thank you for your help !! Best regards --- Kuninori Morimoto
WARNING: multiple messages have this Message-ID (diff)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: Rob Herring <robh@kernel.org>, Linux-ALSA <alsa-devel@alsa-project.org>, Mark Brown <broonie@kernel.org>, devicetree@vger.kernel.org Subject: Re: [PATCH] ASoC: dt-bindings: renesas: adjust to R-Car Gen4 Date: Mon, 6 Feb 2023 02:41:17 +0000 [thread overview] Message-ID: <87k00vqzw2.wl-kuninori.morimoto.gx@renesas.com> (raw) In-Reply-To: <46974ae7-5f7f-8fc1-4ea8-fe77b58f5bfb@linaro.org> Hi Krzysztof Thank you for your review > This does not make sense - you just require it always. (snip) > Please do not embed if within another if, unless strictly necessary. It > gets unmanageable. (snip) > minItems (snip) > Drop OK, thanks. Will fix in v2 > > The "required" with if - then - else on "rcar_sound,ssi" is > > always match to "then" even though it is checking "renesas,rcar_sound-gen4" or not. > > Why ?? Is it my fault ?? I'm not sure why but some "if - then - else" doesn't work correctly for me. One concern is that it is under "patternProperties". Non "patternProperties" case is works well. This is just sample case. In below case, only gen4 case requires "foo/bar" if my understanding was correct. But I get error "foo/bar are required" on *all* compatible. It is my fault ? --- sample ----------- rcar_sound,ssi: ... patternProperties: "^ssi-[0-9]$": ... allOf: - if: properties: compatible: contains: => const: renesas,rcar_sound-gen4 then: required: => - foo => - bar ----------------------- Thank you for your help !! Best regards --- Kuninori Morimoto
next prev parent reply other threads:[~2023-02-06 2:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 1:22 [PATCH] ASoC: dt-bindings: renesas: adjust to R-Car Gen4 Kuninori Morimoto 2023-02-03 1:22 ` Kuninori Morimoto 2023-02-03 9:09 ` Krzysztof Kozlowski 2023-02-03 9:09 ` Krzysztof Kozlowski 2023-02-06 2:41 ` Kuninori Morimoto [this message] 2023-02-06 2:41 ` Kuninori Morimoto 2023-02-06 6:49 ` Geert Uytterhoeven 2023-02-06 6:49 ` Geert Uytterhoeven 2023-02-07 0:56 ` Kuninori Morimoto 2023-02-07 0:56 ` Kuninori Morimoto
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=87k00vqzw2.wl-kuninori.morimoto.gx@renesas.com \ --to=kuninori.morimoto.gx@renesas.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski@linaro.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.