/openbmc/openbmc/meta-phosphor/conf/distro/include/ |
H A D | phosphor-defaults.inc | 60 # The phosphor-ipmi-fru application is data-driven and requires an input 64 # The phosphor-ipmi-fru application is data-driven and requires an input 71 # The phosphor-ipmi-fru application is data-driven and requires an input 84 # The phosphor-host-ipmid application is data-driven. 86 # The phosphor-host-ipmid application is data-driven and requires an input 93 # The phosphor-host-ipmid application is data-driven and requires an input 102 # The phosphor-led-manager application is data-driven and requires an input 109 # The phosphor-logging application has a data driven plugin that adds FRU 118 # The phosphor-fan-presence application is data driven and requires an input 125 # The phosphor-fan-control application is data driven and requires a YAML file
|
/openbmc/openpower-vpd-parser/ |
H A D | README.md | 13 This is a build-time YAML driven application that parses the OpenPower VPD 35 Making the application runtime JSON driven allows us to support multiple systems 41 1. The long-term goal is to completely do away with the build time YAML driven 43 VPD parser applications into a single runtime JSON driven application.
|
/openbmc/linux/Documentation/devicetree/bindings/display/ |
H A D | truly,nt35597.txt | 20 - ports: This device has two video ports driven by two DSIs. Their connections 23 - port@0: DSI input port driven by master DSI 24 - port@1: DSI input port driven by secondary DSI
|
/openbmc/linux/drivers/leds/rgb/ |
H A D | Kconfig | 12 and driven by a controller that doesn't have multi-color support. 18 tristate "PWM driven multi-color LED Support" 21 This option enables support for PWM driven monochrome LEDs that are
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-robotframework_7.2.bb | 3 testing and acceptance test-driven development (ATDD). It has easy-to-use\ 4 tabular test data syntax and it utilizes the keyword-driven testing approach.\
|
H A D | python3-behave_1.2.6.bb | 1 SUMMARY = "A behavior-driven development framework, Python style"
|
/openbmc/linux/arch/arm64/boot/dts/freescale/ |
H A D | imx8mm-venice-gw72xx-0x-rs422.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active) 8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
|
H A D | imx8mm-venice-gw72xx-0x-rs485.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active) 8 * - GPIO4_2 rs485_hd needs to be driven high (active)
|
H A D | imx8mm-venice-gw73xx-0x-rs485.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active) 8 * - GPIO4_2 rs485_hd needs to be driven high (active)
|
H A D | imx8mm-venice-gw73xx-0x-rs422.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active) 8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
|
/openbmc/linux/Documentation/hwmon/ |
H A D | tc654.rst | 32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on 34 driven based on the Vin input.
|
/openbmc/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
H A D | pincfg.txt | 18 0 = The pin is actively driven as an output 20 driven active-low, otherwise it is three-stated.
|
/openbmc/linux/Documentation/driver-api/thermal/ |
H A D | nouveau_thermal.rst | 75 Your fan can be driven in different modes: 78 * 1: The fan can be driven in manual (use pwm1 to change the speed); 79 * 2; The fan is driven automatically depending on the temperature.
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | gpio-matrix-keypad.txt | 1 * GPIO driven matrix keypad device tree bindings 3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
|
/openbmc/linux/Documentation/sound/soc/ |
H A D | clocking.rst | 12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK 24 The Digital Audio Interface is usually driven by a Bit Clock (often referred to
|
/openbmc/linux/Documentation/peci/ |
H A D | peci.rst | 30 bit with a driven, rising edge from an idle near zero volts. The 31 duration of the signal driven high allows to determine whether the bit
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | marvell,dove-pinctrl.txt | 64 pmu-nc Pin not driven by any PM function 65 pmu-low Pin driven low (0) 66 pmu-high Pin driven high (1)
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/gnuplot/ |
H A D | gnuplot_5.4.3.bb | 1 SUMMARY = "Gnuplot is a portable command-line driven graphing utility" 2 DESCRIPTION = "Gnuplot is a portable command-line driven interactive datafile \
|
/openbmc/linux/Documentation/networking/ |
H A D | team.rst | 7 Team devices are driven from userspace via libteam library which is here:
|
/openbmc/openbmc/meta-asrock/meta-e3c246d4i/recipes-x86/chassis/x86-power-control/ |
H A D | power-config-host0.json | 37 * I can tell. It does have an O_PWROK line that's driven
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | intro.rst | 49 options about how that value is driven, so that for example only one 50 value might be driven, supporting "wire-OR" and similar schemes for the 95 level is actually driven), or "open source" (where only the high signal level is 96 driven) signaling. That term applies to CMOS transistors; "open collector" is
|
/openbmc/linux/drivers/parport/ |
H A D | BUGS-parport | 7 software-driven mode in ieee1284_ops.c
|
/openbmc/linux/Documentation/features/debug/stackprotector/ |
H A D | arch-support.txt | 4 # description: arch supports compiler driven stack overflow protection
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-driver-fsi-master-gpio | 9 where the FSI bus is driven externally (for example, by
|
/openbmc/u-boot/doc/device-tree-bindings/timer/ |
H A D | arc_timer.txt | 24 as each timer is driven by the same core clock.
|