From: Ulf Hansson <ulf.hansson@linaro.org>
To: Liming Sun <limings@nvidia.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
David Thompson <davthompson@nvidia.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] dw_mmc-bluefield: add hw_reset() support
Date: Thu, 20 Jun 2024 16:22:10 +0200 [thread overview]
Message-ID: <CAPDyKFqXZ3JdQBMpTM1ccAFqUSsqUcZ2fn+Ste2aG-APS2dt2w@mail.gmail.com> (raw)
In-Reply-To: <2c459196c6867e325f9386ec0559efea464cfdd6.1718213918.git.limings@nvidia.com>
On Thu, 13 Jun 2024 at 00:53, Liming Sun <limings@nvidia.com> wrote:
>
> The eMMC RST_N register is implemented as secure register on
> BlueField SoC and controlled by ATF. This commit sends SMC call
> to ATF for the eMMC HW reset.
Just to make sure I get this correctly. Asserting the eMMC reset line
is managed through a secure register? Or is this about resetting the
eMMC controller?
No matter what, it looks to me that it should be implemented as a
reset provider.
Kind regards
Uffe
>
> Reviewed-by: David Thompson <davthompson@nvidia.com>
> Signed-off-by: Liming Sun <limings@nvidia.com>
> ---
> drivers/mmc/host/dw_mmc-bluefield.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/dw_mmc-bluefield.c b/drivers/mmc/host/dw_mmc-bluefield.c
> index 4747e5698f48..24e0b604b405 100644
> --- a/drivers/mmc/host/dw_mmc-bluefield.c
> +++ b/drivers/mmc/host/dw_mmc-bluefield.c
> @@ -3,6 +3,7 @@
> * Copyright (C) 2018 Mellanox Technologies.
> */
>
> +#include <linux/arm-smccc.h>
> #include <linux/bitfield.h>
> #include <linux/bitops.h>
> #include <linux/mmc/host.h>
> @@ -20,6 +21,9 @@
> #define BLUEFIELD_UHS_REG_EXT_SAMPLE 2
> #define BLUEFIELD_UHS_REG_EXT_DRIVE 4
>
> +/* SMC call for RST_N */
> +#define BLUEFIELD_SMC_SET_EMMC_RST_N 0x82000007
> +
> static void dw_mci_bluefield_set_ios(struct dw_mci *host, struct mmc_ios *ios)
> {
> u32 reg;
> @@ -34,8 +38,20 @@ static void dw_mci_bluefield_set_ios(struct dw_mci *host, struct mmc_ios *ios)
> mci_writel(host, UHS_REG_EXT, reg);
> }
>
> +static void dw_mci_bluefield_hw_reset(struct dw_mci *host)
> +{
> + struct arm_smccc_res res = { 0 };
> +
> + arm_smccc_smc(BLUEFIELD_SMC_SET_EMMC_RST_N, 0, 0, 0, 0, 0, 0, 0,
> + &res);
> +
> + if (res.a0)
> + pr_err("RST_N failed.\n");
> +}
> +
> static const struct dw_mci_drv_data bluefield_drv_data = {
> - .set_ios = dw_mci_bluefield_set_ios
> + .set_ios = dw_mci_bluefield_set_ios,
> + .hw_reset = dw_mci_bluefield_hw_reset
> };
>
> static const struct of_device_id dw_mci_bluefield_match[] = {
> --
> 2.30.1
>
next prev parent reply other threads:[~2024-06-20 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 22:52 [PATCH v1 0/2] eMMC RST_N support on BlueField-2 SoC Liming Sun
2024-06-12 22:52 ` [PATCH v1 1/2] dw_mmc: support platform specific hw_reset() Liming Sun
2024-06-12 22:52 ` [PATCH v1 2/2] dw_mmc-bluefield: add hw_reset() support Liming Sun
2024-06-20 14:22 ` Ulf Hansson [this message]
2024-06-25 19:13 ` Liming Sun
2024-07-08 13:15 ` 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=CAPDyKFqXZ3JdQBMpTM1ccAFqUSsqUcZ2fn+Ste2aG-APS2dt2w@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=davthompson@nvidia.com \
--cc=limings@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).