All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kamal Dasu" <kamal.dasu@broadcom.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v7 2/3] dt-bindings: mmc: Add reset-card-at-resume property
Date: Wed, 05 Aug 2026 22:30:50 +0000	[thread overview]
Message-ID: <20260805223051.5B8FB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805222500.2567801-3-kamal.dasu@broadcom.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing schema dependency for 'reset-card-at-resume' property.
--

--- Patch [2]: [PATCH v7 2/3] dt-bindings: mmc: Add reset-card-at-resume property ---
commit 58ef61eea1643d1fd872cdd2532bc0149abeb166
Author: Kamal Dasu <kamal.dasu@broadcom.com>

dt-bindings: mmc: Add reset-card-at-resume property

On some platforms, firmware or other hardware accesses the card
during suspend/resume, before the kernel's own resume path has run,
leaving the card in a state the kernel can no longer assume it knows.
Add a flag property so such boards can tell the mmc core the card
needs to be reset before it can be used again.

> diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
> index c18bf0d6a56ec..6929969ed5a2a 100644
> --- a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
> +++ b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
> @@ -293,6 +293,13 @@ properties:
>      description:
>        Preserves card power during a suspend/resume cycle.
>  
> +  reset-card-at-resume:
> +    $ref: /schemas/types.yaml#/definitions/flag
> +    description:
> +      The HW/FW may have accessed the card during suspend/resume,
> +      leaving it in an unknown state. Hence, before the card can be
> +      used, it must be reset.
> +

[Severity: Low]
Does this new property need to be added to the dependencies block at the bottom
of the file?

The commit message notes this flag "is expected to be paired with
keep-power-in-suspend", because a resume reset only makes sense if power is
preserved (otherwise power cycling forces a reset inherently). The v7 changelog
also states the driver now strictly requires this property alongside
keep-power-in-suspend for (e)MMC.

Without a schema dependency, device trees might incorrectly specify
reset-card-at-resume without the required keep-power-in-suspend property and
still pass dt_binding_check validation. Would it be better to enforce this
constraint in the schema?

dependencies:
  cd-debounce-delay-ms: [ cd-gpios ]
  fixed-emmc-driver-type: [ non-removable ]
  reset-card-at-resume: [ keep-power-in-suspend ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260805222500.2567801-1-kamal.dasu@broadcom.com?part=2

  reply	other threads:[~2026-08-05 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 22:24 [PATCH v7 0/3] mmc: core: Keep the card powered across suspend when firmware needs it live Kamal Dasu
2026-08-05 22:24 ` [PATCH v7 1/3] dt-bindings: mmc: Extend keep-power-in-suspend beyond SDIO Kamal Dasu
2026-08-05 22:24 ` [PATCH v7 2/3] dt-bindings: mmc: Add reset-card-at-resume property Kamal Dasu
2026-08-05 22:30   ` sashiko-bot [this message]
2026-08-07 13:56   ` Rob Herring
2026-08-05 22:25 ` [PATCH v7 3/3] mmc: core: Honor keep-power-in-suspend and reset-card-at-resume for (e)MMC Kamal Dasu
2026-08-05 22:38   ` 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=20260805223051.5B8FB1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kamal.dasu@broadcom.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.