From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaehoon Chung Subject: Re: [GIT PULL] Update dw-mmc controller - regression!? Date: Tue, 12 Jul 2016 17:29:50 +0900 Message-ID: <5784AA7E.8060109@samsung.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mailout4.samsung.com ([203.254.224.34]:45355 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750787AbcGLIaE (ORCPT ); Tue, 12 Jul 2016 04:30:04 -0400 Received: from epcpsbgr2.samsung.com (u142.gpu120.samsung.co.kr [203.254.230.142]) by mailout4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0OA701RNA0XQDJ10@mailout4.samsung.com> for linux-mmc@vger.kernel.org; Tue, 12 Jul 2016 17:29:50 +0900 (KST) In-reply-to: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Ulf Hansson Cc: "linux-mmc@vger.kernel.org" , Shawn Lin , Jerome Forissier , "sw0312.kim@samsung.com" , Doug Anderson , Ben Dooks , Jae hoon Chung Hi Ulf, On 07/12/2016 05:28 PM, Ulf Hansson wrote: > On 6 July 2016 at 18:19, Ulf Hansson wrote: >> On 29 June 2016 at 03:42, Jaehoon Chung wro= te: >>> Dear Ulf, >>> >>> Could you pull these patches into your repository (next branch)? >>> >>> Best Regards, >>> Jaehoon Chung >>> >>> The following changes since commit 466780648db4aed7722de91e9d9749c6= c5969327: >>> >>> mmc: sh_mmcif: Use a 10s timeout in the error recovery path (2016= -06-27 11:19:29 +0200) >>> >>> are available in the git repository at: >>> >>> https://github.com/jh80chung/dw-mmc.git for-ulf >>> >>> for you to fetch changes up to 545585efee538cac5202b415a3d0c12b4556= e96f: >>> >>> mmc: dw_mmc: fix unmap sg twice when finding data err (2016-06-29= 10:39:05 +0900) >>> >>> ---------------------------------------------------------------- >>> Ben Dooks (1): >>> mmc: dw_mmc: fix 32bit little-endian access of des1 field >>> >>> Doug Anderson (2): >>> mmc: dw_mmc: Consider HLE errors to be data and command error= s >>> mmc: dw_mmc: Wait for data transfer after response errors. >>> >>> Jaehoon Chung (4): >>> mmc: dw_mmc: exynos: fix the NULL pointer dereference error >>> mmc: dw_mmc: remove the quirks flags >>> mmc: dw_mmc: add the card write threshold for HS400 mode >>> mmc: dw_mmc: prevent to set the wrong value >>> >>> J=C3=A9r=C3=B4me Forissier (1): >>> mmc: dw_mmc: k3: add MMC_CAP_CMD23 >>> >>> Seung-Woo Kim (1): >>> mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus() >>> >>> Shawn Lin (3): >>> mmc: dw_mmc: remove redundant of set_bit and clear_bit >>> mmc: dw_mmc: check card present before starting request >>> mmc: dw_mmc: fix unmap sg twice when finding data err >>> >>> drivers/mmc/host/dw_mmc-exynos.c | 2 +- >>> drivers/mmc/host/dw_mmc-k3.c | 7 ++ >>> drivers/mmc/host/dw_mmc-rockchip.c | 3 - >>> drivers/mmc/host/dw_mmc.c | 157 ++++++++++++++++++++++---= ------------ >>> drivers/mmc/host/dw_mmc.h | 10 +-- >>> include/linux/mmc/dw_mmc.h | 9 --- >>> 6 files changed, 108 insertions(+), 80 deletions(-) >> >> Thanks Jaehoon, pulled into my next branch! >=20 >=20 > Reported by kernelci, It seems like some of these patches are causing > the exynos5250-arndale to fail to boot. > I looked briefly at the logs and the bisect report (which isn't > complete) and it turns out that the eMMC card at mmc0 isn't detected > properly. >=20 > Here's the boot summary (it turns out there are more boards failing, > don't know if all are related to dw_mmc, yet): > https://kernelci.org/boot/all/job/ulfh/kernel/v4.7-rc5-92-g4e01b578ad= e9/ >=20 > Here's the bootlog: > https://storage.kernelci.org/ulfh/v4.7-rc5-92-g4e01b578ade9/arm-multi= _v7_defconfig+CONFIG_EFI=3Dy/lab-baylibre-seattle/boot-exynos5250-arnda= le.txt >=20 > Please, could any of you dw_mmc experts have a look at this as soon a= s > possible!? Sure, I will check now..thanks for reporting this. Best Regards, Jaehoon Chung >=20 > Kind regards > Uffe > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" = in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >=20 >=20 >=20