/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | mt8183-afe-pcm.txt | 7 - resets: Must contain an entry for each entry in reset-names 12 - clocks: Must contain an entry for each entry in clock-names
|
H A D | brcm,bcm63xx-audio.txt | 9 - clocks: Must contain an entry for each entry in clock-names. 11 - clock-names: One of each entry matching the clocks phandles list:
|
H A D | img,parallel-out.txt | 11 - dmas: Contains an entry for each entry in dma-names. 16 - clocks : Contains an entry for each entry in clock-names.
|
H A D | img,spdif-in.txt | 11 - dmas: Contains an entry for each entry in dma-names. 16 - clocks : Contains an entry for each entry in clock-names
|
H A D | img,spdif-out.txt | 11 - dmas: Contains an entry for each entry in dma-names. 16 - clocks : Contains an entry for each entry in clock-names.
|
/openbmc/u-boot/doc/device-tree-bindings/pmic/ |
H A D | sandbox.txt | 20 To bind each regulator, the optional regulator subnodes should exists. 23 - ldo/buck subnodes of each device's regulator (see regulator binding info)
|
/openbmc/u-boot/doc/device-tree-bindings/pwm/ |
H A D | pwm.txt | 16 PWM properties should be named "pwms". The exact meaning of each pwms 17 property must be documented in the device tree binding for each device. 19 each of the PWM devices listed in the "pwms" property. If no "pwm-names"
|
/openbmc/linux/Documentation/admin-guide/auxdisplay/ |
H A D | cfag12864b.rst | 38 :Pages: 8 each controller 39 :Addresses: 64 each page 40 :Data size: 1 byte each address
|
/openbmc/linux/Documentation/devicetree/bindings/powerpc/ |
H A D | sleep.yaml | 16 reasonably describe. Thus, each device controlled in such a manner 19 The sleep property consists of one or more sleep resources, each of 33 Some devices may share a clock domain with each other, such that they should
|
/openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
H A D | ti,am3359-adc.yaml | 34 description: List of open delays for each channel of ADC in the order of 43 description: List of sample delays for each channel of ADC in the order of 51 description: Number of averages to be performed for each channel of ADC. If
|
/openbmc/linux/Documentation/devicetree/bindings/display/ |
H A D | arm,komeda.yaml | 15 to a 4K resolution each. Each pipeline can be composed of up to four 53 The stream IDs for each of the used pipelines, each four IDs for the
|
/openbmc/linux/tools/testing/selftests/arm64/fp/ |
H A D | README | 71 1) Start 2 guests, using the following command for each: 82 each instance in separate terminal (use screen or ssh etc.) This 88 2) Run the sve-stress on *each* guest with the Vector-Length set to 32: 98 If no error is detected, you will see output from each sve-stress
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | sprd,pinctrl.txt | 5 The first block comprises some global control registers, and each 28 register definition, and each register described one pin is used 57 register definition, and each register described one pin is used to 63 Please refer to each sprd,<soc>-pinctrl.txt binding doc for supported SoCs. 83 Please refer to each sprd,<soc>-pinctrl.txt binding doc for supported values.
|
/openbmc/phosphor-pid-control/ |
H A D | README.md | 11 application will use thermal control, such that each defined zone is kept within 21 The system will run a control loop for each zone with the attempt to maintain 31 each zone, and has a master thread which listens for dbus messages. Each zone 42 A configuration file will need to exist for each board. 78 The plan is to listen for fan_tach updates for each fan in a background thread. 79 This will receive an update from phosphor-hwmon each time it updates any sensor 82 By default phosphor-hwmon reads each sensor in turn and then sleeps for 1
|
/openbmc/linux/Documentation/devicetree/bindings/interconnect/ |
H A D | samsung,exynos-bus.yaml | 16 Generally, each bus of Exynos SoC includes a source clock and a power line, 18 monitor the usage of each bus in runtime, the driver uses the PPMU (Platform 22 The Exynos SoC includes the various sub-blocks which have the each AXI bus. 23 The each AXI bus has the owned source clock but, has not the only owned power 25 divide into two type of device as the role of each sub-block. There are two 41 There are a little different composition among Exynos SoC because each Exynos 43 in devicetree file instead of each device driver. In result, this driver is
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | qcom_camss.rst | 31 A separate camera sensor can be connected to each of the CSIPHY module; 114 - 2 / 3 CSIPHY sub-devices - each CSIPHY is represented by a single sub-device; 115 - 2 / 4 CSID sub-devices - each CSID is represented by a single sub-device; 119 the number of the input interfaces (3 RDI and 1 PIX for each VFE). 123 - representing CSIPHY and CSID modules by a separate sub-device for each module 125 - representing VFE by a separate sub-devices for each input interface allows 160 configuration on each hardware module is applied on STREAMON ioctl based on
|
/openbmc/linux/Documentation/devicetree/bindings/regulator/ |
H A D | 88pm800.txt | 6 - regulators: A node that houses a sub-node for each regulator within the 9 The content of each sub-node is defined by the standard binding for
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | arch.rst | 27 Rather than enumerating here how each tool makes use of these common 29 in each tool as they come up in the course of the text.
|
/openbmc/linux/Documentation/devicetree/bindings/timer/ |
H A D | ti,keystone-timer.txt | 6 timers, each half can operate in conjunction (chain mode) or independently 7 (unchained mode) of each other.
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | debugfs-scmi-raw | 13 (receiving an EOF at each message boundary). 31 (receiving an EOF at each message boundary). 42 each message boundary). 53 each message boundary). 82 (receiving an EOF at each message boundary). 109 (receiving an EOF at each message boundary).
|
/openbmc/phosphor-fan-presence/docs/control/ |
H A D | events.md | 61 property on each D-Bus object in the group, update the new value in the object 65 the Present property on each member of the group and set the fan target hold to 99 for each. 119 2. `name_has_owner` - Populates the service owned state from D-Bus for each 124 Signal triggers subscribe to certain D-Bus signals for each member of its 292 1. For each member of the 'pcie temps' group: 316 1. For each member of the 'proc 0 core temps' group: 354 1. For each member of the 'pcie temps' group: 378 1. For each member of the 'proc 0 core temps' group: 404 The above config reads the configured D-Bus property on each group member [all …]
|
/openbmc/linux/Documentation/sound/cards/ |
H A D | mixart.rst | 29 One miXart8 board will be represented as 4 alsa cards, each with 1 45 can be muted for each stream to use 8 analog/digital outputs separately. 57 digital volume control of each analog substream. 59 digital volume control of each AES/EBU substream.
|
/openbmc/linux/Documentation/devicetree/bindings/reset/ |
H A D | reset.txt | 23 the DT node of each affected HW block, since if activated, an unrelated block 29 rather than to slavishly enumerate the reset signal that affects each HW 49 for each reset signal that affects the device, or that the 73 This represents a bus that controls the reset signal of each of four sub-
|
/openbmc/u-boot/doc/device-tree-bindings/reset/ |
H A D | reset.txt | 23 the DT node of each affected HW block, since if activated, an unrelated block 29 rather than to slavishly enumerate the reset signal that affects each HW 49 for each reset signal that affects the device, or that the 73 This represents a bus that controls the reset signal of each of four sub-
|
/openbmc/linux/Documentation/admin-guide/perf/ |
H A D | arm-cmn.rst | 6 grid of crosspoints (XPs), with each crosspoint supporting up to two 22 each mesh counts its own events entirely independently, and additional 42 By default each event provides an aggregate count over all nodes of the 61 REQ or SNP channel, it can be specified as two events - one for each
|