From: Heiko Stuebner <heiko@sntech.de>
To: Doug Anderson <dianders@chromium.org>,
Shawn Lin <shawn.lin@rock-chips.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sonny Rao <sonnyrao@chromium.org>,
Alexandru Stan <amstan@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors
Date: Wed, 18 May 2016 20:01:44 +0200 [thread overview]
Message-ID: <9061286.nTNVjb4bva@phil> (raw)
In-Reply-To: <CAD=FV=UoT2GRYWJWXEn_ccvKGgC+PzQM_BCtLHAa7jxzbaQ9SA@mail.gmail.com>
Am Mittwoch, 18. Mai 2016, 10:37:52 schrieb Doug Anderson:
> Note: I'd be very curious if your problems get better if you disable
> the "grf_force_jtag" bit in the GRF. If you're using the builtin card
> detect and you use the boot default of "grf_force_jtag" then your pins
> will be unmuxed behind your back when the card is ejected. This could
> be causing the dw_mmc controller to get confused.
On the rk3288, we saw issues with the jtag/sdmmc function and thus disabled
that altogether in [0]. Not sure if that is a similar problem for you.
Heiko
[0]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c9b75d51c940c25587a2ad72ec7ec60490abfb6c
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors
Date: Wed, 18 May 2016 20:01:44 +0200 [thread overview]
Message-ID: <9061286.nTNVjb4bva@phil> (raw)
In-Reply-To: <CAD=FV=UoT2GRYWJWXEn_ccvKGgC+PzQM_BCtLHAa7jxzbaQ9SA@mail.gmail.com>
Am Mittwoch, 18. Mai 2016, 10:37:52 schrieb Doug Anderson:
> Note: I'd be very curious if your problems get better if you disable
> the "grf_force_jtag" bit in the GRF. If you're using the builtin card
> detect and you use the boot default of "grf_force_jtag" then your pins
> will be unmuxed behind your back when the card is ejected. This could
> be causing the dw_mmc controller to get confused.
On the rk3288, we saw issues with the jtag/sdmmc function and thus disabled
that altogether in [0]. Not sure if that is a similar problem for you.
Heiko
[0]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c9b75d51c940c25587a2ad72ec7ec60490abfb6c
next prev parent reply other threads:[~2016-05-18 18:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 15:48 [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors Doug Anderson
2015-03-10 15:48 ` Doug Anderson
2015-03-13 11:30 ` Jaehoon Chung
2015-03-13 11:30 ` Jaehoon Chung
2015-03-13 20:27 ` Doug Anderson
2015-03-13 20:27 ` Doug Anderson
2015-03-16 5:56 ` Jaehoon Chung
2015-03-16 5:56 ` Jaehoon Chung
2015-03-30 0:55 ` Jaehoon Chung
2015-03-30 0:55 ` Jaehoon Chung
2015-03-30 15:47 ` Doug Anderson
2015-03-30 15:47 ` Doug Anderson
2016-05-18 0:47 ` Doug Anderson
2016-05-18 0:47 ` Doug Anderson
2016-05-18 1:59 ` Shawn Lin
2016-05-18 1:59 ` Shawn Lin
2016-05-18 4:12 ` Doug Anderson
2016-05-18 4:12 ` Doug Anderson
2016-05-18 9:14 ` Shawn Lin
2016-05-18 9:14 ` Shawn Lin
2016-05-18 17:37 ` Doug Anderson
2016-05-18 17:37 ` Doug Anderson
2016-05-18 18:01 ` Heiko Stuebner [this message]
2016-05-18 18:01 ` Heiko Stuebner
2016-05-19 11:31 ` Shawn Lin
2016-05-19 11:31 ` Shawn Lin
2016-05-19 13:07 ` Jaehoon Chung
2016-05-19 13:07 ` Jaehoon Chung
2016-05-26 2:23 ` Shawn Lin
2016-05-26 2:23 ` Shawn Lin
2016-05-26 3:59 ` Jaehoon Chung
2016-05-26 3:59 ` Jaehoon Chung
2016-05-26 4:07 ` Shawn Lin
2016-05-26 4:07 ` Shawn Lin
2016-05-18 2:08 ` Jaehoon Chung
2016-05-18 2:08 ` Jaehoon Chung
2016-05-18 4:13 ` Doug Anderson
2016-05-18 4:13 ` Doug Anderson
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=9061286.nTNVjb4bva@phil \
--to=heiko@sntech.de \
--cc=alim.akhtar@samsung.com \
--cc=amstan@chromium.org \
--cc=dianders@chromium.org \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.