From: Lan Tianyu <tianyu.lan@intel.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-usb@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH V2] ACPI: Allow acpi binding with usb3.0 hub
Date: Fri, 21 Sep 2012 11:16:01 +0800 [thread overview]
Message-ID: <505BDBF1.2020209@intel.com> (raw)
In-Reply-To: <20120921002527.GB6909@xanatos>
On 2012年09月21日 08:25, Sarah Sharp wrote:
> Hi Tianyu,
>
> You're correct that the USB core and the xHCI driver has a slightly
> different architecture than the ACPI representation. We have one PCI
> device that has two USB buses/roothubs underneath it. That's because
> external USB 3.0 hubs show up as two USB devices: a USB 3.0 only
> portion, and a USB 2.0 portion. We wanted roothubs to act the same way.
>
> The architecture looks something like this:
>
> struct pci_dev
> |
> struct usb_hcd *primary_hcd -- struct usb_hcd *secondary_hcd
> | |
> struct usb_bus struct usb_bus
> | |
> struct usb_device *root_hub struct usb_device *root_hub
> | |
> struct device struct device
>
> Where the primary_hcd is for the USB 2.0 roothub, and the secondary_hcd
> is for the USB 3.0 roothub.
>
> So you're trying to bind one ACPI node (RHUB) to the struct device
> contained in those two root_hubs, correct? That goal seems sane to me.
>
Yes, that is my patch's purpose.
> Sarah Sharp
--
Best regards
Tianyu Lan
--
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-09-21 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 6:44 [PATCH V2] ACPI: Allow acpi binding with usb3.0 hub Lan Tianyu
2012-09-21 0:25 ` Sarah Sharp
2012-09-21 3:16 ` Lan Tianyu [this message]
[not found] ` <505BDBF1.2020209-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-09-21 17:24 ` Sarah Sharp
2012-09-21 17:31 ` Len Brown
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=505BDBF1.2020209@intel.com \
--to=tianyu.lan@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sarah.a.sharp@linux.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 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.