Re: [PATCH v4 1/2] dt-bindings: mmc: Extend keep-power-in-suspend beyond SDIO
Ulf Hansson <[email protected]> Mon, 3 Aug 2026 14:14:25 +0200
| Newsgroups | org.kernel.vger.linux-mmc,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAPx+jO-C9AYu012zw5rUZe1-iN6779DpYUqnURfKX=5Mdi1BWg@mail.gmail.com> |
On Tue, Jul 28, 2026 at 9:03=E2=80=AFPM Kamal Dasu <[email protected]= > wrote: > > keep-power-in-suspend already documents exactly the requirement > needed on (e)MMC platforms where firmware accesses the card directly > during resume. Rather than add a separate property describing the > same contract, drop its "SDIO only" restriction and document the > (e)MMC use case alongside the existing SDIO one. > > Signed-off-by: Kamal Dasu <[email protected]> > --- > Changes in v4: > - Dropped no-mmc-poweroff-suspend entirely and extended > keep-power-in-suspend instead, per Krzysztof: the two properties > described the same "don't power off across suspend/resume" > contract. > > Changes in v3: > - Renamed from no-mmc-sleep; dropped S_A_TIMEOUT framing per Ulf. > > Changes in v2: > - New patch, replacing v1's card-level quirk, per Ulf. > > Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml | 7 +++= +++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller-common.= yaml b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml > index 3d7195e9461c..f4663b318435 100644 > --- a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml > +++ b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml > @@ -291,7 +291,12 @@ properties: > keep-power-in-suspend: > $ref: /schemas/types.yaml#/definitions/flag > description: > - SDIO only. Preserves card power during a suspend/resume cycle. > + Preserves card power during a suspend/resume cycle. For SDIO, > + this is a request an individual function driver can make at > + runtime via sdio_set_host_pm_flags(). For (e)MMC, it is instead > + a fixed platform characteristic, needed on boards where firmware > + accesses the card directly during system resume, before the > + kernel's own resume path runs. The above isn't a proper HW description. It even refers to functions that currently exist in the kernel. Please update and remove the software related parts. > > wakeup-source: > $ref: /schemas/types.yaml#/definitions/flag > -- > 2.34.1 > Kind regards Uffe