[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <529C76AF.10106@linutronix.de>
Date: Mon, 02 Dec 2013 13:01:51 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Roger Quadros <rogerq@...com>
CC: Michael Trimarchi <michael@...rulasolutions.com>,
Felipe Balbi <balbi@...com>, lee.jones@...aro.org,
sameo@...ux.intel.com, tomi.valkeinen@...com,
Stefan Roese <sr@...x.de>, ljkenny.mailinglists@...il.com,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] mfd: omap-usb-host: Fix USB device detection problems
on OMAP4 Panda
- stable@...r.kernel.org since they probably don't care about this
unless the patch is merged.
On 12/02/2013 10:41 AM, Roger Quadros wrote:
> Michael,
>
> On 11/29/2013 05:32 PM, Michael Trimarchi wrote:
>> Hi Roger
>>
>> On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros <rogerq@...com> wrote:
>>> With u-boot 2013.10, USB devices are sometimes not detected
>>> on OMAP4 Panda. To make us independent of what bootloader does
>>> with the USB Host module, we must RESET it to get it to a known
>>> good state. This patch Soft RESETs the USB Host module.
>>>
>>
>> Do you think that we need something similar of usb musb?
>> I have seen the OTG_SYSCONFIG is touched in uboot and
>> only readed in omap2430.c.
>
> I'm not sure about musb. Maybe Sebastian/Felipe have better idea.
> In general I believe that all modules must be reset by the kernel.
>
based on the code at the bottom it touches the first few register(s)
sysconfig. Isn't hwmod actually doing this idle stuff and resting the
device during boot?
> cheers,
> -roger
>>
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists