public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-mmc@vger.kernel.org, viresh.linux@gmail.com,
	g.liakhovetski@gmx.de, vinod.koul@linux.intel.com,
	s.hauer@pengutronix.de, cjb@laptop.org,
	fabio.estevam@freescale.com, gcembed@gmail.com
Subject: Re: [PATCH v2] mmc: mxcmmc: fix bug that may block a data transfer forever.
Date: Thu, 21 Feb 2013 13:57:55 +0100	[thread overview]
Message-ID: <20130221135755.44440261@crub> (raw)
In-Reply-To: <CACKLOr0vTr=8F7Ly_bQCL5FLWhn8hqmsLaUeGfDUMM7OaEqWOg@mail.gmail.com>

Hi,

On Thu, 21 Feb 2013 13:32:08 +0100
javier Martin <javier.martin@vista-silicon.com> wrote:
...
> It was tested executing a loop with bonnie++ for a week.
> I didn't notice the race condition. Have you had real issues or just
> found  it by analysing the code?

I've had real issues, but my setup is different. I'm using this mxcmmc
driver with extensions on mpc5121e (with different DMA controller/driver).
It is quite difficult to reproduce the issue on my test system. I've also
an i.mx31 based pcm037 board but the SD-Card slot is broken on it, so I
can not test the driver on i.mx31.

Thanks,

Anatolij

  reply	other threads:[~2013-02-21 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 10:43 [PATCH v2] mmc: mxcmmc: fix bug that may block a data transfer forever Javier Martin
2012-09-10  7:47 ` Sascha Hauer
2012-09-19  5:52   ` Chris Ball
2012-09-14  2:52 ` Vinod Koul
2012-09-14 12:50   ` javier Martin
2013-02-19 14:14 ` Anatolij Gustschin
2013-02-21 12:32   ` javier Martin
2013-02-21 12:57     ` Anatolij Gustschin [this message]
2013-02-21 15:49   ` Fabio Estevam
2013-03-14 19:58     ` Anatolij Gustschin

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=20130221135755.44440261@crub \
    --to=agust@denx.de \
    --cc=cjb@laptop.org \
    --cc=fabio.estevam@freescale.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=gcembed@gmail.com \
    --cc=javier.martin@vista-silicon.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=vinod.koul@linux.intel.com \
    --cc=viresh.linux@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