From: Adrian Hunter <adrian.hunter@intel.com>
To: Ben Chuang <benchuanggli@gmail.com>, <ulf.hansson@linaro.org>
Cc: <victor.shih@genesyslogic.com.tw>,
<ben.chuang@genesyslogic.com.tw>, <HL.Liu@genesyslogic.com.tw>,
<SeanHY.Chen@genesyslogic.com.tw>, <victorshihgli@gmail.com>,
<linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] mmc: sdhci-uhs2: Fix calling incorrect sdhci_set_clock() function
Date: Mon, 1 Sep 2025 15:07:32 +0300 [thread overview]
Message-ID: <86721a4f-1dbd-4ef5-a149-746111170352@intel.com> (raw)
In-Reply-To: <20250901094046.3903-1-benchuanggli@gmail.com>
On 01/09/2025 12:40, Ben Chuang wrote:
> From: Ben Chuang <ben.chuang@genesyslogic.com.tw>
>
> Fix calling incorrect sdhci_set_clock() in __sdhci_uhs2_set_ios() when the
> vendor defines its own sdhci_set_clock().
>
> Fixes: 10c8298a052b ("mmc: sdhci-uhs2: add set_ios()")
> Cc: stable@vger.kernel.org # v6.13+
> Signed-off-by: Ben Chuang <ben.chuang@genesyslogic.com.tw>
> ---
> drivers/mmc/host/sdhci-uhs2.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sdhci-uhs2.c b/drivers/mmc/host/sdhci-uhs2.c
> index 0efeb9d0c376..704fdc946ac3 100644
> --- a/drivers/mmc/host/sdhci-uhs2.c
> +++ b/drivers/mmc/host/sdhci-uhs2.c
> @@ -295,7 +295,10 @@ static void __sdhci_uhs2_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
> else
> sdhci_uhs2_set_power(host, ios->power_mode, ios->vdd);
>
> - sdhci_set_clock(host, host->clock);
> + if (host->ops->set_clock)
> + host->ops->set_clock(host, host->clock);
> + else
> + sdhci_set_clock(host, host->clock);
host->ops->set_clock is not optional. So this should just be:
host->ops->set_clock(host, host->clock);
> }
>
> static int sdhci_uhs2_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
next prev parent reply other threads:[~2025-09-01 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 9:40 Ben Chuang
2025-09-01 12:07 ` Adrian Hunter [this message]
2025-09-01 16:50 ` Adrian Hunter
2025-09-02 6:32 ` Ben Chuang
2025-09-03 11:14 ` Adrian Hunter
2025-09-04 9:49 ` Ben Chuang
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=86721a4f-1dbd-4ef5-a149-746111170352@intel.com \
--to=adrian.hunter@intel.com \
--cc=HL.Liu@genesyslogic.com.tw \
--cc=SeanHY.Chen@genesyslogic.com.tw \
--cc=ben.chuang@genesyslogic.com.tw \
--cc=benchuanggli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=victor.shih@genesyslogic.com.tw \
--cc=victorshihgli@gmail.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®