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 3/6] pinctrl: qcom: correct the number of ngpios for QCS615
Date: Thu, 12 Dec 2024 17:24:02 +0800 [thread overview]
Message-ID: <20241212-correct_gpio_ranges-v1-3-c5f20d61882f@quicinc.com> (raw)
In-Reply-To: <20241212-correct_gpio_ranges-v1-0-c5f20d61882f@quicinc.com>
The UFS_RESET pin is expected to be wired to the reset pin of the primary
UFS memory. Reorder the pins and expose it as a GPIO, so that the UFS
driver can toggle it. Therefore, correct the number of ngpios.
Fixes: b698f36a9d40 ("pinctrl: qcom: add the tlmm driver for QCS615 platform")
Signed-off-by: Lijuan Gao <quic_lijuang@quicinc.com>
---
drivers/pinctrl/qcom/pinctrl-qcs615.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/qcom/pinctrl-qcs615.c b/drivers/pinctrl/qcom/pinctrl-qcs615.c
index 23015b055f6a..17ca743c2210 100644
--- a/drivers/pinctrl/qcom/pinctrl-qcs615.c
+++ b/drivers/pinctrl/qcom/pinctrl-qcs615.c
@@ -1062,7 +1062,7 @@ static const struct msm_pinctrl_soc_data qcs615_tlmm = {
.nfunctions = ARRAY_SIZE(qcs615_functions),
.groups = qcs615_groups,
.ngroups = ARRAY_SIZE(qcs615_groups),
- .ngpios = 123,
+ .ngpios = 124,
.tiles = qcs615_tiles,
.ntiles = ARRAY_SIZE(qcs615_tiles),
.wakeirq_map = qcs615_pdc_map,
--
2.46.0
next prev parent reply other threads:[~2024-12-12 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 9:23 [PATCH 0/6] Correct the number of GPIOs in gpio-ranges for QCS615 and QCS8300 Lijuan Gao
2024-12-12 9:24 ` [PATCH 1/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in examples for qcs615 Lijuan Gao
2024-12-17 14:50 ` Rob Herring (Arm)
2024-12-12 9:24 ` [PATCH 2/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in examples for qcs8300 Lijuan Gao
2024-12-17 14:50 ` Rob Herring (Arm)
2024-12-12 9:24 ` Lijuan Gao [this message]
2024-12-12 9:24 ` [PATCH 4/6] pinctrl: qcom: correct the number of ngpios for QCS8300 Lijuan Gao
2024-12-12 9:24 ` [PATCH 5/6] arm64: dts: qcom: correct gpio-ranges for QCS615 Lijuan Gao
2024-12-12 9:24 ` [PATCH 6/6] arm64: dts: qcom: correct gpio-ranges for QCS8300 Lijuan Gao
2024-12-12 9:34 ` [PATCH 0/6] Correct the number of GPIOs in gpio-ranges for QCS615 and QCS8300 Dmitry Baryshkov
2024-12-16 6:46 ` Lijuan Gao
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=20241212-correct_gpio_ranges-v1-3-c5f20d61882f@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®