From: Christoph Hellwig <hch@infradead.org>
To: Sayali Lokhande <quic_sayalil@quicinc.com>
Cc: ulf.hansson@linaro.org, wsa+renesas@sang-engineering.com,
avri.altman@wdc.com, adrian.hunter@intel.com,
shawn.lin@rock-chips.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH V1 1/1] mmc: sdio: Export an API to reinit the SDIO card
Date: Mon, 21 Jul 2025 22:55:33 -0700 [thread overview]
Message-ID: <aH8n1RNBmorMq9X9@infradead.org> (raw)
In-Reply-To: <20250721094328.6556-2-quic_sayalil@quicinc.com>
On Mon, Jul 21, 2025 at 03:13:28PM +0530, Sayali Lokhande wrote:
> Some SDIO client drivers, manage external power to the SDIO card.
> In such cases, the card may be power-cycled independently of the
> MMC core's runtime PM state.
> Currently, reinitialization of the SDIO card is tied to the runtime
> PM resume path. However, if the card is powered off and on again before
> the autosuspend delay expires, the runtime suspend/resume callbacks are
> not triggered, leaving the card in an uninitialized state.
>
> To address this, export sdio_reinit_card() so that client drivers can
> explicitly trigger reinitialization after powering the card back on,
> ensuring proper device state regardless of runtime PM behavior.
>
> This change enables more robust handling of power-managed SDIO devices
> in scenarios where runtime PM is disabled or insufficient.
This seems to lack an actual users.
If we keep getting these malicious add unused export patches from
certain companies over and over we'll really have to start consider
banning them from kernel development.
next prev parent reply other threads:[~2025-07-22 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:43 [PATCH V1 0/1] Export an API to reinit " Sayali Lokhande
2025-07-21 9:43 ` [PATCH V1 1/1] mmc: sdio: Export an API to reinit the " Sayali Lokhande
2025-07-22 5:55 ` Christoph Hellwig [this message]
2025-07-23 10:25 ` [PATCH V1 0/1] Export an API to reinit " Ulf Hansson
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=aH8n1RNBmorMq9X9@infradead.org \
--to=hch@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_sayalil@quicinc.com \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
/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
all inboxes | Powered by JetHome®