From: zhiyong.tao <zhiyong.tao@mediatek.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: alexandre.belloni@bootlin.com, allen-kh.cheng@mediatek.com, linux-kernel@vger.kernel.org, macpaul.lin@mediatek.com, lee.jones@linaro.org, hsin-hsiung.wang@mediatek.com, linux-rtc@vger.kernel.org, wen.su@mediatek.com, Project_Global_Chrome_Upstream_Group@mediatek.com, devicetree@vger.kernel.org, sean.wang@mediatek.com, hui.liu@mediatek.com, robh+dt@kernel.org, linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com, eddie.huang@mediatek.com, linux-arm-kernel@lists.infradead.org, a.zummo@towertech.it, sen.chu@mediatek.com, lgirdwood@gmail.com, broonie@kernel.org Subject: Re: [PATCH v3 1/1] regulator: dt-bindings: mediatek: add mt6366 Date: Tue, 16 Aug 2022 20:54:31 +0800 [thread overview] Message-ID: <9bc148119fc36c34f404091ca0f5a2e37727c285.camel@mediatek.com> (raw) In-Reply-To: <CAGE=qrohYZ6f9bbEuYfF=2Rz21nbW_8ho3rBQmHt1D+kQG2-jA@mail.gmail.com> On Fri, 2022-08-12 at 15:55 +0300, Krzysztof Kozlowski wrote: > On Fri, 12 Aug 2022 at 15:52, zhiyong.tao <zhiyong.tao@mediatek.com> > wrote: > > > > On Fri, 2022-08-12 at 13:55 +0300, Krzysztof Kozlowski wrote: > > > On 12/08/2022 12:29, Zhiyong Tao wrote: > > > > Add mt6366 regulator document > > > > > > > > + > > > > +properties: > > > > + compatible: > > > > + const: mediatek,mt6366-regulator > > > > + > > > > + regulators: > > > > + type: object > > > > + description: List of regulators and its properties > > > > + > > > > + patternProperties: > > > > + "^buck- > > > > v(dram1|core|coresshub|proc11|proc12|gpu|s2|modem|s1)$": > > > > + type: object > > > > + $ref: regulator.yaml# > > > > + unevaluatedProperties: false > > > > + > > > > + "^ldo-v(dram2|sim1|ibr|rf12|usb|camio|camd|cn18|fe28)$": > > > > + type: object > > > > + $ref: regulator.yaml# > > > > > > You miss unevaluatedProperties in most of the places. > > > > Hi Krzysztof, > > Thanks for your suggestion, > > Do you mean that all places should have the > > unevaluatedProperties > > Properties ? > > Yes. You put it in some of the places which does not really make > sense... Hi Krzysztof, Thanks for your suggestion, We find that if there is a properties "compatible = "regulator- fixed";" in ldo-vrf12, we should set unevaluatedProperties as true. or it will check yaml warning "Unevaluated Properties are not allowed('compatible' was unexpected)". is it right? There is a properties "compatible = "regulator-fixed";"in ldo-vrf12. It will cause the checking yaml error "ldo-vrf12: 'regulator-name' is a required property". Can you help to give a suggestion to fix the warning? Add regulator-name for ldo-vrf12 or other suggestion? Thanks > > Best regards, > Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: zhiyong.tao <zhiyong.tao@mediatek.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: <lee.jones@linaro.org>, <robh+dt@kernel.org>, <matthias.bgg@gmail.com>, <lgirdwood@gmail.com>, <broonie@kernel.org>, <eddie.huang@mediatek.com>, <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>, <fshao@chromium.org>, <sen.chu@mediatek.com>, <hui.liu@mediatek.com>, <allen-kh.cheng@mediatek.com>, <hsin-hsiung.wang@mediatek.com>, <sean.wang@mediatek.com>, <macpaul.lin@mediatek.com>, <wen.su@mediatek.com>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-rtc@vger.kernel.org>, <Project_Global_Chrome_Upstream_Group@mediatek.com>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org> Subject: Re: [PATCH v3 1/1] regulator: dt-bindings: mediatek: add mt6366 Date: Tue, 16 Aug 2022 20:54:31 +0800 [thread overview] Message-ID: <9bc148119fc36c34f404091ca0f5a2e37727c285.camel@mediatek.com> (raw) In-Reply-To: <CAGE=qrohYZ6f9bbEuYfF=2Rz21nbW_8ho3rBQmHt1D+kQG2-jA@mail.gmail.com> On Fri, 2022-08-12 at 15:55 +0300, Krzysztof Kozlowski wrote: > On Fri, 12 Aug 2022 at 15:52, zhiyong.tao <zhiyong.tao@mediatek.com> > wrote: > > > > On Fri, 2022-08-12 at 13:55 +0300, Krzysztof Kozlowski wrote: > > > On 12/08/2022 12:29, Zhiyong Tao wrote: > > > > Add mt6366 regulator document > > > > > > > > + > > > > +properties: > > > > + compatible: > > > > + const: mediatek,mt6366-regulator > > > > + > > > > + regulators: > > > > + type: object > > > > + description: List of regulators and its properties > > > > + > > > > + patternProperties: > > > > + "^buck- > > > > v(dram1|core|coresshub|proc11|proc12|gpu|s2|modem|s1)$": > > > > + type: object > > > > + $ref: regulator.yaml# > > > > + unevaluatedProperties: false > > > > + > > > > + "^ldo-v(dram2|sim1|ibr|rf12|usb|camio|camd|cn18|fe28)$": > > > > + type: object > > > > + $ref: regulator.yaml# > > > > > > You miss unevaluatedProperties in most of the places. > > > > Hi Krzysztof, > > Thanks for your suggestion, > > Do you mean that all places should have the > > unevaluatedProperties > > Properties ? > > Yes. You put it in some of the places which does not really make > sense... Hi Krzysztof, Thanks for your suggestion, We find that if there is a properties "compatible = "regulator- fixed";" in ldo-vrf12, we should set unevaluatedProperties as true. or it will check yaml warning "Unevaluated Properties are not allowed('compatible' was unexpected)". is it right? There is a properties "compatible = "regulator-fixed";"in ldo-vrf12. It will cause the checking yaml error "ldo-vrf12: 'regulator-name' is a required property". Can you help to give a suggestion to fix the warning? Add regulator-name for ldo-vrf12 or other suggestion? Thanks > > Best regards, > Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-16 13:45 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-12 9:29 [PATCH v3 0/1] Mediatek MT6366 Regulator patch Zhiyong Tao 2022-08-12 9:29 ` Zhiyong Tao 2022-08-12 9:29 ` [PATCH v3 1/1] regulator: dt-bindings: mediatek: add mt6366 Zhiyong Tao 2022-08-12 9:29 ` Zhiyong Tao 2022-08-12 10:55 ` Krzysztof Kozlowski 2022-08-12 10:55 ` Krzysztof Kozlowski 2022-08-12 12:52 ` zhiyong.tao 2022-08-12 12:52 ` zhiyong.tao 2022-08-12 12:55 ` Krzysztof Kozlowski 2022-08-12 12:55 ` Krzysztof Kozlowski 2022-08-12 12:55 ` Krzysztof Kozlowski 2022-08-16 12:54 ` zhiyong.tao [this message] 2022-08-16 12:54 ` zhiyong.tao 2022-08-16 12:57 ` Krzysztof Kozlowski 2022-08-16 12:57 ` Krzysztof Kozlowski 2022-08-16 12:57 ` Krzysztof Kozlowski 2022-08-23 12:42 ` zhiyong.tao 2022-08-23 12:42 ` zhiyong.tao 2022-08-12 15:13 ` Rob Herring 2022-08-12 15:13 ` Rob Herring 2022-08-12 15:13 ` Rob Herring 2022-08-12 10:56 ` [PATCH v3 0/1] Mediatek MT6366 Regulator patch Krzysztof Kozlowski 2022-08-12 10:56 ` Krzysztof Kozlowski
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=9bc148119fc36c34f404091ca0f5a2e37727c285.camel@mediatek.com \ --to=zhiyong.tao@mediatek.com \ --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \ --cc=a.zummo@towertech.it \ --cc=alexandre.belloni@bootlin.com \ --cc=allen-kh.cheng@mediatek.com \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=eddie.huang@mediatek.com \ --cc=hsin-hsiung.wang@mediatek.com \ --cc=hui.liu@mediatek.com \ --cc=krzysztof.kozlowski@linaro.org \ --cc=lee.jones@linaro.org \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-rtc@vger.kernel.org \ --cc=macpaul.lin@mediatek.com \ --cc=matthias.bgg@gmail.com \ --cc=robh+dt@kernel.org \ --cc=sean.wang@mediatek.com \ --cc=sen.chu@mediatek.com \ --cc=wen.su@mediatek.com \ /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.