From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753804AbcEBNkR (ORCPT ); Mon, 2 May 2016 09:40:17 -0400 Received: from lb2-smtp-cloud3.xs4all.net ([194.109.24.26]:34572 "EHLO lb2-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752779AbcEBNkJ (ORCPT ); Mon, 2 May 2016 09:40:09 -0400 Subject: Re: [RFT PATCH 0/3] usb: misc: usb3503: Fix missing device when TFTP booting To: Krzysztof Kozlowski References: <1461927591-7864-1-git-send-email-k.kozlowski@samsung.com> <57247E50.1020000@xs4all.nl> <20160501131746.GA16766@kozik-lap> <57260E1E.70205@xs4all.nl> <57262844.7060809@xs4all.nl> <20160501164252.GA3581@kozik-lap> Cc: Kukjin Kim , Chanwoo Choi , Liam Girdwood , Mark Brown , Greg Kroah-Hartman , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-usb@vger.kernel.org, linux.amoon@gmail.com, tjakobi@math.uni-bielefeld.de, m.szyprowski@samsung.com, Bartlomiej Zolnierkiewicz From: Hans Verkuil Message-ID: <572758B1.60202@xs4all.nl> Date: Mon, 2 May 2016 15:40:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160501164252.GA3581@kozik-lap> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/01/16 18:42, Krzysztof Kozlowski wrote: > On Sun, May 01, 2016 at 06:01:08PM +0200, Hans Verkuil wrote: >>> Sorry, I meant the hanging issue I got in 4.6, not the ethernet issue. >>> I get the same problem with linux-next. Can you mail me the .config you are using? >> >> Never mind. >> >>> After some more testing I don't think it is hanging, instead it seems that the mmc >>> isn't enabled/found and so it just sits waiting for the root partition to appear. >> >> That was fun. There are two problems that both caused the boot to end at the same >> place: first of all the root partition is now called mmcblk1p1 instead of mmcblk0p1 >> in 4.6, so it was just waiting for the root partition to appear. Nothing to do with >> your patch series, just unexpected. > > Yes, annoying issue and unfortunately this is known... recommended > solution is to use root=PARTUUID=xxxx (you can get the PARTUUID with > blkid)... or replace the mmc device. > >> The second is that enabling CONFIG_VIDEO_S5P_FIMC causes the boot to hang at that >> same place. I suspect there is a deadlock somewhere. I'm digging deeper into that >> but again, unrelated to your patch series. >> >> Anyway, after disabling that config option I was finally able to test your patch >> series: >> >> Tested-by: Hans Verkuil BTW, one thing I noticed is that to have u-boot detect the network device I need to call 'usb reset' twice. This is with u-boot 2016.1 release. Not a big deal, but I wondered if you see the same. Regards, Hans