From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Lan Tianyu <tianyu.lan@intel.com>,
lenb@kernel.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: Fri, 11 May 2012 13:11:24 -0700 [thread overview]
Message-ID: <20120511201124.GF18754@xanatos> (raw)
In-Reply-To: <20120511183543.GF7920@kroah.com>
On Fri, May 11, 2012 at 11:35:43AM -0700, Greg KH wrote:
> On Fri, May 11, 2012 at 01:44:26PM -0400, Alan Stern wrote:
> > On Sat, 12 May 2012, Lan Tianyu wrote:
> > > So I should work on the external ports without devices firstly and
> > > add the sys file for user to control?
> >
> > Yes, I think so. It will be less controversial and probably simpler.
> > When that mechanism is ready, you should be able to use it
> > automatically for unconnectable ports.
> >
> > One tricky thing: In theory, there should be a separate sysfs file for
> > each port. That seems like a lot of overhead though; is there any way
> > to present the information in a single file that won't offend sysfs
> > purists?
>
> Why is that a lot of "overhead"? It's what, 7-9 files max? As Sarah
> points out, one file for all ports is racy and can get to be a mess.
>
> But then again, I'm a "sysfs purist" :)
Theoretically there's no maximum number for xHCI root ports, so I
wouldn't be so sure you'll only have 9 files on future xHCI hosts.
Sarah Sharp
next prev parent reply other threads:[~2012-05-11 20:11 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
[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 [this message]
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=20120511201124.GF18754@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tianyu.lan@intel.com \
/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