qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 10/11] usb-uhci: Add support for being a companion controller
Date: Wed, 29 Jun 2011 14:29:52 +0200	[thread overview]
Message-ID: <4E0B1AC0.1030002@redhat.com> (raw)
In-Reply-To: <4E0B0A32.7070907@redhat.com>

   Hi,

> I agree, but there is a reason why I went with a usb_bus_register_companion
> function instead of with a usb_bus_register_companion_port function, the
> uhci controller needs to know how many companion controllers it has
> (to report this in one of its registers). When we're registering
> ports 1 by 1, it does not know.

Good point.

> Thinking more about this I think that the best approach would be to move
> the port setup code (setting index, ops, speedmask, etc.) to
> usb_bus_register_companion, and keep doing the entire registration
> of all the ports in one single call. Would that work for you?

Yes.  Or have some helper function to fill the USBPort struct (which 
could be called by usb_register_port too).  I just don't like the 
initialization being done by the host adapter in one case and by the usb 
core code in the other case as this is a bit confusing and makes the 
code harder to read.

> This still leaves the building of the port pointers array, we could
> pass in a stride parameter to usb_bus_register_companion and make it
> build that list too, I'm not sure if that is a good idea though?

Passing in the pointer array is fine with me.

cheers,
   Gerd

  reply	other threads:[~2011-06-29 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 19:32 [Qemu-devel] RFC/PULL: usb: add support for companion controllers Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 01/11] usb: Add a register_companion USB bus op Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 02/11] usb: Make port wakeup and complete ops take a USBPort instead of a Device Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 03/11] usb: Replace device_destroy bus op with a child_detach port op Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 04/11] usb-ehci: drop unused num-ports state member Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 05/11] usb-ehci: Connect Status bit is read only, don't allow changing it by the guest Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 06/11] usb-ehci: cleanup port reset handling Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 07/11] usb: assert on calling usb_attach(port, NULL) on a port without a dev Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 08/11] usb-ehci: Fix handling of PED and PEDC port status bits Hans de Goede
2011-06-25  0:15   ` Brad Hards
2011-06-25  6:08     ` Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 09/11] usb-ehci: Add support for registering companion controllers Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 10/11] usb-uhci: Add support for being a companion controller Hans de Goede
2011-06-29 10:57   ` Gerd Hoffmann
2011-06-29 11:19     ` Hans de Goede
2011-06-29 12:29       ` Gerd Hoffmann [this message]
2011-06-30 11:09         ` Hans de Goede
2011-06-24 19:32 ` [Qemu-devel] [PATCH 11/11] usb-ohci: " Hans de Goede

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=4E0B1AC0.1030002@redhat.com \
    --to=kraxel@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).