From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Subject: Re: [PATCH v5 00/14] usb: phy: msm: Fixes, cleanups and DT support
Date: Mon, 24 Mar 2014 17:25:22 +0200
Message-ID: <1395674722.30455.54.camel@iivanov-dev>
References: <1394014430-26485-1-git-send-email-iivanov@mm-sol.com>
	 <CA+bK7J5ABQ9WcSKkLf=DfTEv3xb_ZKDYgjHTqwLbapYr63ivxQ@mail.gmail.com>
	 <5318A34A.7070407@mm-sol.com>
	 <CA+bK7J5oGKEvMp1Eq0TUprWrx+xc66o=swmVGkmosuZbQd3-hQ@mail.gmail.com>
	 <531D9620.3050009@mm-sol.com> <531F0376.2000403@mm-sol.com>
	 <531F1C40.5090403@mm-sol.com>
	 <CA+bK7J6VF=soYQCf4dJuyGHZ0NdSYb2bsHYaimHm6PmVLcjYJQ@mail.gmail.com>
	 <CA+bK7J651ZFrJT3sH8sjChcsCLv4UeLHwgB=6bgAhjU4UuHxCw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-arm-msm-owner@vger.kernel.org>
Received: from ns.mm-sol.com ([37.157.136.199]:39375 "EHLO extserv.mm-sol.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752754AbaCXP0b (ORCPT <rfc822;linux-arm-msm@vger.kernel.org>);
	Mon, 24 Mar 2014 11:26:31 -0400
In-Reply-To: <CA+bK7J651ZFrJT3sH8sjChcsCLv4UeLHwgB=6bgAhjU4UuHxCw@mail.gmail.com>
Sender: linux-arm-msm-owner@vger.kernel.org
List-Id: linux-arm-msm@vger.kernel.org
To: Tim Bird <tbird20d@gmail.com>
Cc: Bjorn Andersson <bjorn@kryo.se>, linux-arm-msm@vger.kernel.org


Hi,

On Fri, 2014-03-21 at 08:20 -0700, Tim Bird wrote:
> Here's some more progress.
> 
> I can successfully get the dragonboard to establish a USB connection
> to the host (have the host enumerate it) with this code, but only if I
> first boot the machine to fastboot, then boot the kernel from ramboot.
>  When I boot the kernel from RAM, the device comes right up, after the
> g_zero module is loaded.

Same here.

> 
> Ivan,
> 
> Can you tell me if you are booting from RAM or from flash?  

I am using boot from RAM.

> If you are
> booting from RAM (doing something like 'fastboot boot boot.img' to
> start the kernel), then could you try instead writing the kernel to
> flash and booting directly to it, without first going into fastboot,
> and let me know what happens.  In my situation, clearly there's some
> element of hardware setup that fastboot does that my kernel can rely
> upon for working, that my kernel alone does not perform.

I will look what aboot is doing and add same sequence to driver.

Thanks.
Ivan

> 
> Thanks for any info you can provide.
>  -- Tim