From: "Lu, Baolu" <baolu.lu@linux.intel.com>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
qiuxu.zhuo@intel.com
Subject: Re: [PATCH v2 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall
Date: Fri, 22 May 2015 15:50:47 +0800 [thread overview]
Message-ID: <555EDFD7.6000605@linux.intel.com> (raw)
In-Reply-To: <555ED0CF.3060903@linux.intel.com>
On 05/22/2015 02:46 PM, Lu, Baolu wrote:
>
>
> On 05/22/2015 11:11 AM, David Cohen wrote:
>> On Thu, May 21, 2015 at 08:09:54PM -0700, David Cohen wrote:
>>> Hi,
>>>
>>> On Fri, May 22, 2015 at 10:07:05AM +0800, Lu Baolu wrote:
>>>> Many drivers and modules depend on ULPI bus registeration to
>>>> register ULPI interfaces and drivers. It's more appropriate
>>>> to register ULPI bus in subsys_initcall instead of module_init.
>>>>
>>>> Kernel panic has been reported with some kind of kernel config.
>>> Even though I agree subsys_initcall is better to register ulpi bus,
>>> it's
>>> still no excuse to have kernel panic. What about ULPI bus being
>>> compiled
>>> as module?
>
> No kernel panic if ULPI is built as a module.
>
>>> IMHO this is avoiding the proper kernel panic fix which should be
>>> failing gracefully (or defer probe) from tusb1210 driver.
>> Maybe I need to express myself better :)
>> IMHO we should not consider work done with this patch only. It's still
>> incomplete.
>
> I am with you on that we should know the real problem.
>
> I could go ahead with further debugging. Do you have any suggestions
> about which direction should I go?
I forgot to mention that the panic was found in an Android environment.
The kernel version is v4.1-rc3.
>
>>
>> Br, David
>
> Thank you,
> -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/
>>
>>
>
> --
> 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/
>
next prev parent reply other threads:[~2015-05-22 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 2:07 [PATCH v2 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall Lu Baolu
2015-05-22 3:09 ` David Cohen
2015-05-22 3:11 ` David Cohen
2015-05-22 6:46 ` Lu, Baolu
2015-05-22 7:50 ` Lu, Baolu [this message]
2015-05-22 16:12 ` David Cohen
2015-05-22 10:07 ` Heikki Krogerus
2015-05-24 16:25 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555EDFD7.6000605@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox