From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ivan T. Ivanov" Subject: Re: [PATCH v5 00/14] usb: phy: msm: Fixes, cleanups and DT support Date: Mon, 24 Mar 2014 18:27:25 +0200 Message-ID: <1395678445.30455.64.camel@iivanov-dev> References: <1394014430-26485-1-git-send-email-iivanov@mm-sol.com> <5318A34A.7070407@mm-sol.com> <531D9620.3050009@mm-sol.com> <531F0376.2000403@mm-sol.com> <531F1C40.5090403@mm-sol.com> <1395674722.30455.54.camel@iivanov-dev> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from ns.mm-sol.com ([37.157.136.199]:43944 "EHLO extserv.mm-sol.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752521AbaCXQ2e (ORCPT ); Mon, 24 Mar 2014 12:28:34 -0400 In-Reply-To: <1395674722.30455.54.camel@iivanov-dev> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Tim Bird Cc: Bjorn Andersson , linux-arm-msm@vger.kernel.org On Mon, 2014-03-24 at 17:25 +0200, Ivan T. Ivanov wrote: > > > 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. It was small, but important difference. There is MUX, which selects which port to be used by USB2.0 controller. On DragonBord8074 it should be second one. This is what "qcom,phy-num" DT property supposed to select. Unfortunately this is not enough. Register 0xfd4ab000 should contain value different than zero. Example of this can be seen in qcom,dwc3 driver [1]. Regards, Ivan [1] http://thread.gmane.org/gmane.linux.documentation/14549 > > > > > Thanks for any info you can provide. > > -- Tim >