From: Oliver Neukum <oneukum@suse.de>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: lenb@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org,
stern@rowland.harvard.edu, sarah.a.sharp@linux.intel.com,
mjg59@srcf.ucam.org, mfm@muteddisk.com,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [Resend PATCH V2 3/7] usb: Set device removable state based on ACPI USB data
Date: Fri, 4 May 2012 08:24:16 +0200 [thread overview]
Message-ID: <201205040824.17010.oneukum@suse.de> (raw)
In-Reply-To: <1336100803-28353-4-git-send-email-tianyu.lan@intel.com>
Am Freitag, 4. Mai 2012, 05:06:39 schrieb Lan Tianyu:
>
> From: Matthew Garrett <mjg@redhat.com>
>
> ACPI offers two methods that allow us to infer whether or not a USB port
> is removable. The _PLD method gives us information on whether the port is
> "user visible" or not. If that's not present then we can fall back to the
> _UPC method which tells us whether or not a port is connectable.
How does this act on bluetooth devices that are (dis)connected by switches
on laptops?
Regards
Oliver
next prev parent reply other threads:[~2012-05-04 6:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 3:06 [Resend PATCH V2 0/7] usb/acpi: Add binding usb device with acpi Lan Tianyu
2012-05-04 3:06 ` [Resend PATCH V2 1/7] ACPI: Add _PLD support Lan Tianyu
2012-05-04 6:18 ` Oliver Neukum
2012-05-04 3:06 ` [Resend PATCH V2 2/7] usb: Bind devices to ACPI devices when possible Lan Tianyu
[not found] ` <1336100803-28353-3-git-send-email-tianyu.lan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-05-05 0:21 ` Greg KH
2012-05-05 5:26 ` Matthew Garrett
2012-05-05 11:14 ` Sergei Shtylyov
2012-05-05 14:47 ` Greg KH
2012-05-05 15:00 ` Matthew Garrett
2012-05-04 3:06 ` [Resend PATCH V2 5/7] usb: move struct usb_device->children to struct usb_hub_port->child Lan Tianyu
[not found] ` <1336100803-28353-1-git-send-email-tianyu.lan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-05-04 3:06 ` [Resend PATCH V2 3/7] usb: Set device removable state based on ACPI USB data Lan Tianyu
2012-05-04 6:24 ` Oliver Neukum [this message]
2012-05-07 1:38 ` Lan Tianyu
2012-05-07 16:57 ` Greg KH
[not found] ` <20120507165744.GA28045-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-05-08 2:58 ` Matthew Garrett
2012-05-08 8:52 ` Lan Tianyu
2012-05-08 20:23 ` Len Brown
[not found] ` <4FA980C9.4020107-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-05-09 1:00 ` Lan Tianyu
2012-05-08 17:31 ` Greg KH
2012-05-09 2:49 ` Lan Tianyu
2012-05-04 3:06 ` [Resend PATCH V2 4/7] usb: add struct usb_hub_port to store port related members Lan Tianyu
2012-05-04 3:06 ` [Resend PATCH V2 6/7] usb/acpi: add the support of usb hub ports' acpi binding without attached devices Lan Tianyu
2012-05-04 3:06 ` [Resend PATCH V2 7/7] usb/acpi: add usb check for the connect type of usb port Lan Tianyu
2012-05-04 6:37 ` Oliver Neukum
2012-05-07 1:37 ` Lan Tianyu
2012-05-04 3:17 ` [Resend PATCH V2 0/7] usb/acpi: Add binding usb device with acpi Matthew Garrett
[not found] ` <20120504031720.GA6840-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2012-05-04 3:20 ` Greg KH
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=201205040824.17010.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfm@muteddisk.com \
--cc=mjg59@srcf.ucam.org \
--cc=mjg@redhat.com \
--cc=sarah.a.sharp@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).