public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
To: dianders@chromium.org, jh80.chung@samsung.com
Cc: ulf.hansson@linaro.org, alim.akhtar@samsung.com,
	sonnyrao@chromium.org, abrestic@chromium.org, heiko@sntech.de,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: dw_mmc: HLE errors
Date: Mon, 23 Nov 2015 09:10:03 -0500	[thread overview]
Message-ID: <56531E3B.6060601@linaro.org> (raw)

Doug/Jaehoon,

Were there any follow ups to this thread [1] from March 30, 2015?
We are seeing HLE errors on 3.18 and we are trying to determine if a solution
was ever delivered.
On inspection, I can't find anything specific in recent kernels that address
this particular issue (was the actual root cause identified?)

I put together a possible work-around that avoids the HLE storm from occurring
for this specific SoC [2].
However we'd rather not merge this -or any other similar fix- if there is a
generic solution already that we can pick up from mainline.

thanks

Jorge




[1] https://lkml.org/lkml/headers/2015/3/30/423
[2]
https://github.com/96boards/linux/commit/fe8d7f714d420121cec460e69f6529044a2cb6d8

             reply	other threads:[~2015-11-23 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 14:10 Jorge Ramirez-Ortiz [this message]
2015-11-23 16:57 ` dw_mmc: HLE errors Doug Anderson
2015-11-23 17:29   ` Jorge Ramirez-Ortiz
2015-11-24  0:11     ` Jaehoon Chung
2015-11-24  1:55       ` Jorge Ramirez-Ortiz
2015-11-24  1:59         ` 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=56531E3B.6060601@linaro.org \
    --to=jorge.ramirez-ortiz@linaro.org \
    --cc=abrestic@chromium.org \
    --cc=alim.akhtar@samsung.com \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=sonnyrao@chromium.org \
    --cc=ulf.hansson@linaro.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