From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: muzafferkadir@mainlining.org,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@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 v2 2/2] pinctrl: qcom: Add MSM8952 tlmm pinctrl driver
Date: Wed, 2 Sep 2026 15:03:33 +0200 [thread overview]
Message-ID: <7eea6a82-6bcf-486d-9c0e-5a68c34c03de@oss.qualcomm.com> (raw)
In-Reply-To: <20260820-msm8952-pinctrl-v2-2-bf2b8b7b379b@mainlining.org>
On 20-Aug-26 13:17, Muzaffer Kadir via B4 Relay wrote:
> From: Muzaffer Kadir <muzafferkadir@mainlining.org>
>
> MSM8952 has same pin count and similar pinctrl
> functions mostly with msm8917, but some functions use different pins.
>
> Signed-off-by: Muzaffer Kadir <muzafferkadir@mainlining.org>
> ---
The following is a review from my AI agent who inspected the
hw specification and prior art/review feedback regarding qcom
pinctrl. I read it and approve of it:
Hi Muzaffer,
The driver currently contains function/group declarations which are not connected to any PINGROUP() entry.
For each item below, add the function to the corresponding GPIO’s PINGROUP() definition:
Function GPIO
━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━
mipi_dsi0 0
────────────────────── ──────
smb_int 1
────────────────────── ──────
qdss_cti_trig_out_b0 2
────────────────────── ──────
rcm_marker2 3
────────────────────── ──────
qdss_cti_trig_out_a1 3
────────────────────── ──────
codec_mad 13
────────────────────── ──────
nfc_disable 16
────────────────────── ──────
nfc_irq 17
────────────────────── ──────
flash_strobe 33
────────────────────── ──────
cam1_standby 35
────────────────────── ──────
cam1_rst 36
────────────────────── ──────
cam2_standby 37
────────────────────── ──────
cam2_rst 38
────────────────────── ──────
webcam_standby 39
────────────────────── ──────
webcam_rst 40
────────────────────── ──────
rcm_marker1 41
────────────────────── ──────
accel_int 42
────────────────────── ──────
alsp_int 43
────────────────────── ──────
mag_int 44
────────────────────── ──────
gyro_int 45
────────────────────── ──────
pressure_int 46
────────────────────── ──────
fp_gpio 47
────────────────────── ──────
fp_int 48
────────────────────── ──────
us_euro 63
────────────────────── ──────
ts_resout 64
────────────────────── ──────
ts_sample 65
────────────────────── ──────
sdcard_det 67
────────────────────── ──────
audio_reset 68
────────────────────── ──────
codec_int1 73
────────────────────── ──────
codec_int2 74
────────────────────── ──────
key_volp 85
────────────────────── ──────
key_snapshot 86
────────────────────── ──────
key_focus 87
────────────────────── ──────
key_home 88
────────────────────── ──────
backlight_en 91
────────────────────── ──────
lcd_en 92
────────────────────── ──────
usbc_irq 93
────────────────────── ──────
uim3_ldo 96
────────────────────── ──────
wsa_irq 97
For example:
> static const char *const mipi_dsi0_groups[] = { "gpio0" };
must have a matching mipi_dsi0 entry in the GPIO0 PINGROUP() definition. The same consistency is required for every item in the table. The gpio function is intentionally excluded because it is inserted
implicitly by the PINGROUP() macro.
There are also functions missing from the GPIO table. Please add these to the corresponding groups. The final column is the function index from the MSM8952 GPIO mapping:
Function GPIO Function index
━━━━━━━━━━━ ━━━━━━ ━━━━━━━━━━━━━━━━
gp_pdm_2a 7 4
─────────── ────── ────────────────
gp_pdm_1b 20 3
─────────── ────── ────────────────
gp_pdm_2b 38 1
─────────── ────── ────────────────
gp_mn 39 2
─────────── ────── ────────────────
gp_pdm_1a 45 1
─────────── ────── ────────────────
gp0_clk 46 1
─────────── ────── ────────────────
gp1_clk 47 2
─────────── ────── ────────────────
gp_pdm_0b 48 2
─────────── ────── ────────────────
gp_pdm_0a 66 3
Finally, please move:
> MODULE_DEVICE_TABLE(of, msm8952_pinctrl_of_match);
immediately after the OF match table, consistent with the other Qualcomm pinctrl drivers.
Best regards,
Konrad
next prev parent reply other threads:[~2026-09-02 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 11:17 [PATCH v2 0/2] Add pinctrl support for MSM8952 Muzaffer Kadir via B4 Relay
2026-08-20 11:17 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add MSM8952 pinctrl Muzaffer Kadir via B4 Relay
2026-08-20 11:17 ` [PATCH v2 2/2] pinctrl: qcom: Add MSM8952 tlmm pinctrl driver Muzaffer Kadir via B4 Relay
2026-09-02 13:03 ` Konrad Dybcio [this message]
2026-09-02 16:11 ` Muzaffer Kadir
2026-09-04 9:43 ` Konrad Dybcio
2026-08-20 16:37 ` [PATCH v2 0/2] Add pinctrl support for MSM8952 Linus Walleij
2026-09-01 15:59 ` Bartosz Golaszewski
2026-09-02 10:32 ` Muzaffer Kadir
2026-09-02 10:34 ` Bartosz Golaszewski
2026-09-02 10:41 ` Muzaffer Kadir
2026-09-02 11:06 ` Bartosz Golaszewski
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=7eea6a82-6bcf-486d-9c0e-5a68c34c03de@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=muzafferkadir@mainlining.org \
--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