Searched +full:bus +full:- +full:powered (Results 1 – 25 of 69) sorted by relevance
123
| /Documentation/devicetree/bindings/usb/ |
| D | usb251xb.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Microchip USB 2.0 Hi-Speed Hub Controller 10 - Richard Leitner <richard.leitner@skidata.com> 15 - microchip,usb2422 16 - microchip,usb2512b 17 - microchip,usb2512bi 18 - microchip,usb2513b 19 - microchip,usb2513bi [all …]
|
| D | atmel-usb.txt | 6 - compatible: Should be "atmel,at91rm9200-ohci" for USB controllers 8 - reg: Address and length of the register set for the device 9 - interrupts: Should contain ohci interrupt 10 - clocks: Should reference the peripheral, host and system clocks 11 - clock-names: Should contain three strings 15 - num-ports: Number of ports. 16 - atmel,vbus-gpio: If present, specifies a gpio that needs to be 17 activated for the bus to be powered. 18 - atmel,oc-gpio: If present, specifies a gpio that needs to be 22 compatible = "atmel,at91rm9200-ohci", "usb-ohci"; [all …]
|
| D | samsung,exynos-usb2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/usb/samsung,exynos-usb2.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Krzysztof Kozlowski <krzk@kernel.org> 15 - samsung,exynos4210-ehci 16 - samsung,exynos4210-ohci 21 clock-names: 23 - const: usbhost 32 phy-names: [all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-diseqc-reset-overload.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 13 FE_DISEQC_RESET_OVERLOAD - Restores the power to the antenna subsystem, if it was powered off due -… 31 If the bus has been automatically powered off due to power overload, 32 this ioctl call restores the power to the bus. The call requires 34 is manually powered off. Not all Digital TV adapters support this ioctl. 41 On error -1 is returned, and the ``errno`` variable is set 45 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/firmware-guide/acpi/ |
| D | non-d0-probe.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 In some cases it may be preferred to leave certain devices powered off for the 19 probe. The support for _DSC requires support from the kernel bus type if the 20 bus driver normally sets the device in D0 state for probe. 22 The downside of using _DSC is that as the device is not powered on, even if 28 --- 33 the device will not be powered on (put in D0 state) for probe. 36 -------- 41 .. code-block:: text 44 0 D0 Device fully powered on [all …]
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 16 ----------- 42 A bulk read of all devices on the bus could be done writing ``trigger`` 44 send the convert command to all devices on the bus, and if parasite 45 powered devices are detected on the bus (and strong pullup is enabled 47 time required by parasited powered device on the line. Reading 49 -1 if at least one sensor still in conversion, 1 if conversion is complete 72 the sensor. Resolution is reset when the sensor gets power-cycled. 81 Some non-genuine DS18B20 chips are fixed in 12-bit mode only, so the actual 86 The write-only sysfs entry ``eeprom_cmd`` is an alternative for EEPROM operations. 91 ``0`` if the device is parasite powered, ``1`` if the device is externally powered. [all …]
|
| D | w1_ds28e17.rst | 7 * Maxim DS28E17 1-Wire-to-I2C Master Bridge 19 ----------- 20 The DS28E17 is a Onewire slave device which acts as an I2C bus master. 22 This driver creates a new I2C bus for any DS28E17 device detected. I2C buses 25 connected to a "native" I2C bus master. 30 SUBSYSTEM=="i2c-dev", KERNEL=="i2c-[0-9]*", ATTRS{name}=="w1-19-*", \ 31 SYMLINK+="i2c-$attr{name}" 33 may be used to create stable /dev/i2c- entries based on the unique id of the 41 it is connected. The power-on default of the DS28E17 is 400kBaud, but 42 chips may come and go on the Onewire bus without being de-powered and [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-usb-devices-usbsevseg | 1 What: /sys/bus/usb/.../powered 5 Description: Controls whether the device's display will powered. 6 A value of 0 is off and a non-zero value is on. 8 What: /sys/bus/usb/.../mode_msb 9 What: /sys/bus/usb/.../mode_lsb 22 What: /sys/bus/usb/.../textmode 28 hex: each character is between 0-15 29 ascii: each character is between '0'-'9' and 'A'-'F'. 31 What: /sys/bus/usb/.../text 37 What: /sys/bus/usb/.../decimals
|
| D | sysfs-bus-platform-onboard-usb-dev | 1 What: /sys/bus/platform/devices/<dev>/always_powered_in_suspend 5 linux-usb@vger.kernel.org 7 (RW) Controls whether the USB hub remains always powered 9 available for non-hub devices.
|
| D | sysfs-driver-w1_therm | 1 What: /sys/bus/w1/devices/.../alarms 7 (typical -55 degC to 125 degC), if not values will be trimmed 11 master level, refer to Documentation/w1/w1-generic.rst for 17 What: /sys/bus/w1/devices/.../eeprom_cmd 33 What: /sys/bus/w1/devices/.../ext_power 39 * '0': device parasite powered 40 * '1': device externally powered 41 * '-xx': xx is kernel error when reading power status 47 What: /sys/bus/w1/devices/.../resolution 55 values after power-on. Read or write are : [all …]
|
| D | sysfs-driver-bd9571mwv-regulator | 1 What: /sys/bus/i2c/devices/.../bd9571mwv-regulator.*.auto/backup_mode 6 if DDR power rails will be kept powered during system suspend. 18 wake-up switch,
|
| D | sysfs-bus-coresight-devices-cti | 1 What: /sys/bus/coresight/devices/<cti-name>/enable 7 What: /sys/bus/coresight/devices/<cti-name>/powered 11 Description: (Read) Indicate if the CTI hardware is powered. 13 What: /sys/bus/coresight/devices/<cti-name>/ctmid 19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons 25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name 31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals 37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types 44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals 50 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types [all …]
|
| D | sysfs-bus-i2c-devices-turris-omnia-mcu | 1 What: /sys/bus/i2c/devices/<mcu_device>/board_revision 8 revisions have board information burned in the ATSHA204-A chip). 12 What: /sys/bus/i2c/devices/<mcu_device>/first_mac_address 21 revisions have board information burned in the ATSHA204-A chip). 25 What: /sys/bus/i2c/devices/<mcu_device>/front_button_mode 35 - ``mcu`` makes the button press event be handled by the MCU to 37 - ``cpu`` makes the button press event be handled by the CPU. 41 What: /sys/bus/i2c/devices/<mcu_device>/front_button_poweron 47 low power mode. The router can be powered on by pressing the 57 What: /sys/bus/i2c/devices/<mcu_device>/fw_features [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tlv320aic3x.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 TLV320AIC3x are a series of low-power stereo audio codecs with stereo 13 single-ended or fully differential configurations. 15 The serial control bus supports SPI or I2C protocols, while the serial audio 16 data bus is programmable for I2S, left/right-justified, DSP, or TDM modes. 44 - Jai Luthra <j-luthra@ti.com> 49 - ti,tlv320aic3x 50 - ti,tlv320aic33 [all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | renesas,bsc.yaml | 2 --- 3 $id: http://devicetree.org/schemas/bus/renesas,bsc.yaml# 4 $schema: http://devicetree.org/meta-schemas/core.yaml# 6 title: Renesas Bus State Controller (BSC) 9 - Geert Uytterhoeven <geert+renesas@glider.be> 12 The Renesas Bus State Controller (BSC, sometimes called "LBSC within Bus 13 Bridge", or "External Bus Interface") can be found in several Renesas ARM 14 SoCs. It provides an external bus for connecting multiple external 18 While the BSC is a fairly simple memory-mapped bus, it may be part of a 21 must be powered on, and the functional clock driving the BSC must be [all …]
|
| /Documentation/mhi/ |
| D | topology.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 -------------- 14 such as the external modems and WiFi chipsets. It is also the MHI bus master 17 is taken care by the physical bus such as PCIe. Each controller driver exposes 22 * Turns on the physical bus and establishes the link to the device 24 * Allocates struct mhi_controller and registers with the MHI bus framework 30 ---------- 33 for bi-directional communication. Once MHI is in powered on state, the MHI 40 /sys/bus/mhi/devices/ 43 ---------- [all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 -------------------- 21 0 C 0----------->: : +======>(other CTI channel IO) 22 0 P 0<-----------: : v 24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+ 25 ####### in_trigs : : (id 0-3) ***** ::::::: v 26 # ETM #----------->: : ^ ####### 27 # #<-----------: : +---# ETR # 50 The hardware trigger signals can also be connected to non-CoreSight devices 60 --------------------------- [all …]
|
| D | coresight-cpu-debug.rst | 9 ------------ 11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual 13 debug module and it is mainly used for two modes: self-hosted debug and 16 explore debugging method which rely on self-hosted debug mode, this document 19 The debug module provides sample-based profiling extension, which can be used 21 every CPU has one dedicated debug module to be connected. Based on self-hosted 29 -------------- 31 - During driver registration, it uses EDDEVID and EDDEVID1 - two device ID 32 registers to decide if sample-based profiling is implemented or not. On some 36 - At the time this documentation was written, the debug driver mainly relies on [all …]
|
| /Documentation/usb/ |
| D | misc_usbsevseg.rst | 2 USB 7-Segment Numeric Display 8 ------------------ 16 ------------ 28 hex expects a value between 0-15 per character, 29 ascii expects a value between '0'-'9' and 'A'-'F'. 33 ---------------- 35 echo 1 > /sys/bus/usb/.../powered 37 echo $mode_msb > /sys/bus/usb/.../mode_msb 38 echo $mode_lsb > /sys/bus/usb/.../mode_lsb 40 echo $textmode > /sys/bus/usb/.../textmode [all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | mediatek,bluetooth.txt | 13 - compatible: Must be 14 "mediatek,mt7663u-bluetooth": for MT7663U device 15 "mediatek,mt7668u-bluetooth": for MT7668U device 16 - vcc-supply: Main voltage regulator 21 - pinctrl-names: Should be "default", "runtime" 22 - pinctrl-0: Should contain UART RXD low when the device is powered up to 24 - pinctrl-1: Should contain UART mode pin ctrl 30 - boot-gpios: GPIO same to the pin as UART RXD and used to keep LOW when 31 the device is powered up to enter proper bootstrap mode when 32 - pinctrl-names: Should be "default" [all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-kovaplus | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 4 Description: The integer value of this attribute ranges from 1-4. 11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 14 Description: The integer value of this attribute ranges from 0-4. 18 The profile that's active when powered down is the same that's 19 active when the mouse is powered on. 22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 25 Description: The integer value of this attribute ranges from 1-10. 32 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 35 Description: The integer value of this attribute ranges from 1-10. [all …]
|
| D | sysfs-driver-hid-roccat-koneplus | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 4 Description: The integer value of this attribute ranges from 0-4. 7 profile that's active when the mouse is powered on next time. 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 15 Description: The integer value of this attribute ranges from 0-4. 18 profile that's active when the mouse is powered on next time. 24 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 36 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
|
| D | sysfs-driver-hid-roccat-savu | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 17 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 25 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 48 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 59 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 65 that's active when the mouse is powered on next time. 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 74 Description: The mouse has a Avago ADNS-3090 sensor.
|
| /Documentation/arch/s390/ |
| D | pci.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 - Pierre Morel 17 ----------------------- 28 --------------- 36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf 50 * /sys/bus/pci/slots/XXXXXXXX 56 - /sys/bus/pci/slots/XXXXXXXX/power 59 powered off until all virtual functions are removed with: 60 echo 0 > /sys/bus/pci/devices/XXXX:XX:XX.X/sriov_numvf 62 * /sys/bus/pci/devices/XXXX:XX:XX.X/ [all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12057.txt | 8 ("wakeup-source") to handle the specific use-case found 9 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104 10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip 12 to the SoC but to a PMIC. It allows the device to be powered up when 20 - "compatible": must be "isil,isl12057" 21 - "reg": I2C bus address of the device 25 - "wakeup-source": mark the chip as a wakeup source, independently of 38 that the pinctrl-related properties below are given for completeness and 41 "interrupt-parent" and "interrupts" are usually sufficient): 60 pinctrl-0 = <&rtc_alarm_pin>; [all …]
|
123