From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephan Gerhold <stephan@gerhold.net>,
Melody Olvera <quic_molvera@quicinc.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Richard Acayan <mailingradian@gmail.com>,
Martin Botka <martin.botka@somainline.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: qcom: add missing tlmm labels in examples
Date: Mon, 9 Nov 2026 23:03:31 +0100 [thread overview]
Message-ID: <a93ffdfd-c745-42d4-bef3-70b991adcca6@kernel.org> (raw)
In-Reply-To: <20261109-qcom-tlmm-ex-phandle-v1-1-b77b09e6ec9b@oss.qualcomm.com>
On 09/11/2026 16:57, Bartosz Golaszewski wrote:
> Several DT binding documents for Qualcomm TLMM pin controllers define
> the gpio-ranges property in the example node that references the tlmm
> node except that the label is missing. It's harmless as we ignore
> non-existent phandles but for correctness and consistency - add missing
> labels.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/pinctrl/qcom,msm8909-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,qdu1000-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sar2130p-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sc8180x-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sdm670-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sdm845-pinctrl.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm6125-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm6350-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm6375-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm8250-pinctrl.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm8350-tlmm.yaml | 2 +-
> Documentation/devicetree/bindings/pinctrl/qcom,sm8450-tlmm.yaml | 2 +-
> 13 files changed, 13 insertions(+), 13 deletions(-)
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-09 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:57 Bartosz Golaszewski
2026-11-09 21:53 ` Richard Acayan
2026-11-09 22:03 ` Krzysztof Kozlowski [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=a93ffdfd-c745-42d4-bef3-70b991adcca6@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mailingradian@gmail.com \
--cc=martin.botka@somainline.org \
--cc=quic_molvera@quicinc.com \
--cc=robh@kernel.org \
--cc=stephan@gerhold.net \
--cc=vkoul@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: 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
all inboxes | Powered by JetHome®