On Fri, Feb 7, 2014 at 7:15 AM, Alan Stern wrote:
> On Fri, 7 Feb 2014, Dan Williams wrote:
>
>> >> +static int pair_port(struct device *dev, void *data)
>> >> +{
>> >> + struct usb_port *peer = data;
>> >> + struct usb_port *port_dev = to_usb_port(dev);
>> >
>> > Isn't this backward? dat
On Fri, 7 Feb 2014, Dan Williams wrote:
> >> +static int pair_port(struct device *dev, void *data)
> >> +{
> >> + struct usb_port *peer = data;
> >> + struct usb_port *port_dev = to_usb_port(dev);
> >
> > Isn't this backward? data is the port you want to match, and dev
> > is the device (
On Thu, Feb 6, 2014 at 12:46 PM, Alan Stern wrote:
> On Fri, 31 Jan 2014, Dan Williams wrote:
>
>> ACPI identifies peer ports by setting their 'group_token' and
>> 'group_position' _PLD data to the same value. If a platform has tier
>> mismatch [1] , ACPI can override the default, USB3 defined, p
On Fri, 31 Jan 2014, Dan Williams wrote:
> ACPI identifies peer ports by setting their 'group_token' and
> 'group_position' _PLD data to the same value. If a platform has tier
> mismatch [1] , ACPI can override the default, USB3 defined, peer port
> association for internal hubs. External hubs f
ACPI identifies peer ports by setting their 'group_token' and
'group_position' _PLD data to the same value. If a platform has tier
mismatch [1] , ACPI can override the default, USB3 defined, peer port
association for internal hubs. External hubs follow the default peer
association scheme.
Locati
