Home
last modified time | relevance | path

Searched full:driven (Results 1 – 25 of 185) sorted by relevance

12345678

/openbmc/openbmc/meta-phosphor/conf/distro/include/
H A Dphosphor-defaults.inc60 # 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/qemu/include/hw/gpio/
H A Dnrf51_gpio.h8 * Level 0: Input externally driven LOW
9 * Level 1: Input externally driven HIGH
12 * Level 0: Driven LOW
13 * Level 1: Driven HIGH
/openbmc/openpower-vpd-parser/
H A DREADME.md13 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 parser applications into a single runtime JSON driven application.
/openbmc/u-boot/drivers/video/
H A Dam335x-fb.h11 * 0 = lcd_lp and lcd_fp are driven on
14 * 1 = lcd_lp and lcd_fp are driven
21 * 0 = lcd_lp and lcd_fp are driven on
24 * 1 = lcd_lp and lcd_fp are driven on
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-robotframework_7.2.2.bb3 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 Dpython3-behave_1.2.6.bb1 SUMMARY = "A behavior-driven development framework, Python style"
/openbmc/openbmc/meta-facebook/meta-fbdarwin/recipes-phosphor/state/phosphor-state-manager/
H A Dhost-powercycle27 # The GPIO must be driven low before a subsequent reset can be issued
30 echo "Reset pin driven low."
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/pxaregs/pxaregs-1.14/
H A Dpxaregs.c176 { "PGSR_SS0", 0x40F00020, 0, 0x00000001, 'd', "PM GPIO pin 0 is driven to 1 during sleep" },
177 { "PGSR_SS1", 0x40F00020, 1, 0x00000001, 'd', "PM GPIO pin 1 is driven to 1 during sleep" },
178 { "PGSR_SS2", 0x40F00020, 2, 0x00000001, 'd', "PM GPIO pin 2 is driven to 1 during sleep" },
179 { "PGSR_SS3", 0x40F00020, 3, 0x00000001, 'd', "PM GPIO pin 3 is driven to 1 during sleep" },
180 { "PGSR_SS4", 0x40F00020, 4, 0x00000001, 'd', "PM GPIO pin 4 is driven to 1 during sleep" },
181 { "PGSR_SS5", 0x40F00020, 5, 0x00000001, 'd', "PM GPIO pin 5 is driven to 1 during sleep" },
182 { "PGSR_SS6", 0x40F00020, 6, 0x00000001, 'd', "PM GPIO pin 6 is driven to 1 during sleep" },
183 { "PGSR_SS7", 0x40F00020, 7, 0x00000001, 'd', "PM GPIO pin 7 is driven to 1 during sleep" },
184 { "PGSR_SS8", 0x40F00020, 8, 0x00000001, 'd', "PM GPIO pin 8 is driven to 1 during sleep" },
185 { "PGSR_SS9", 0x40F00020, 9, 0x00000001, 'd', "PM GPIO pin 9 is driven to 1 during sleep" },
[all …]
/openbmc/u-boot/doc/
H A DREADME.i2c11 U-Boot provides a scheme based on two 'claim' GPIOs, one driven by the
12 AP (Application Processor, meaning the main CPU) and one driven by the EC
H A DREADME.commands.itest4 Now table driven to allow the operators
/openbmc/phosphor-power/
H A DREADME.md12 - [phosphor-power-sequencer](phosphor-power-sequencer/README.md): JSON-driven
17 - [phosphor-regulators](phosphor-regulators/README.md): JSON-driven application
/openbmc/u-boot/doc/device-tree-bindings/gpio/
H A Dgpio-pcf857x.txt4 driven high by a pull-up current source or driven low to ground. This combines
/openbmc/qemu/hw/gpio/
H A Dnpcm7xx_gpio.c97 /* Calculate level of each pin driven by GPIO controller. */ in npcm7xx_gpio_update_pins()
103 * If a pin is driven to opposite levels by the GPIO controller and the in npcm7xx_gpio_update_pins()
116 /* Set pins to externally driven level. */ in npcm7xx_gpio_update_pins()
118 /* Set internally driven pins, ignoring any conflicts. */ in npcm7xx_gpio_update_pins()
122 /* Pins not driven, pulled up or pulled down are undefined */ in npcm7xx_gpio_update_pins()
/openbmc/u-boot/drivers/sound/
H A Dbroadwell_i2s.h33 /* Data driven (falling), data sampled (rising), idle state (low) */
35 /* Data driven (rising), data sampled (falling), idle state (low) */
37 /* Data driven (rising), data sampled (falling), idle state (high) */
39 /* Data driven (falling), data sampled (rising), idle state (high) */
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/gnuplot/
H A Dgnuplot_5.4.3.bb1 SUMMARY = "Gnuplot is a portable command-line driven graphing utility"
2 DESCRIPTION = "Gnuplot is a portable command-line driven interactive datafile \
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/netcat/
H A Dnetcat.inc5 'back-end' tool that can be used directly or easily driven by other \
/openbmc/openbmc/meta-openpower/recipes-phosphor/logging/
H A Dopenpower-libhei_git.bb4 "The library provides a set of tools to isolate hardware attentions driven \
/openbmc/u-boot/doc/device-tree-bindings/timer/
H A Darc_timer.txt24 as each timer is driven by the same core clock.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/
H A Dyajl_1.0.12.bb3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
H A Dyajl_2.1.0.bb3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/pugixml/
H A Dpugixml_1.15.bb6 data-driven tree queries."
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-extended/mime-construct/
H A Dmime-construct_1.11.bb3 It is entirely driven from the command line, it is \
/openbmc/qemu/docs/specs/
H A Dfsi.rst34 FSI is a bit-based protocol supporting synchronous and DMA-driven accesses
54 CFAM to be simultaneously driven from multiple FSI links. The modeling is not
/openbmc/openbmc/meta-openpower/conf/machine/include/
H A Dopenpower.inc28 # The openpower-occ-control application is data-driven and requires an input
/openbmc/openbmc/meta-asrock/meta-e3c246d4i/recipes-x86/chassis/x86-power-control/
H A Dpower-config-host0.json37 * I can tell. It does have an O_PWROK line that's driven

12345678