~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/leds/ledtrig-usbport.rst

Version: ~ [ linux-6.11.5 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.58 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.114 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.169 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.228 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.284 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.322 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 ====================
  2 USB port LED trigger
  3 ====================
  4 
  5 This LED trigger can be used for signalling to the user a presence of USB device
  6 in a given port. It simply turns on LED when device appears and turns it off
  7 when it disappears.
  8 
  9 It requires selecting USB ports that should be observed. All available ones are
 10 listed as separated entries in a "ports" subdirectory. Selecting is handled by
 11 echoing "1" to a chosen port.
 12 
 13 Please note that this trigger allows selecting multiple USB ports for a single
 14 LED.
 15 
 16 This can be useful in two cases:
 17 
 18 1) Device with single USB LED and few physical ports
 19 ====================================================
 20 
 21 In such a case LED will be turned on as long as there is at least one connected
 22 USB device.
 23 
 24 2) Device with a physical port handled by few controllers
 25 =========================================================
 26 
 27 Some devices may have one controller per PHY standard. E.g. USB 3.0 physical
 28 port may be handled by ohci-platform, ehci-platform and xhci-hcd. If there is
 29 only one LED user will most likely want to assign ports from all 3 hubs.
 30 
 31 
 32 This trigger can be activated from user space on led class devices as shown
 33 below::
 34 
 35   echo usbport > trigger
 36 
 37 This adds sysfs attributes to the LED that are documented in:
 38 Documentation/ABI/testing/sysfs-class-led-trigger-usbport
 39 
 40 Example use-case::
 41 
 42   echo usbport > trigger
 43   echo 1 > ports/usb1-port1
 44   echo 1 > ports/usb2-port1
 45   cat ports/usb1-port1
 46   echo 0 > ports/usb1-port1

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php