27" Mac screen issues with power-cycling of ports

[wkoszek]

First of all - thanks a lot for uhubctl. I think it's a remedy for hanging USB in tablets and smartphones I work with

Setup

I have 27" Apple Retina screen hooked up to a Macbook Air. I want to use it to selectively power cycle ASUS Android tablet and an iPhone which I've hooked up to the screen.

First note

My understanding is that port 1 is special? Output:

Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0100 power
   Port 2: 0503 highspeed power enable connect
   Port 3: 0503 highspeed power enable connect
   Port 4: 0103 power enable connect
   Port 5: 0503 highspeed power enable connect
   Port 6: 0000 off
   Port 7: 0103 power enable connect

It only reports power, but not anything else? My empirical experiments show it's a special thing toggling power for the whole bus. Just wanted to know if this is documented. Below I provide the USB bus topology. This screen has 7 logical USBs, but the back of the screen has 3 physical USB ports.

Issue

What I'm seeing: I can't power-cycle the power2...7 if Android phone/tablet is hooked up to it. Example:

Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0100 power
   Port 2: 0503 highspeed power enable connect <------- Android phone
   Port 3: 0100 power
   Port 4: 0103 power enable connect
   Port 5: 0503 highspeed power enable connect
   Port 6: 0100 power
   Port 7: 0103 power enable connect

The output:

[11:41:30][wkoszek@wkoszek_mba:~/r/autotest/www]$ uhubctl -p 2 -a off
Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 2: 0503 highspeed power enable connect
Sent power off request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 2: 0000 off
[11:41:55][wkoszek@wkoszek_mba:~/r/autotest/www]$ uhubctl -p 2 -a on
Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 2: 0000 off
Sent power on request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 2: 0100 power

So looks like it's OK from the uhubctl reporting point of view, but I don't see this power-cycle happening on a device. I'm looking at the battery status and "debugging" mode icon, since I'm developing on this phone. But when I do:

[11:43:50][wkoszek@wkoszek_mba:~/r/autotest/www]$ uhubctl -p 1 -a off
Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0100 power
Sent power off request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0000 off
[11:43:56][wkoszek@wkoszek_mba:~/r/autotest/www]$ uhubctl -p 1 -a on
Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0000 off
Sent power on request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0100 power

The power-cycle is reported by a device.

Now weird thing. I unplug everything and connect iPhone to port 3:

Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 1: 0100 power
   Port 2: 0100 power
   Port 3: 0503 highspeed power enable connect <----------- iPhone.
   Port 4: 0103 power enable connect
   Port 5: 0503 highspeed power enable connect
   Port 6: 0100 power
   Port 7: 0103 power enable connect

When I do:

[11:47:20][wkoszek@wkoszek_mba:~/r/autotest/www]$ uhubctl -p 3 -a cycle
Current status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 3: 0503 highspeed power enable connect
Sent power off request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 3: 0000 off
Sent power on request
New status for hub 64-1, vendor 05ac:9127, 7 ports
   Port 3: 0100 power

it works fine. The reporting is OK, and the phone gets power cycled. Same when I replugged it in port 2.

I'm trying to understand if other people see the same issue or whether it's an expected behaviour.

USB:

    USB 3.0 Bus:

      Capacity: 2.02 GB (2,021,654,528 bytes)
      Removable Media: Yes
      BSD Name: disk2
      Host Controller Driver: AppleUSBXHCIWPT
      Partition Map Type: MBR (Master Boot Record)
      PCI Device ID: 0x9cb1
      PCI Revision ID: 0x0003
      PCI Vendor ID: 0x8086
      Volumes:
        6509990502:
          Capacity: 2.02 GB (2,021,538,304 bytes)
          Available: 1.23 GB (1,227,030,528 bytes)
          Writable: Yes
          File System: MS-DOS FAT16
          BSD Name: disk2s1
          Mount Point: /Volumes/6509990502
          Content: DOS_FAT_16

        Card Reader:

          Product ID: 0x8406
          Vendor ID: 0x05ac  (Apple Inc.)
          Version: 8.20
          Serial Number: 000000000820
          Speed: Up to 5 Gb/sec
          Manufacturer: Apple
          Location ID: 0x14600000 / 23
          Current Available (mA): 1800
          Current Required (mA): 224
          Extra Operating Current (mA): 0
          Capacity: 2.02 GB (2,021,654,528 bytes)
          Removable Media: Yes
          Detachable Drive: Yes
          BSD Name: disk2
          Built-In: Yes
          Partition Map Type: MBR (Master Boot Record)
          Volumes:
            6509990502:
              Capacity: 2.02 GB (2,021,538,304 bytes)
              Available: 1.23 GB (1,227,030,528 bytes)
              Writable: Yes
              File System: MS-DOS FAT16
              BSD Name: disk2s1
              Mount Point: /Volumes/6509990502
              Content: DOS_FAT_16

        BRCM20702 Hub:

          Product ID: 0x4500
          Vendor ID: 0x0a5c  (Broadcom Corp.)
          Version: 1.00
          Speed: Up to 12 Mb/sec
          Manufacturer: Apple Inc.
          Location ID: 0x14300000 / 2
          Current Available (mA): 1000
          Current Required (mA): 94
          Extra Operating Current (mA): 0
          Built-In: Yes

            Bluetooth USB Host Controller:

              Product ID: 0x828f
              Vendor ID: 0x05ac  (Apple Inc.)
              Version: 1.18
              Speed: Up to 12 Mb/sec
              Manufacturer: Apple Inc.
              Location ID: 0x14330000 / 5
              Current Available (mA): 1000
              Current Required (mA): 0
              Extra Operating Current (mA): 0
              Built-In: Yes

        Hub:

          Product ID: 0x1521
          Vendor ID: 0x04cc  (Philips Semiconductors)
          Version: 2.00
          Speed: Up to 480 Mb/sec
          Location ID: 0x14200000 / 8
          Current Available (mA): 1000
          Current Required (mA): 0
          Extra Operating Current (mA): 0

    USB 2.0 Bus:

      Host Controller Driver: AppleUSBEHCIPI7C9X440SL
      PCI Device ID: 0x400f
      PCI Revision ID: 0x0003
      PCI Vendor ID: 0x12d8

        Hub:

          Product ID: 0x9127
          Vendor ID: 0x05ac  (Apple Inc.)
          Version: 1.00
          Speed: Up to 480 Mb/sec
          Location ID: 0x40100000 / 6
          Current Available (mA): 1000
          Current Required (mA): 100
          Extra Operating Current (mA): 0
          Built-In: Yes

            Nexus 7:

              Product ID: 0x4ee2
              Vendor ID: 0x18d1  (Google Inc.)
              Version: 2.28
              Serial Number: 0a83b2b0
              Speed: Up to 480 Mb/sec
              Manufacturer: asus
              Location ID: 0x40130000 / 7
              Current Available (mA): 1000
              Current Required (mA): 500
              Extra Operating Current (mA): 0

            FaceTime HD Camera (Display):

              Product ID: 0x1112
              Vendor ID: 0x05ac  (Apple Inc.)
              Version: 71.60
              Serial Number: CC2E9T04VPDJ9FLP
              Speed: Up to 480 Mb/sec
              Manufacturer: Apple Inc.
              Location ID: 0x40150000 / 3
              Current Available (mA): 1000
              Current Required (mA): 500
              Extra Operating Current (mA): 0
              Built-In: Yes

            Apple Thunderbolt Display:

              Product ID: 0x9227
              Vendor ID: 0x05ac  (Apple Inc.)
              Version: 1.39
              Serial Number: 182A0933
              Speed: Up to 12 Mb/sec
              Manufacturer: Apple Inc.
              Location ID: 0x40170000 / 2
              Current Available (mA): 1000
              Current Required (mA): 2
              Extra Operating Current (mA): 0
              Built-In: Yes

            iPhone:

              Product ID: 0x12a8
              Vendor ID: 0x05ac  (Apple Inc.)
              Version: 6.01
              Serial Number: ba8b31ea427d8730fa2412906d9df1f6e90a1d94
              Speed: Up to 480 Mb/sec
              Manufacturer: Apple Inc.
              Location ID: 0x40120000 / 5
              Current Available (mA): 1000
              Current Required (mA): 500
              Extra Operating Current (mA): 500
              Sleep current (mA): 1000

            Display Audio:

              Product ID: 0x1107
              Vendor ID: 0x05ac  (Apple Inc.)
              Version: 2.09
              Serial Number: 182A0933
              Speed: Up to 12 Mb/sec
              Manufacturer: Apple Inc.
              Location ID: 0x40140000 / 4
              Current Available (mA): 1000
              Current Required (mA): 2
              Extra Operating Current (mA): 0
              Built-In: Yes

[mvp]

Thank you! :)

• Note that USB ports as reported by libusb don't necessarily map well to actual physical ports. Some of them may be not even wired - e.g. uhubctl discovers 7 ports, but only 3 physical ports could be present. You may need to use some experimentation to find out which physical port is which from uhubctl (actually, libusb) point of view.
• Some USB hubs may act really weird if high-powered devices are connected. Normally, USB hubs can provide just 500mA of power, however some modern Android and iOS devices like to draw a lot more, e.g. 1A or even 2A of power. I observed that in those cases, some hubs may refuse to turn off power, or they do turn it off only to automatically reenable it back milliseconds later - this is why I added command line swtich --repeat - if used, it will try to turn off power many times in quick succession, and sometimes it does help to turn off stubborn device.
• Some hubs report that selective power control is supported, but apparently some manufacturers want to save few cents and actual power rails maybe not really connected, which makes uhubctl not work...

[mvp]

Not much can be done to fix this hardware issue by uhubctl itself, closing...

[wkoszek]

@mvp I'm OK with closing, but how about we move what you/I wrote to the README? Also maybe it'd be worth starting a table of hubs that are known to cause issues/known to work, and how to check which is which?

[mvp]

Ok, I will add short summary of hw issues into README later this week.

[wkoszek]

Sounds good. You may reopen until then. Thanks, take care.

On Mon, Aug 15, 2016 at 12:47 PM, mvp notifications@github.com wrote:

Ok, I will add short summary of hw issues into README later this week.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdgEHAaha2uQ5wPFMh1DzJyiD6iAXY8ks5qgMJlgaJpZM4JkqdV
.

Wojciech A. Koszek
wojciech@koszek.com
http://www.koszek.com/