Searched refs:output (Results 4001 – 4025 of 6206) sorted by relevance
1...<<161162163164165166167168169170>>...249
/openbmc/linux/net/ipv4/ |
H A D | ipcomp.c | 165 .output = ipcomp_output
|
/openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
H A D | aspeed-pwm-tacho.txt | 6 There can be upto 8 fans supported. Each fan can have one PWM output and
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | intel,pinctrl-keembay.yaml | 14 of pin directions, input/output values and configuration
|
/openbmc/linux/samples/pktgen/ |
H A D | functions.sh | 166 local node_cpu_range_list=`cut -f1- -d, --output-delimiter=" " \
|
/openbmc/linux/drivers/staging/media/atomisp/ |
H A D | notes.txt | 17 struct with various input and output parameters and then calling
|
/openbmc/linux/arch/alpha/lib/ |
H A D | ev6-csum_ipv6_magic.S | 131 zapnot $0,15,$1 # U : Start folding output (1 cycle stall on $0)
|
/openbmc/linux/net/ipv6/ |
H A D | ipcomp6.c | 184 .output = ipcomp_output,
|
H A D | ndisc.c | 90 .output = neigh_resolve_output, 98 .output = neigh_resolve_output, 105 .output = neigh_direct_output, 350 neigh->output = neigh_direct_output; in ndisc_constructor() 369 neigh->output = neigh->ops->connected_output; in ndisc_constructor() 371 neigh->output = neigh->ops->output; in ndisc_constructor()
|
/openbmc/linux/arch/arm/boot/dts/samsung/ |
H A D | exynos5410-smdk5410.dts | 33 clock-output-names = "fin_pll";
|
/openbmc/linux/arch/arm64/boot/dts/freescale/ |
H A D | imx8mn-bsh-smm-s2pro.dts | 77 fsl,sai-mclk-direction-output;
|
/openbmc/linux/drivers/iio/dac/ |
H A D | m62332.c | 166 .output = 1, \
|
H A D | ad8801.c | 92 .output = 1, \
|
H A D | dpot-dac.c | 48 .output = 1,
|
/openbmc/linux/Documentation/devicetree/bindings/spi/ |
H A D | qcom,spi-geni-qcom.yaml | 16 (an output FIFO and an input FIFO) for serial peripheral interface (SPI)
|
/openbmc/linux/arch/arm64/boot/dts/cavium/ |
H A D | thunder2-99xx.dtsi | 94 clock-output-names = "clk125mhz";
|
/openbmc/linux/drivers/iio/potentiometer/ |
H A D | ad5272.c | 58 .output = 1,
|
/openbmc/linux/arch/arm64/boot/dts/arm/ |
H A D | vexpress-v2f-1xv7-ca53x2.dts | 120 clock-output-names = "smclk";
|
/openbmc/dbus-sensors/src/ |
H A D | meson.build | 12 output: 'dbus-sensor_config.h',
|
/openbmc/linux/arch/arm64/boot/dts/amlogic/ |
H A D | meson-s4.dtsi | 60 clock-output-names = "xtal";
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 198.out | 1 QA output created by 198
|
H A D | 271.out | 1 QA output created by 271 459 read failed: Input/output error 474 read failed: Input/output error 481 read failed: Input/output error 504 write failed: Input/output error 519 write failed: Input/output error 526 write failed: Input/output error 558 read failed: Input/output error
|
/openbmc/linux/Documentation/powerpc/ |
H A D | hvcs.rst | 145 output of the sysfs directory shows where these numbers are presented:: 169 For the above examples the following output is a result of cat'ing the 184 The output from reading the "dev" attribute is the char device major and 189 Given the example output above, to manually create a /dev/hvcs* node entry 240 applications that are invoked from the console that they should output 275 from a vty following output of data to the vty the vty adapter may not have 450 Q: Why is the console output all strange and unintelligible?
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | kernel-yocto.bbclass | 531 …atal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-8'))) 539 …atal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-8'))) 583 bb.fatal( "Cannot gather config fragments for audit: %s" % e.output.decode("utf-8") ) 592 # streamline the output to only report options that could be boot issues, 602 …bb.fatal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-… 624 …bb.fatal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-… 643 …bb.fatal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-…
|
/openbmc/qemu/docs/about/ |
H A D | emulation.rst | 156 is performed on input or output. This is because gdb semihosting 224 To show output, you may use this additional parameter:: 579 access was. Not compatible with the pattern option. Example output:: 589 a device. Example output:: 608 Please be aware that this will generate a lot of output. 615 which will output an execution trace following this structure:: 630 The output can be filtered to only track certain instructions or
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | devtool-reference.rst | 36 -d, --debug Enable debug output 38 --color COLOR Colorize output (where COLOR is auto, always, never) 61 deploy-target Deploy recipe output files to live target machine 62 undeploy-target Undeploy recipe output files in live target machine 79 As directed in the general help output, you can 508 output to the live target machine:: 556 output from the target machine. For the ``devtool undeploy-target`` 601 Here is sample output after using
|
1...<<161162163164165166167168169170>>...249