From: "Jaehoon Chung" <jh80.chung@samsung.com>
To: "'Yang Xiwen'" <forbidden405@outlook.com>,
"'Peng Fan'" <peng.fan@nxp.com>
Cc: <u-boot@lists.denx.de>
Subject: RE: [PATCH v2 2/3] mmc: dw_mmc: Don't return error if data busy timeout
Date: Mon, 15 Apr 2024 15:58:54 +0900 [thread overview]
Message-ID: <008601da8f02$618147e0$2483d7a0$@samsung.com> (raw)
In-Reply-To: <SEZPR06MB69598F7A966ABC6664BD4724963D2@SEZPR06MB6959.apcprd06.prod.outlook.com>
Hi,
> -----Original Message-----
> From: Yang Xiwen <forbidden405@outlook.com>
> Sent: Wednesday, April 3, 2024 10:20 AM
> To: Jaehoon Chung <jh80.chung@samsung.com>; Peng Fan <peng.fan@nxp.com>
> Cc: u-boot@lists.denx.de
> Subject: Re: [PATCH v2 2/3] mmc: dw_mmc: Don't return error if data busy timeout
>
> On 4/3/2024 8:41 AM, Jaehoon Chung wrote:
> > Hi,
> >
> > On 2/1/24 23:05, Yang Xiwen via B4 Relay wrote:
> >> From: Yang Xiwen <forbidden405@outlook.com>
> >>
> >> As described in [1], some poor hardware or cards would fail to release
> >> the bus and keep driving data lines low. Ignore it and send the next cmd
> >> directly seems okay for most cases.
> > This patch seems to be same with previous patch, right?
>
>
> From my observation, this patch does fix some weird problems and is
> mostly okay for other dwmmc users. I can't say it is very well tested
> because of I can't come up of other tests i can do except some `mmc
> read` and `mmc write`.
>
>
> >
> > Best Regards,
> > Jaehoon Chung
> >
> >> [1]: https://patchwork.kernel.org/project/linux-mmc/patch/1424458179-5456-1-git-send-email-
> dianders@chromium.org/
> >>
> >> Signed-off-by: Yang Xiwen <forbidden405@outlook.com>
Tested-by: Jaehoon Chung <jh80.chung@samsung.com>
Best Regards,
Jaehoon Chung
> >> ---
> >> drivers/mmc/dw_mmc.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c
> >> index 400066fa99..e103664145 100644
> >> --- a/drivers/mmc/dw_mmc.c
> >> +++ b/drivers/mmc/dw_mmc.c
> >> @@ -262,8 +262,8 @@ static int dwmci_send_cmd(struct mmc *mmc, struct mmc_cmd *cmd,
> >>
> >> while (dwmci_readl(host, DWMCI_STATUS) & DWMCI_BUSY) {
> >> if (get_timer(start) > timeout) {
> >> - debug("%s: Timeout on data busy\n", __func__);
> >> - return -ETIMEDOUT;
> >> + debug("%s: Timeout on data busy, continue anyway\n", __func__);
> >> + break;
> >> }
> >> }
> >>
>
>
> --
> Regards,
> Yang Xiwen
next prev parent reply other threads:[~2024-04-15 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 14:05 [PATCH v2 0/3] mmc: hi6220-dwmmc: handle resets and clocks Yang Xiwen via B4 Relay
2024-02-01 14:05 ` [PATCH v2 1/3] mmc: hi6220-dwmmc: handle clocks and resets if CONFIG_CLK and CONFIG_DM_RESET enabled Yang Xiwen via B4 Relay
2024-04-03 0:39 ` Jaehoon Chung
2024-04-03 1:16 ` Yang Xiwen
2024-04-15 6:57 ` Jaehoon Chung
2024-02-01 14:05 ` [PATCH v2 2/3] mmc: dw_mmc: Don't return error if data busy timeout Yang Xiwen via B4 Relay
2024-04-03 0:41 ` Jaehoon Chung
2024-04-03 1:19 ` Yang Xiwen
2024-04-15 6:58 ` Jaehoon Chung [this message]
2024-02-01 14:05 ` [PATCH v2 3/3] mmc: hi6220_dw_mmc: add fifoth_val to private data and set it in .probe Yang Xiwen via B4 Relay
2024-04-03 0:43 ` Jaehoon Chung
2024-04-03 1:22 ` Yang Xiwen
2024-04-15 7:00 ` Jaehoon Chung
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='008601da8f02$618147e0$2483d7a0$@samsung.com' \
--to=jh80.chung@samsung.com \
--cc=forbidden405@outlook.com \
--cc=peng.fan@nxp.com \
--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