All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mohammad Rafi Shaik" <mohammad.rafi.shaik@oss.qualcomm.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: pinctrl: qcom,tlmm-common: Add wakeup-enable
Date: Thu, 15 Oct 2026 14:32:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-172963@kernel.org> (raw)
In-Reply-To: <20261015-tlmm_wakeup_gpio_support-v1-1-c6d6f37a7e51@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: custom property wakeup-enable lacks vendor prefix
--

commit 1b3617dbc4a7e1c4b006d9d99d89f2ff25a551bc
Author: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>

dt-bindings: pinctrl: qcom,tlmm-common: Add wakeup-enable

The TLMM can gate whether a toggle of a pad is transferred to the wake up
controller (PDC/MPM) while the system is in a low power mode. This commit
adds a pin configuration property so a pin can be armed from its own pin
configuration without being turned into a GPIO.

> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
> index aec72e8c06214..95f5396116916 100644
> --- a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
> @@ -87,6 +87,18 @@ $defs:
>        output-high: true
>        output-low: true
>  
> +      wakeup-enable:

[Severity: Low]
Does this hardware-specific property need a vendor prefix?

Since this controls Qualcomm's specific interaction with the PDC/MPM wakeup
controllers, defining it without a qcom, prefix risks namespace collisions
if the pinctrl subsystem later standardizes a generic wakeup-enable property
with different constraints.

If this is intended to be a generic capability, shouldn't it be added to the
core pincfg-node.yaml bindings instead?

> +        type: boolean
> +        description:
> +          Allow a toggle of the specified pins to be transferred to the wake up
> +          controller while the system is in a low power mode. The driver arms
> +          this on its own for pins requested as GPIO interrupts, so it is only
> +          needed for pins that stay muxed to a peripheral function and are
> +          toggled by an external device to request a wake up, such as a
> +          SoundWire data line driven by a codec while the bus is clock stopped.
> +          Only supported on pins that are marked as wakeup capable by the
> +          hardware.
> +
>      allOf:
>        - $ref: pincfg-node.yaml#
>        - $ref: pinmux-node.yaml#

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261015-tlmm_wakeup_gpio_support-v1-0-c6d6f37a7e51@oss.qualcomm.com?part=1

  reply	other threads:[~2026-10-15 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 14:22 [PATCH 0/2] pinctrl: qcom: Allow arming the wakeup_enable bit from pin config Mohammad Rafi Shaik
2026-10-15 14:22 ` [PATCH v1 1/2] dt-bindings: pinctrl: qcom,tlmm-common: Add wakeup-enable Mohammad Rafi Shaik
2026-10-15 14:32   ` sashiko-bot [this message]
2026-10-15 14:23 ` [PATCH v1 2/2] pinctrl: qcom: Allow arming the wakeup_enable bit from pin config Mohammad Rafi Shaik
2026-10-15 14:30   ` sashiko-bot

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=sashiko-outbox-172963@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mohammad.rafi.shaik@oss.qualcomm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.