From: Rob Herring <robh@kernel.org>
To: Tengfei Fan <quic_tengfan@quicinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
andersson@kernel.org, agross@kernel.org,
konrad.dybcio@linaro.org, linus.walleij@linaro.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_tsoni@quicinc.com, quic_shashim@quicinc.com,
quic_kaushalk@quicinc.com, quic_tdas@quicinc.com,
quic_tingweiz@quicinc.com, quic_aiquny@quicinc.com,
kernel@quicinc.com
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add SM4450 pinctrl
Date: Fri, 15 Sep 2023 09:59:47 -0500 [thread overview]
Message-ID: <20230915145947.GA3716246-robh@kernel.org> (raw)
In-Reply-To: <35371580-8e5a-4f72-aec2-951268c296a3@quicinc.com>
On Fri, Sep 15, 2023 at 03:30:16PM +0800, Tengfei Fan wrote:
>
>
> 在 9/15/2023 3:04 PM, Krzysztof Kozlowski 写道:
> > On 15/09/2023 03:58, Tengfei Fan wrote:
> > > Add device tree binding Documentation details for Qualcomm SM4450
> > > TLMM device.
> > >
> > > Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
> >
> > ...
> >
> > > +
> > > +patternProperties:
> > > + "-state$":
> > > + oneOf:
> > > + - $ref: "#/$defs/qcom-sm4450-tlmm-state"
> > > + - patternProperties:
> > > + "-pins$":
> > > + $ref: "#/$defs/qcom-sm4450-tlmm-state"
> > > + additionalProperties: false
> > > +
> > > +$defs:
> > > + qcom-sm4450-tlmm-state:
> > > + type: object
> > > + description:
> > > + Pinctrl node's client devices use subnodes for desired pin configuration.
> > > + Client device subnodes use below standard properties.
> > > + $ref: qcom,tlmm-common.yaml#/$defs/qcom-tlmm-state
> > > + unevaluatedProperties: false
> > > +
> > > + properties:
> > > + pins:
> > > + description:
> > > + List of gpio pins affected by the properties specified in this
> > > + subnode.
> > > + items:
> > > + oneOf:
> > > + - pattern: "^gpio([0-9]|[1-9][0-9]|1[0-9][0-9])$"
> >
> > This is still wrong. How many GPIOs do you have? Please open existing
> > bindings for recent device (e.g. sm8550) and look how it is done there.
> yes, will update to "^gpio([0-9]|[1-9][0-9]|1[0-2][0-5])$".
What about 106, 116, etc.?
Rob
next prev parent reply other threads:[~2023-09-15 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 1:58 [PATCH v2 0/2] pinctl: qcom: Add SM4450 pinctrl driver Tengfei Fan
2023-09-15 1:58 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add SM4450 pinctrl Tengfei Fan
2023-09-15 7:04 ` Krzysztof Kozlowski
2023-09-15 7:30 ` Tengfei Fan
2023-09-15 14:59 ` Rob Herring [this message]
2023-09-18 1:39 ` Tengfei Fan
2023-09-15 1:58 ` [PATCH v2 2/2] pinctrl: qcom: Add SM4450 pinctrl driver Tengfei Fan
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=20230915145947.GA3716246-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_kaushalk@quicinc.com \
--cc=quic_shashim@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.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).