From: Brian Norris <briannorris@chromium.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: linux-mmc@vger.kernel.org, linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>,
amstan@chromium.org, Ziyuan Xu <xzy.xu@rock-chips.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [REGRESSION 4.10] dw_mmc: failures on Rockchip rk3288 veyron boards
Date: Wed, 29 Mar 2017 18:42:31 -0700 [thread overview]
Message-ID: <20170330014230.GA21467@google.com> (raw)
In-Reply-To: <6d87cb71-1339-0dc9-e071-1c117f541881@rock-chips.com>
On Thu, Mar 30, 2017 at 09:32:22AM +0800, Shawn Lin wrote:
> Hi Brian,
>
> On 2017/3/30 9:17, Brian Norris wrote:
> >Hi all,
> >
> >I haven't managed to get as far as a bugfix for this, but I've bisected
> >some issues seen on v4.10+ with a Chromebook of the Veyron family (Jaq,
> >in particular). v4.9 works fine.
>
> Does your v4.10+ kernel have these commits?
By "4.10+", I meant that pure 4.10 is broken, as are all subsequent
versions (e.g., 4.11-rc1).
> commit e9748e0364fe82dc037d22900ff13a62d04518bf
> Author: Ziyuan Xu <xzy.xu@rock-chips.com>
> Date: Tue Jan 17 09:22:56 2017 +0800
>
> mmc: dw_mmc: force setup bus if active slots exist
>
>
> commit df9bcc2bc0a1f8d2963bd916698268fb2470713b
> Author: Joonyoung Shim <jy0922.shim@samsung.com>
> Date: Fri Nov 25 12:47:15 2016 +0900
>
> mmc: dw_mmc: add missing codes for runtime resume
'git describe' tells me these are in 4.10-rc1 and -rc6. So yes.
> commit ce69e2fea093b7fa3991c87849c4955cd47796c9
> Author: Shawn Lin <shawn.lin@rock-chips.com>
> Date: Tue Jan 17 09:22:55 2017 +0800
>
> mmc: dw_mmc: silent verbose log when calling from PM context
'git describe' tells me this is in 4.11-rc1, so no.
Brian
next prev parent reply other threads:[~2017-03-30 1:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 1:17 [REGRESSION 4.10] dw_mmc: failures on Rockchip rk3288 veyron boards Brian Norris
[not found] ` <20170330011709.GA110687-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-03-30 1:32 ` Shawn Lin
2017-03-30 1:42 ` Brian Norris [this message]
2017-03-30 2:18 ` Eddie Cai
2017-03-30 2:53 ` Brian Norris
2017-03-30 5:11 ` Jaehoon Chung
2017-04-06 22:04 ` Brian Norris
2017-04-07 4:59 ` Jaehoon Chung
2017-04-07 6:50 ` Shawn Lin
2017-04-07 7:38 ` Jaehoon Chung
2017-04-10 23:35 ` Doug Anderson
2017-04-11 10:21 ` Ulf Hansson
2017-04-11 22:57 ` Doug Anderson
2017-04-12 0:54 ` Shawn Lin
2017-04-12 16:12 ` Doug Anderson
2017-04-13 7:17 ` Ulf Hansson
2017-04-13 15:45 ` Doug Anderson
2017-04-13 8:28 ` Shawn Lin
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=20170330014230.GA21467@google.com \
--to=briannorris@chromium.org \
--cc=amstan@chromium.org \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.com \
--cc=xzy.xu@rock-chips.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