From: Lan Tianyu <tianyu.lan@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, lenb@kernel.org,
linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org,
sarah.a.sharp@linux.intel.com
Subject: Re: [RFC PATCH V3 3/3] usb : Add sysfs files to control usb port's power
Date: Wed, 06 Jun 2012 09:53:18 +0800 [thread overview]
Message-ID: <4FCEB80E.3070100@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1206051017040.1542-100000@iolanthe.rowland.org>
On 2012年06月05日 22:18, Alan Stern wrote:
> On Tue, 5 Jun 2012, Lan Tianyu wrote:
>
>>> The patch does not implement anything at all for "auto". It should do
>>> _something_.
>>>
>> Yeah, if we don't power off port without device when echo "auto"> portX/control,
>> this patch does nothing about "auto". Original plan is to deal with port without
>> devices firstly. Do you mean I should add the process of port with device in this
>> patch?
>
> At least make a start. For example, have "auto" turn off the power if
> no device is attached to the port.
In your reply for v2, hint that user space can power off port without
device, so I removed related code. Did I misunderstand?
>> control has three options. "auto", "on" and "off"
>> "auto" - if port without device, power off the port.
>> (This patch only cover ports without device)
> Is this option really needed? Can't userspace check first to see
> whether there is a device, and then write "off" if there isn't?
>
>> For ports with device, there is a proposal that if the device was not
>> in the suspend at that pointer, the power would remain on but it would
>> power off when it was suspended. If the the device was in the suspend,
>> "auto" means the device could be put into much lower state so the device
>> need to resume and suspend again.
> That makes more sense. Without this, however, there is no need for
> "auto".
>
>
> If "auto" does nothing, there's no reason to put it in this patch at
> all. It could be added in a later patch, along with its
> implementation.
OK. I prefer to remove "auto" option in this patch. We can further discuss
the function of "auto".
>
> Alan Stern
>
--
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-06-06 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1338799665-13997-1-git-send-email-tianyu.lan@intel.com>
2012-06-04 8:47 ` [RFC PATCH V3 2/3] USB/ACPI: Add usb port's acpi power control in the xhci PORT_POWER feature request process Lan Tianyu
2012-06-04 8:47 ` [RFC PATCH V3 3/3] usb : Add sysfs files to control usb port's power Lan Tianyu
[not found] ` <1338799665-13997-3-git-send-email-tianyu.lan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-06-04 15:02 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1206041040510.1555-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-06-05 8:30 ` Lan Tianyu
2012-06-05 14:18 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1206051017040.1542-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-06-05 15:58 ` Sarah Sharp
2012-06-06 1:53 ` Lan Tianyu [this message]
2012-06-06 14:21 ` Alan Stern
2012-06-07 6:45 ` Lan Tianyu
2012-06-07 14:24 ` Alan Stern
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=4FCEB80E.3070100@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 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.