Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] using a usb3 hub as a hackerboard power switch?
Date: Wed, 27 Apr 2016 12:25:44 -0700	[thread overview]
Message-ID: <CALQXh-Nf4aUEoOqNbSm80D+T+NWG_1vTR=8yd_5z4A1B2t-CxA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw68U4YYup6Jy0sRTo1z4n+47Q+w8nzPs18ee2Wy4SfvtA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]

Most USB hub chips I've seen don't have individual lines per-port.  Instead
they monitor the +5VDC rail for powering all USB devices, and grant
requests to use power based on a configured power budget (how many amps the
supply can push).

To hack it, I'd use a Pi with it's relay modules and cut the traces to the
port, and then splice in a relay from the module (normally closed side of
the relay).  Then when you need to power-cycle, tell the Pi to cycle output
X.

-Aaron

On Wed, Apr 27, 2016 at 11:44 AM, Dave Taht <dave.taht@gmail.com> wrote:

> I am curious if there would be a way to use a powered usb3 hub to
> individually be able to address and power cycle the ports individually
> on it?
>
> I have accumulated enough hackerboards powered via usb that it would
> make sense to just power them all that way... kind of like I already
> do with these:
>
> http://www.digital-loggers.com/lpc.html
>
> and just use that (rather than an individual power supply for each).
>
>  I am perpetually locking one up or losing connectivity to it for some
> reason or another.
>
> I figure somewhere in the usb spec/protocol/device driver/whatever
> there would be a simple command to just flip the power on and off to
> the port....
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2341 bytes --]

  reply	other threads:[~2016-04-27 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 18:44 Dave Taht
2016-04-27 19:25 ` Aaron Wood [this message]
2016-04-29  9:54 ` Toke Høiland-Jørgensen
2016-04-29 15:02   ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALQXh-Nf4aUEoOqNbSm80D+T+NWG_1vTR=8yd_5z4A1B2t-CxA@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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