Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 May 2011 14:21:35 +0200
From:      Damjan Marion <damjan.marion@gmail.com>
To:        Hans Petter Selasky <hselasky@c2i.net>
Cc:        freebsd-usb@freebsd.org
Subject:   Re: Timeouts on Marvell EHCI (FreeBSD-arm)
Message-ID:  <6E1BE65D-E041-4470-A0FD-581E667BA20F@gmail.com>
In-Reply-To: <201105021358.44990.hselasky@c2i.net>
References:  <58C62437-2759-47DE-83BB-1F9F377AB212@gmail.com> <201105021333.39129.hselasky@c2i.net> <87A80DBE-517D-44E6-B769-E0F338E22EF8@gmail.com> <201105021358.44990.hselasky@c2i.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On May 2, 2011, at 1:58 PM, Hans Petter Selasky wrote:

> On Monday 02 May 2011 13:51:18 Damjan Marion wrote:
>> On May 2, 2011, at 1:33 PM, Hans Petter Selasky wrote:
>>> On Monday 02 May 2011 12:58:02 Damjan Marion wrote:
>>>> Hi,
>>>>=20
>>>> I'm trying to bring up FreeBSD on Marvell 88F5181L based ARM board =
and I
>>>> have problem with EHCI driver. EHCI controller is detected but it =
fails
>>>> to activate connected device.
>>>>=20
>>>> I will appreciate any hints how to fix this. Output follows....
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Damjan
>>>=20
>>> Can you set:
>>>=20
>>> hw.usb.uhub.debug=3D15
>>>=20
>>> and
>>>=20
>>> hw.usb.debug=3D15
>>>=20
>>> --HPS
>>=20
>> Here it is, thanks....
>>=20
>>=20
>> ehci0: <Marvell Integrated USB 2.0 controller> mem =
0xf1050000-0xf1050fff
>> irq 17,16 on simplebus0 usbus0: EHCI version 1.0
>> usbus0: set host controller mode
>> usbus0: <Marvell Integrated USB 2.0 controller> on ehci0
>> usb_needs_explore:
>> usb_needs_explore: No root HUB
>> pcib0: <Marvell Integrated PCI/PCI-E Controller> mem =
0xf1030000-0xf1031fff
>> irq 11 on fdtbus0 pci0: <PCI bus> on pcib0
>> Timecounters tick every 1.000 msec
>> usbus0: 480Mbps High Speed USB v2.0
>> usb_alloc_device: parent_dev=3D0xc13b1300, bus=3D0xc1393c78, =
parent_hub=3D0,
>> depth=3D0, port_index=3D0, port_no=3D1, speed=3D3, usb_mode=3D0
>> usb_set_device_state: udev 0xc13ba800 state DETACHED -> POWERED
>> usbd_req_set_address: setting device address=3D1
>> usbd_do_request_flags: udev=3D0xc13ba800 bmRequestType=3D0x00 =
bRequest=3D0x05
>> wValue=3D0x0001 wIndex=3D0x0000 wLength=3D0x0000 =
usbd_do_request_flags: Handle
>> Request function is set
>> Root mount waiting for: usbus0
>> usb_set_device_state: udev 0xc13ba800 state POWERED -> ADDRESSED
>> usbd_setup_device_desc: Minimum MaxPacketSize is large enough to hold =
the
>> complete device descriptor usbd_req_get_device_desc:
>> usbd_req_get_desc: id=3D0, type=3D1, index=3D0, max_len=3D18
>> usbd_do_request_flags: udev=3D0xc13ba800 bmRequestType=3D0x80 =
bRequest=3D0x06
>> wValue=3D0x0100 wIndex=3D0x0000 wLength=3D0x0012 =
usbd_do_request_flags: Handle
>> Request function is set
>> usbd_setup_device_desc: adding unit addr=3D1, rev=3D200, class=3D9, =
subclass=3D0,
>> protocol=3D1, maxpacket=3D64, len=3D18, speed=3D3 usbd_req_get_desc: =
id=3D0, type=3D3,
>> index=3D0, max_len=3D4
>> usbd_do_request_flags: udev=3D0xc13ba800 bmRequestType=3D0x80 =
bRequest=3D0x06
>> wValue=3D0x0300 wIndex=3D0x0000 wLength=3D0x0002 =
usbd_do_request_flags: Handle
>=20
> Hi,
>=20
> I looks like no EHCI interrupts are generated. Try calling the EHCI =
interrupt=20
> every 100ms and see what happens.
>=20
> --HPS

Thanks, great hint.

Interrupts were defined in wrong order in FDT. Correct is:
ehci0: <Marvell Integrated USB 2.0 controller> mem 0xf1050000-0xf1050fff =
irq 16,17 on simplebus0

Damjan=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6E1BE65D-E041-4470-A0FD-581E667BA20F>