From: Adrian Hunter <adrian.hunter@intel.com>
To: Artem Shimko <a.shimko.dev@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
<Jisheng.Zhang@synaptics.com>, <hehuan1@eswincomputing.com>,
<yifeng.zhao@rock-chips.com>, Ulf Hansson <ulfh@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
<linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: sdhci-of-dwcmshc: add reset control support in suspend/resume
Date: Tue, 5 May 2026 15:36:52 +0300 [thread overview]
Message-ID: <39db3c9d-e2f8-4018-93b8-5a97b5119d19@intel.com> (raw)
In-Reply-To: <CAOPX746c1N1vsibTMW8KLJoi7BzZXuQj+yCUgApagLwmOMt9TQ@mail.gmail.com>
On 05/05/2026 15:12, Artem Shimko wrote:
> Hi Adrian,
>
> On Tue, May 5, 2026 at 2:28 PM Adrian Hunter <adrian.hunter@intel.com> wrote:
>> Only dwcmshc_rk35xx_init() and sdhci_eic7700_reset_init() assign
>> dwc_priv->reset, so I am confused about what devices you intend
>> this patch for.
>
> Yeah, the change as proposed would affect other devices, and I should
> not assume it's safe for them without testing. Yes, I was so fast to
> send it.
> My intention was to make the reset control accessible for PM
> operations, but only for the specific SoC I'm working with.
> However, since the custom MMC driver code is not part of this upstream
> submission, the patch currently lacks the necessary condition to limit
> the new behavior.
>
> Could you please check my plan to prepare v2 to:
> 1. Keep the reset control moved to dwcmshc_priv (so it's accessible
> where needed).
> 2. Add a dedicated flag (e.g., bool needs_reset_on_pm or similar) to
> dwcmshc_priv so that only devices that explicitly opt in will trigger
> the reset during suspend/resume.
Sounds fine
>
> That ensures the existing behavior for Rockchip RK35xx and EIC7700
> remains unchanged.
> This way, the infrastructure is in place for devices that need it,
> without imposing it on platforms where it hasn't been validated.
> Thank you again for the review!
>
> Regards,
> Artem
next prev parent reply other threads:[~2026-05-05 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 12:34 [PATCH] mmc: sdhci-of-dwcmshc: add reset control support in suspend/resume Artem Shimko
2026-04-15 14:51 ` Andy Shevchenko
2026-04-17 10:45 ` Artem Shimko
2026-05-05 11:27 ` Adrian Hunter
2026-05-05 12:12 ` Artem Shimko
2026-05-05 12:36 ` Adrian Hunter [this message]
2026-05-05 12:49 ` Artem Shimko
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=39db3c9d-e2f8-4018-93b8-5a97b5119d19@intel.com \
--to=adrian.hunter@intel.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=a.shimko.dev@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=hehuan1@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=ulfh@kernel.org \
--cc=yifeng.zhao@rock-chips.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 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.