From: Lan Tianyu <tianyu.lan@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
lenb@kernel.org, gregkh@linuxfoundation.org,
linux-acpi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC PATCH] usb/acpi: Add support usb port power off mechanism for device fixed on the motherboard
Date: Sat, 12 May 2012 02:18:54 +0800 [thread overview]
Message-ID: <4FAD580E.2010301@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1205111302080.1865-100000@iolanthe.rowland.org>
On 2012年05月12日 01:44, Alan Stern wrote:
> On Sat, 12 May 2012, Lan Tianyu wrote:
>
>> The power saving depends on devices. I test a usb3.0 ssd. The power saving of
>> power off is about 2.2w more than just selective suspend. In theory, power
>> off can help to save remaining power after selective suspend.
>
> That's a lot of power! Suspended USB devices aren't supposed to
> consume more than 2.5 mA of bus current, which at 5 V amounts to<=
> 0.0125 W. Does the port really use that much? Or does the SSD have a
> separate power supply that it disables when port power is removed?
The device consumes about 3.1w. The selective suspend can cut down 0.7-0.9w
After power off port, all power will removed.
I test all the motherboard power consumption and get the result.
From lsusb, it's self-powered.
lsusb
Bus 003 Device 006: ID 174c:55aa ASMedia Technology Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x174c ASMedia Technology Inc.
idProduct 0x55aa
bcdDevice 1.00
iManufacturer 2 01234567890123456789012345678901234567890123
iProduct 3 012345678901234567890123456789012345678901234567
iSerial 1 0123456789ABCDEF019F
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0001
Self Powered
--
Best Regards
Tianyu Lan
linux kernel enabling team
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-11 18:24 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 8:33 [RFC PATCH] usb/acpi: Add support usb port power off mechanism for device fixed on the motherboard Lan Tianyu
2012-05-10 15:54 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1205101136470.1831-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-05-10 16:35 ` Sarah Sharp
2012-05-10 17:44 ` Alan Stern
2012-05-11 16:12 ` Lan Tianyu
2012-05-11 16:16 ` Lan Tianyu
2012-05-11 17:44 ` Alan Stern
2012-05-11 18:12 ` Sarah Sharp
2012-05-12 12:47 ` Sergei Shtylyov
2012-05-12 14:04 ` Greg KH
2012-05-12 18:00 ` Lan Tianyu
2012-05-11 18:18 ` Lan Tianyu [this message]
[not found] ` <Pine.LNX.4.44L0.1205111302080.1865-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-05-11 18:35 ` Greg KH
2012-05-11 19:32 ` Alan Stern
2012-05-11 20:11 ` Sarah Sharp
2012-05-11 21:09 ` Peter Stuge
2012-05-15 1:47 ` Sarah Sharp
2012-05-15 4:57 ` Peter Stuge
2012-05-11 19:54 ` Lan, Tianyu
2012-05-11 20:15 ` Sarah Sharp
2012-05-11 20:26 ` Alan Stern
2012-05-11 20:20 ` Alan Stern
2012-05-12 17:47 ` Lan Tianyu
2012-05-12 18:04 ` Lan Tianyu
2012-05-13 2:50 ` Alan Stern
2012-05-10 19:19 ` Dan Williams
[not found] ` <1336677578.6463.5.camel-wKZy7rqYPVb5EHUCmHmTqw@public.gmane.org>
2012-05-10 21:11 ` Sarah Sharp
2012-05-11 4:13 ` Peter Stuge
2012-05-11 14:20 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1205111019000.1865-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-05-11 14:30 ` Peter Stuge
2012-05-11 14:08 ` Alan Stern
2012-05-11 18:03 ` Sarah Sharp
2012-05-11 19:14 ` Alan Stern
2012-05-11 20:21 ` Sarah Sharp
2012-05-11 20:36 ` Alan Stern
2012-05-11 23:59 ` Sarah Sharp
2012-05-12 0:17 ` Greg KH
2012-05-12 13:54 ` Alan Stern
2012-05-14 23:21 ` Sarah Sharp
2012-05-15 14:31 ` Lan Tianyu
[not found] ` <4FB268CA.9060304-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-05-15 15:18 ` Greg KH
2012-05-15 20:00 ` Sarah Sharp
2012-05-16 6:26 ` Lan Tianyu
2012-05-16 14:36 ` Alan Stern
2012-05-16 14:39 ` Greg KH
2012-05-16 14:54 ` Lan Tianyu
2012-05-16 15:08 ` Greg KH
2012-05-16 15:32 ` Lan Tianyu
[not found] ` <20120516150846.GB3293-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-05-16 15:57 ` Sarah Sharp
2012-05-16 15:12 ` Alan Stern
[not found] ` <20120516143958.GA612-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-05-17 11:42 ` Sergei Shtylyov
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=4FAD580E.2010301@intel.com \
--to=tianyu.lan@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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