From: Roger Quadros <rogerq@ti.com>
To: Julien Grall <julien.grall@arm.com>,
Juergen Gross <jgross@suse.com>,
xen-devel@lists.xen.org
Subject: Re: USB passthrough with Xen on ARM
Date: Tue, 12 Sep 2017 14:22:36 +0300 [thread overview]
Message-ID: <00a0cfaa-d007-e119-e154-b91246b51597@ti.com> (raw)
In-Reply-To: <d5f2db5d-ff9e-271a-e367-b340d1d4512c@arm.com>
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 12/09/17 13:57, Julien Grall wrote:
> Hi,
>
> On 12/09/17 11:00, Juergen Gross wrote:
>> On 12/09/17 10:13, Roger Quadros wrote:
>>> Hi,
>>>
>>> I'm running Xen v4.9 on DRA7 (OMAP5/ArmV7) with Linux kernel v3.14 (yikes!!) on dom0 and domU.
>>> I'm struggling to get USB passthrough working using pvUSB.
>>>
>>> My domU config file contains
>>> usb = 1
>>> usbctrl = ['type=qusb,version=2,ports=4', 'type=qusb,version=1, ports=4', ]
>>>
>>> I can see the vusb-0 and vusb-1 platform devices in /sys/devices
>>>
>>> And the following message on domU kernel log
>>> [ 1.849572] xenbus_probe_frontend: Device with no driver: device/vusb/0
>>> [ 1.849627] xenbus_probe_frontend: Device with no driver: device/vusb/1
>>>
>>> This means that there is no device driver for the vusb host controllers.
>>>
>>> What is the way forward? Do I need to apply some patches to the domU kernel to
>>> add support for the USB frontend HCD drivers?
>>
>> This is one mandatory step, yes. You'll need:
>>
>> https://lkml.org/lkml/2015/6/23/34
>> https://lkml.org/lkml/2015/6/23/36
>>
OK, after applying the above 2 patches to v4.12 kernel for domU I'm able to see the xen HCD driver
enumerate, but it times out most likely due to the missing pvusb backend.
[ 0.510149] vusb vusb-0: Xen USB2.0 Virtual Host Controller
[ 0.510192] vusb vusb-0: new USB bus registered, assigned bus number 1
[ 0.510811] hub 1-0:1.0: USB hub found
[ 0.510865] hub 1-0:1.0: 4 ports detected
[ 0.812721] vusb vusb-1: Xen USB1.1 Virtual Host Controller
[ 0.812760] vusb vusb-1: new USB bus registered, assigned bus number 2
[ 0.813356] hub 2-0:1.0: USB hub found
[ 0.813410] hub 2-0:1.0: 4 ports detected
...
[ 5.888997] xenbus_probe_frontend: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...
[ 35.919000] 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
[ 270.879130]
[ 270.884161] xenbus_probe_frontend: Timeout connecting to device: device/vusb/0 (local state 1, remote state 1)
[ 270.887059] xenbus_probe_frontend: Timeout connecting to device: device/vusb/1 (local state 1, remote state 1)
>> The question is whether this will be enough for you to make it work: the
>> pvusb backend is qemu based. I'm not sure this will just work on ARM.
>
> Backends in QEMU should just work with ARM. Although, I haven't tried the PVUSB one.
>
Newbie question now. How do I start the QEMU pvusb backend on dom0?
--
cheers,
-roger
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-12 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 8:13 USB passthrough with Xen on ARM Roger Quadros
2017-09-12 10:00 ` Juergen Gross
2017-09-12 10:52 ` Roger Quadros
2017-09-12 11:11 ` Juergen Gross
2017-09-12 10:57 ` Julien Grall
2017-09-12 11:22 ` Roger Quadros [this message]
2017-09-12 15:08 ` Julien Grall
2017-09-12 15:28 ` Juergen Gross
2017-09-13 10:33 ` Roger Quadros
2017-09-13 10:42 ` Juergen Gross
2017-09-13 10:48 ` Julien Grall
2017-09-13 11:02 ` Juergen Gross
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=00a0cfaa-d007-e119-e154-b91246b51597@ti.com \
--to=rogerq@ti.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.