Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752137AbbE0BdY (ORCPT ); Tue, 26 May 2015 21:33:24 -0400 Received: from mga14.intel.com ([192.55.52.115]:56051 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220AbbE0BdV (ORCPT ); Tue, 26 May 2015 21:33:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,502,1427785200"; d="scan'208";a="732176035" Message-ID: <55651EDD.8030002@linux.intel.com> Date: Wed, 27 May 2015 09:33:17 +0800 From: "Lu, Baolu" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: balbi@ti.com CC: David Cohen , Heikki Krogerus , Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall References: <1432294155-18039-1-git-send-email-baolu.lu@linux.intel.com> <20150522160845.GA31627@psi-dev26.jf.intel.com> <5562C000.8010302@linux.intel.com> <20150526145043.GC26599@saruman.tx.rr.com> In-Reply-To: <20150526145043.GC26599@saruman.tx.rr.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1407 Lines: 43 On 05/26/2015 10:50 PM, Felipe Balbi wrote: > Hi, > > On Mon, May 25, 2015 at 02:24:00PM +0800, Lu, Baolu wrote: >> >> On 05/23/2015 12:08 AM, David Cohen wrote: >>> Hi, >>> >>> On Fri, May 22, 2015 at 07:29:15PM +0800, Lu Baolu wrote: >>>> Phy drivers and the ulpi interface providers depend on the >>>> registeration of the ulpi bus. Ulpi registers the bus in >>>> module_init(). This could result in a load order issue, i.e. >>> It's still not an issue :( >>> I'd say "unnecessary probe delays". >> I managed to boot a kernel built from the top of Felipe's >> remotes/origin/next branch under an Ubuntu environment >> on Intel's Bay Trail tablet. >> >> The same panic (as I found in the Android environment previously) >> shows up as well. And if I replace module_init() with sys_initcall(), >> the panic disappears. > the problem is something else... Moving things around in the init levels > is just a workaround for another issue. Seems like there's some missing > EPROBE_DEFER somewhere. Yes, I agree. Heikki, I assume "missing EPROBE_DEFER issue" will be fixed by Sasha's patch. I will resend the patch with a new commit message. Thanks, Baolu > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/