From: Jaehoon Chung <jh80.chung@samsung.com>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>, u-boot@lists.denx.de
Cc: aford173@gmail.com, Hai Pham <hai.pham.ud@renesas.com>
Subject: Re: [PATCH 04/13] mmc: renesas-sdhi: Adjust HS400 calibration offsets for M3-W r1.3
Date: Wed, 1 Feb 2023 08:33:26 +0900 [thread overview]
Message-ID: <5116a00a-e5cf-e019-e9ab-b7c2bccbb877@samsung.com> (raw)
In-Reply-To: <20230126200607.73185-4-marek.vasut+renesas@mailbox.org>
On 1/27/23 05:05, Marek Vasut wrote:
> From: Hai Pham <hai.pham.ud@renesas.com>
>
> Still uses 0x3 for now, adjust the offset value to TMPPORT3 accordingly
>
> Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> Signed-off-by: Hai Pham <hai.pham.ud@renesas.com>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
Best Regards,
Jaehoon Chung
> ---
> drivers/mmc/renesas-sdhi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/renesas-sdhi.c b/drivers/mmc/renesas-sdhi.c
> index f9155bc44de..90e8aaddb05 100644
> --- a/drivers/mmc/renesas-sdhi.c
> +++ b/drivers/mmc/renesas-sdhi.c
> @@ -899,7 +899,7 @@ static void renesas_sdhi_filter_caps(struct udevice *dev)
> (rmobile_get_cpu_rev_integer() == 1) &&
> (rmobile_get_cpu_rev_fraction() > 2)) {
> priv->adjust_hs400_enable = true;
> - priv->adjust_hs400_offset = 0;
> + priv->adjust_hs400_offset = 3;
> priv->hs400_bad_tap = BIT(1) | BIT(3) | BIT(5) | BIT(7);
> priv->adjust_hs400_calib_table =
> r8a7796_rev13_calib_table[!rmobile_is_gen3_mmc0(priv)];
next prev parent reply other threads:[~2023-01-31 23:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 20:05 [PATCH 01/13] mmc: renesas-sdhi: R-Car M3 r1.3 also uses 4 tuning taps Marek Vasut
2023-01-26 20:05 ` [PATCH 02/13] mmc: renesas-sdhi: Filter out HS400 on M3-W r1.2, V3M, V3H r1.x, D3 Marek Vasut
2023-01-31 23:26 ` Jaehoon Chung
2023-01-26 20:05 ` [PATCH 03/13] mmc: renesas-sdhi: Adjust HS400 calibration tables Marek Vasut
2023-01-31 23:27 ` Jaehoon Chung
2023-01-26 20:05 ` [PATCH 04/13] mmc: renesas-sdhi: Adjust HS400 calibration offsets for M3-W r1.3 Marek Vasut
2023-01-31 23:33 ` Jaehoon Chung [this message]
2023-01-26 20:05 ` [PATCH 05/13] mmc: renesas-sdhi: Add R8A77961 M3-W+ support Marek Vasut
2023-01-31 23:34 ` Jaehoon Chung
2023-01-26 20:06 ` [PATCH 06/13] mmc: renesas-sdhi: Drop R-Car H3 ES3.0 HS400 calibration table Marek Vasut
2023-01-31 23:35 ` Jaehoon Chung
2023-01-26 20:06 ` [PATCH 07/13] mmc: renesas-sdhi: Flag non-standard SDnH handling for V3M Marek Vasut
2023-01-31 23:36 ` Jaehoon Chung
2023-01-26 20:06 ` [PATCH 08/13] clk: renesas: Convert Gen2/Gen3 clock tables to clk-provider struct clk_div_table Marek Vasut
2023-01-26 20:06 ` [PATCH 09/13] clk: renesas: Introduce and use rcar_clk_get_rate64_div_table function Marek Vasut
2023-01-26 20:06 ` [PATCH 10/13] clk: renesas: Handle E3/D3 RPCSRC clock Marek Vasut
2023-01-26 20:06 ` [PATCH 12/13] clk: renesas: Add R8A77970 SD0H/SD0 clocks for SDHI Marek Vasut
2023-01-26 20:06 ` [PATCH 13/13] clk: renesas: rcar-gen3: Factor out CPG library Marek Vasut
2023-01-29 1:50 ` [PATCH 11/13] clk: renesas: Switch to new SD clock handling Marek Vasut
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=5116a00a-e5cf-e019-e9ab-b7c2bccbb877@samsung.com \
--to=jh80.chung@samsung.com \
--cc=aford173@gmail.com \
--cc=hai.pham.ud@renesas.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=u-boot@lists.denx.de \
/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