From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 2/2] pinctrl: qcom: Add Shikra pinctrl driver
Date: Wed, 13 May 2026 22:00:37 +0000 [thread overview]
Message-ID: <20260513220038.0697AC19425@smtp.kernel.org> (raw)
In-Reply-To: <20260512-shikra-pinctrl-v4-2-b93c3a2e4c08@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The Kconfig symbol PINCTRL_SHIKRA incorrectly uses `default ARCH_QCOM`, which is inconsistent with the rest of the pinctrl drivers in the subsystem.
--
commit 635e77fc90eb7d688d1990612274cdff1b91f42d
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
pinctrl: qcom: Add Shikra pinctrl driver
This commit adds the pinctrl driver for the TLMM block found in the
Qualcomm Shikra SoC.
> diff --git a/drivers/pinctrl/qcom/Kconfig.msm b/drivers/pinctrl/qcom/Kconfig.msm
> index 836cdeca1006f..20e1068492734 100644
> --- a/drivers/pinctrl/qcom/Kconfig.msm
> +++ b/drivers/pinctrl/qcom/Kconfig.msm
[ ... ]
> @@ -369,6 +369,17 @@ config PINCTRL_SDX75
> Qualcomm Technologies Inc TLMM block found on the Qualcomm
> Technologies Inc SDX75 platform.
>
> +config PINCTRL_SHIKRA
> + tristate "Qualcomm Shikra pin controller driver"
> + depends on ARM64 || COMPILE_TEST
> + default ARCH_QCOM
Is this default intended? Looking at the other SoC-specific pin controller
drivers in this file, such as PINCTRL_SM4450 just below this, they do not
appear to use default ARCH_QCOM.
Defining it here forces this driver to be built by default whenever the
generic ARCH_QCOM is enabled, which seems inconsistent with the established
pattern for the rest of the subsystem.
> + help
> + This is the pinctrl, pinmux, pinconf and gpiolib driver for the
> + Qualcomm Technologies Inc Top Level Mode Multiplexer block (TLMM)
> + found on the Qualcomm Technologies Inc Shikra platform.
> + Say Y here to compile statically, or M here to compile it as a module.
> + If unsure, say N.
> +
> config PINCTRL_SM4450
> tristate "Qualcomm Technologies Inc SM4450 pin controller driver"
> depends on ARM64 || COMPILE_TEST
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260512-shikra-pinctrl-v4-0-b93c3a2e4c08@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-05-13 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:25 [PATCH v4 0/2] pinctrl: qcom: Add support for Qualcomm Shikra SoC Komal Bajaj
2026-05-12 13:25 ` [PATCH v4 1/2] dt-bindings: pinctrl: qcom: Document Shikra Top Level Mode Multiplexer Komal Bajaj
2026-05-12 13:25 ` [PATCH v4 2/2] pinctrl: qcom: Add Shikra pinctrl driver Komal Bajaj
2026-05-13 22:00 ` sashiko-bot [this message]
2026-05-12 14:25 ` [PATCH v4 0/2] pinctrl: qcom: Add support for Qualcomm Shikra SoC 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=20260513220038.0697AC19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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