From: hui.liu <hui.liu@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: <linus.walleij@linaro.org>, <krzysztof.kozlowski+dt@linaro.org>,
<matthias.bgg@gmail.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<jianguo.zhang@mediatek.com>, <zhiyong.tao@mediatek.com>,
<sean.wang@mediatek.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: pinctrl: mediatek: add support for mt8188
Date: Mon, 1 Aug 2022 14:16:47 +0800 [thread overview]
Message-ID: <e8dc87197fd19de2fd16262967ee305c142f4282.camel@mediatek.com> (raw)
In-Reply-To: <20220729230439.GA99380-robh@kernel.org>
On Fri, 2022-07-29 at 17:04 -0600, Rob Herring wrote:
>
> > +
> > +# PIN CONFIGURATION NODES
> > +patternProperties:
> > + '-pins$':
> > + type: object
> > + $ref: "/schemas/pinctrl/pincfg-node.yaml"
>
> Doesn't this belong in the child '^pins' node? There's no properties
> in
> this node, right?
>
> >
Hi Rob,
Yes. I will move $ref: "/schemas/pinctrl/pincfg-node.yaml" to '^pins'
node in the next version:
# PIN CONFIGURATION NODES
patternProperties:
'-pins$':
type: object
additionalProperties: false
patternProperties:
'^pins':
type: object
$ref: "/schemas/pinctrl/pincfg-node.yaml"
additionalProperties: false
Thanks.
Hui
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-08-01 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 10:24 [PATCH v3 0/2] MediaTek pinctrl patch on mt8188 Hui Liu
2022-07-29 10:24 ` [PATCH v4 1/2] dt-bindings: pinctrl: mediatek: add support for mt8188 Hui Liu
2022-07-29 23:04 ` Rob Herring
2022-08-01 6:16 ` hui.liu [this message]
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=e8dc87197fd19de2fd16262967ee305c142f4282.camel@mediatek.com \
--to=hui.liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jianguo.zhang@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=zhiyong.tao@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: 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;
as well as URLs for NNTP newsgroup(s).