From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:51896)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1TfWDj-00074l-93
	for qemu-devel@nongnu.org; Mon, 03 Dec 2012 08:38:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1TfWDd-0004an-Fu
	for qemu-devel@nongnu.org; Mon, 03 Dec 2012 08:38:03 -0500
Received: from mx1.redhat.com ([209.132.183.28]:19789)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1TfWDd-0004ae-80
	for qemu-devel@nongnu.org; Mon, 03 Dec 2012 08:37:57 -0500
Message-ID: <50BCAB2C.6040106@redhat.com>
Date: Mon, 03 Dec 2012 14:37:48 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <1354417042-8818-1-git-send-email-andreas.faerber@web.de>
	<20121202103453.GA6029@pek-lwang0-d1> <50BB8164.9040308@web.de>
	<50BC4DEB.7080303@redhat.com> <20121203115812.GC6029@pek-lwang0-d1>
	<CAFEAcA9OQBWFsnWWLyVczaucJGQQL-adSkzxm7RdC-e9cqGoWw@mail.gmail.com>
	<20121203123821.GE6029@pek-lwang0-d1>
In-Reply-To: <20121203123821.GE6029@pek-lwang0-d1>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus
	EHCI
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: walimis <walimisdev@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, peter.crosthwaite@xilinx.com, Igor Mitsyanko <i.mitsyanko@samsung.com>, qemu-devel@nongnu.org, andreas.faerber@web.de, Vincent Palatin <vpalatin@chromium.org>

  Hi,

>>> Qemu doesn't provide some properties, such as "bus", to specify which EHCI controller the
>>> usb device attach to.  If we use "device" and "usb-storage", we never attach the usb
>>> device to the specified EHCI controller.
>>
>> -device certainly ought to let you specify a bus= property;
> 
> Sorry, I don't know the bus= property. 
> But why both EHCI controller are named "usb-bus.0"? How to distinguish the
> different usb usb?

That is the default name.  For usb controllers added via -device the bus
name is derived from the device name, i.e. '-device usb-ehci,id=ehci"
gives you a bus named "ehci.0".

For builtin devices that doesn't work though as you don't have to add
them manually.  Guess they should be explicitly named then by zynq_init().

cheers,
  Gerd