qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: hkran <hkran@linux.vnet.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: hkran <hkran@vnet.linux.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] usb-hub: wakeup on attach
Date: Thu, 03 Nov 2011 17:20:32 +0800	[thread overview]
Message-ID: <4EB25CE0.9060703@linux.vnet.ibm.com> (raw)
In-Reply-To: <4EB253BE.8070300@redhat.com>

On 11/03/2011 04:41 PM, Gerd Hoffmann wrote:
> On 11/03/11 07:01, hkran wrote:
>> On 11/02/2011 08:56 PM, Gerd Hoffmann wrote:
>>>     Hi,
>>>
>>>>>     static void usb_hub_detach(USBPort *port1)
>>>> pulled, In what cases, the usb hub will be suspended? and how to tell it
>>>> happened? thanks.
>>> The guest enables the remote-wakeup feature.  'lspci -v' (within the
>>> guest) shows it.
>>>
>>> cheers,
>>>     Gerd
>>>
>> I use the param "-usb -usbdevice tablet" to start qemu  and then usb_del
>> tablet via monitor console after getting qemu up.
>> I saw this by entering lsusb -v
>>
>> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Device Descriptor:
>>    bLength                18
>>    bDescriptorType         1
>>    bcdUSB               1.10
>>    bDeviceClass            9 Hub
>>    bDeviceSubClass         0 Unused
>>    bDeviceProtocol         0 Full speed (or root) hub
>>    bMaxPacketSize0        64
>>    idVendor           0x1d6b Linux Foundation
>>    idProduct          0x0001 1.1 root hub
>>    bcdDevice            2.06
>>    iManufacturer           3 Linux 2.6.32-131.0.15.el6.x86_64 uhci_hcd
>>    iProduct                2 UHCI Host Controller
>>    iSerial                 1 0000:00:01.2
>> ..........................
>> Hub Descriptor:
>>    bLength               9
>>    bDescriptorType      41
>>    nNbrPorts             2
>>    wHubCharacteristic 0x000a
>>      No power switching (usb 1.0)
>>      Per-port overcurrent protection
>>    bPwrOn2PwrGood        1 * 2 milli seconds
>>    bHubContrCurrent      0 milli Ampere
>>    DeviceRemovable    0x00
>>    PortPwrCtrlMask    0xff
>>   Hub Port Status:
>>     Port 1: 0000.0100 power
>>     Port 2: 0000.0100 power
>> Device Status:     0x0003
>>    Self Powered
>>    Remote Wakeup Enabled
>>
>> (It seems that the Remote-wakeup feature has been enabled)
>> There are two ports with the status "power",  and I do not know how to
>> make it suspended yet. Can you help more ?
> That is the root hub created by the linux kernel, not the hub emulated
> by qemu.  If you hook up just a single device no hob is needed.
>
> cheers,
>    Gerd
>
Yes, it is. After I usb_add a storage a 8-port hub emulated is added :

lsusb
Bus 001 Device 004: ID 0000:7777
Bus 001 Device 003: ID 0000:0000
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Device 003 is the hub and Device 004 is my storage

lsusb -s 3 -v:

Bus 001 Device 003: ID 0000:0000
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            9 Hub
   bDeviceSubClass         0 Unused
   bDeviceProtocol         0 Full speed (or root) hub
   bMaxPacketSize0         8
   idVendor           0x0000
   idProduct          0x0000
   bcdDevice            1.01
   iManufacturer           1 QEMU 0.15.50
   iProduct                2 QEMU USB Hub
   iSerial                 3 314159
   bNumConfigurations      1
...........................................
     iConfiguration          0
     bmAttributes         0xe0
       Self Powered
       Remote Wakeup
     MaxPower                0mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         9 Hub
       bInterfaceSubClass      0 Unused
       bInterfaceProtocol      0 Full speed (or root) hub
       iInterface              0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0002  1x 2 bytes
         bInterval             255
Hub Descriptor:
   bLength              10
   bDescriptorType      41
   nNbrPorts             8
   wHubCharacteristic 0x000a
     No power switching (usb 1.0)
     Per-port overcurrent protection
   bPwrOn2PwrGood        1 * 2 milli seconds
   bHubContrCurrent      0 milli Ampere
   DeviceRemovable    0x00 0x00
   PortPwrCtrlMask    0xff 0x00
  Hub Port Status:
    Port 1: 0000.0103 power enable connect
    Port 2: 0000.0100 power
    Port 3: 0000.0100 power
    Port 4: 0000.0100 power
    Port 5: 0000.0100 power
    Port 6: 0000.0100 power
    Port 7: 0000.0100 power
    Port 8: 0000.0100 power
Device Status:     0x0001
   Self Powered

my storage is connected to the port 1.

after usb_del, all the hub port status will turn to power. how should i 
do next to get it to be suspended?thanks.

  reply	other threads:[~2011-11-03  9:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 14:56 [Qemu-devel] [PULL] usb patch queue Gerd Hoffmann
2011-11-01 14:56 ` [Qemu-devel] [PATCH 1/3] usb-hub: wakeup on attach Gerd Hoffmann
2011-11-02  9:38   ` hkran
2011-11-02 12:56     ` Gerd Hoffmann
2011-11-03  6:01       ` hkran
2011-11-03  8:41         ` Gerd Hoffmann
2011-11-03  9:20           ` hkran [this message]
2011-11-10  3:45   ` hkran
2011-11-22 12:23     ` Gerd Hoffmann
2011-11-01 14:56 ` [Qemu-devel] [PATCH 2/3] usb: change VID/PID for usb-hub and usb-msd to prevent conflict Gerd Hoffmann
2011-11-01 15:29   ` Andreas Färber
2011-11-01 15:40     ` Gerd Hoffmann
2011-11-01 14:56 ` [Qemu-devel] [PATCH 3/3] usb-host: fix host close Gerd Hoffmann
2011-11-01 18:13 ` [Qemu-devel] [PULL] usb patch queue Anthony Liguori

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=4EB25CE0.9060703@linux.vnet.ibm.com \
    --to=hkran@linux.vnet.ibm.com \
    --cc=hkran@vnet.linux.ibm.com \
    --cc=kraxel@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).