From: Lijuan Gao <quic_lijuang@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Jingyi Wang" <quic_jingyw@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: <kernel@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Lijuan Gao <quic_lijuang@quicinc.com>
Subject: [PATCH v2 2/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in examples for qcs8300
Date: Thu, 19 Dec 2024 15:59:44 +0800 [thread overview]
Message-ID: <20241219-correct_gpio_ranges-v2-2-19af8588dbd0@quicinc.com> (raw)
In-Reply-To: <20241219-correct_gpio_ranges-v2-0-19af8588dbd0@quicinc.com>
Correct the gpio-ranges in the QCS8300 TLMM pin controller example to
include the UFS_RESET pin, which is expected to be wired to the reset
pin of the primary UFS memory. This allows the UFS driver to toggle it.
Fixes: 5778535972e2 ("dt-bindings: pinctrl: describe qcs8300-tlmm")
Signed-off-by: Lijuan Gao <quic_lijuang@quicinc.com>
---
Documentation/devicetree/bindings/pinctrl/qcom,qcs8300-tlmm.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,qcs8300-tlmm.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,qcs8300-tlmm.yaml
index bb0d7132886a..489b41dcc179 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,qcs8300-tlmm.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,qcs8300-tlmm.yaml
@@ -106,7 +106,7 @@ examples:
interrupts = <GIC_SPI 208 IRQ_TYPE_LEVEL_HIGH>;
gpio-controller;
#gpio-cells = <2>;
- gpio-ranges = <&tlmm 0 0 133>;
+ gpio-ranges = <&tlmm 0 0 134>;
interrupt-controller;
#interrupt-cells = <2>;
--
2.46.0
next prev parent reply other threads:[~2024-12-19 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:59 [PATCH v2 0/6] Correct the number of GPIOs in gpio-ranges for QCS615 and QCS8300 Lijuan Gao
2024-12-19 7:59 ` [PATCH v2 1/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in examples for qcs615 Lijuan Gao
2024-12-19 8:15 ` Krzysztof Kozlowski
2024-12-19 9:30 ` Lijuan Gao
2024-12-19 7:59 ` Lijuan Gao [this message]
2024-12-19 7:59 ` [PATCH v2 3/6] pinctrl: qcom: correct the ngpios entry for QCS615 Lijuan Gao
2024-12-19 18:57 ` Konrad Dybcio
2024-12-19 7:59 ` [PATCH v2 4/6] pinctrl: qcom: correct the ngpios entry for QCS8300 Lijuan Gao
2024-12-19 18:58 ` Konrad Dybcio
2024-12-19 7:59 ` [PATCH v2 5/6] arm64: dts: qcom: correct gpio-ranges for QCS615 Lijuan Gao
2024-12-19 18:58 ` Konrad Dybcio
2024-12-19 7:59 ` [PATCH v2 6/6] arm64: dts: qcom: correct gpio-ranges for QCS8300 Lijuan Gao
2024-12-19 18:58 ` Konrad Dybcio
2024-12-22 8:53 ` [PATCH v2 0/6] Correct the number of GPIOs in gpio-ranges for QCS615 and QCS8300 Linus Walleij
2025-01-07 16:38 ` (subset) " Bjorn Andersson
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=20241219-correct_gpio_ranges-v2-2-19af8588dbd0@quicinc.com \
--to=quic_lijuang@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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_jingyw@quicinc.com \
--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: 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®