/openbmc/linux/Documentation/userspace-api/media/rc/ |
H A D | lirc-get-features.rst | 88 The driver supports changing the duty cycle using 95 The driver supports changing the active transmitter(s) using 102 The driver supports setting the receive carrier frequency using 130 The driver supports measuring of the modulation frequency using 137 The driver supports learning mode using 150 The driver supports sending (also called as IR blasting or IR TX) using
|
/openbmc/linux/arch/powerpc/crypto/ |
H A D | Kconfig | 13 Architecture: powerpc64 using 25 Architecture: powerpc64 using 61 Architecture: powerpc using 72 Architecture: powerpc using 83 Architecture: powerpc using: 107 Architecture: powerpc64 using:
|
/openbmc/linux/fs/jbd2/ |
H A D | Kconfig | 14 If you are using ext4 or OCFS2, you need to say Y here. 15 If you are not using ext4 or OCFS2 then you will 26 If you are using the ext4 journaled file system (or 27 potentially any other filesystem/device using JBD2), this option
|
/openbmc/sdbusplus/tools/sdbusplus/templates/ |
H A D | method.aserver.tag.hpp.mako | 8 using value_types = std::tuple<${m_param}>; 9 using return_type = ${m_return};
|
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/apache2/apache2/ |
H A D | 0003-apache2-do-not-export-apr-apr-util-symbols-when-usin.patch | 4 Subject: [PATCH] apache2: do not export apr/apr-util symbols when using shared 7 There is no need to "suck in" the apr/apr-util symbols when using 12 Note: EXPORT_DIRS change is conditional on using shared apr
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | bmaptool.rst | 15 - If you are using Ubuntu or Debian distributions, you can install 16 the ``bmap-tools`` package using the following command and then 23 need to build bmaptool before using it. Use the following command:: 29 any type of image. Use these steps to flash an image using bmaptool: 42 #. *Flash the Device:* Flash the device with the image by using bmaptool
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | typec_bus.rst | 8 Alternate modes require communication with the partner using Vendor Defined 14 modes by using the SVID and the mode number. 25 driver will happen using the same API. 49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`. 51 If the communication with the partner using the SVID specific commands results 53 needs to notify the bus using :c:func:`typec_altmode_notify()`. The driver 55 parameter. The bus driver will then configure the mux behind the connector using 88 plug alternate modes using :c:func:`typec_altmode_get_plug()`, and take over
|
/openbmc/linux/tools/testing/selftests/amd-pstate/ |
H A D | gitsource.sh | 300 …'/${all_scaling_names[0]}-${gitsource_governors[0]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 301 …'/${all_scaling_names[0]}-${gitsource_governors[1]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 305 …'/${all_scaling_names[1]}-${gitsource_governors[0]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 306 …'/${all_scaling_names[1]}-${gitsource_governors[1]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 310 …'/${all_scaling_names[0]}-${gitsource_governors[0]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 311 …'/${all_scaling_names[0]}-${gitsource_governors[1]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 312 …'/${all_scaling_names[1]}-${gitsource_governors[0]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "… 313 …'/${all_scaling_names[1]}-${gitsource_governors[1]}/p' $OUTFILE_GIT.csv)" using $4:xtic(2) title "…
|
H A D | tbench.sh | 287 …'/${all_scaling_names[0]}-${tbench_governors[0]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 288 …'/${all_scaling_names[0]}-${tbench_governors[1]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 292 …'/${all_scaling_names[1]}-${tbench_governors[0]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 293 …'/${all_scaling_names[1]}-${tbench_governors[1]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 297 …'/${all_scaling_names[0]}-${tbench_governors[0]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 298 …'/${all_scaling_names[0]}-${tbench_governors[1]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 299 …'/${all_scaling_names[1]}-${tbench_governors[0]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "… 300 …'/${all_scaling_names[1]}-${tbench_governors[1]}/p' $OUTFILE_TBENCH.csv)" using $4:xtic(2) title "…
|
/openbmc/linux/Documentation/PCI/endpoint/ |
H A D | pci-endpoint.rst | 6 endpoint controller driver, endpoint function driver, and using configfs 63 devm_pci_epc_create() or pci_epc_create() using devm_pci_epc_destroy() or 97 using this API. 118 free the memory space allocated using pci_epc_mem_alloc_addr(). 125 using these APIs. 134 Release the reference to the PCI endpoint controller obtained using 178 The PCI Function driver can then register the PCI EPF driver by using 183 The PCI Function driver can unregister the PCI EPF driver by using 188 The PCI Function driver can allocate space for a particular BAR using 194 (using pci_epf_alloc_space) by invoking pci_epf_free_space(). [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | marvell-pxa168.txt | 11 - #address-cells: must be 1 when using sub-nodes. 12 - #size-cells: must be 0 when using sub-nodes. 15 The MAC address will be determined using the optional properties
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/openct/openct/ |
H A D | 0001-m4-Just-emit-the-first-line-of-compiler-version.patch | 24 - echo "/* generated using a gnu compiler version" `$CC --version` "*/" \ 25 + echo "/* generated using a gnu compiler version" `$CC --version|head -1` "*/" \ 28 echo "/* generated using $CC */" >>$ac_stdint_h
|
/openbmc/openbmc/poky/meta/recipes-graphics/kmscube/ |
H A D | kmscube_git.bb | 1 SUMMARY = "Demo application to showcase 3D graphics using kms and gbm" 3 without a compositor like X11, wayland or similar, using DRM/KMS (kernel mode \ 4 setting), GBM (graphics buffer manager) and EGL for rendering content using \
|
/openbmc/u-boot/doc/ |
H A D | README.mpc83xxads | 19 GNU assembler version 2.15 (powerpc-linux) using BFD version 2.15 58 Assuming you're using BASH shell: 68 5.0 Download over serial line using Kermit: 82 5.1 Reflash U-Boot Image using U-Boot
|
/openbmc/linux/Documentation/admin-guide/gpio/ |
H A D | gpio-aggregator.rst | 10 Aggregating GPIOs using Sysfs 13 GPIO controllers are exported to userspace using /dev/gpiochip* character 20 using standard UNIX file ownership and permissions. Furthermore, this 33 aggregate to the "new_device" file, using the format 83 Example: If "door" is a GPIO-operated device described in DT, using its own 97 2. Binding manually using "driver_override":
|
/openbmc/docs/testing/ |
H A D | run-test-docker.md | 3 Running OpenBMC automation using Docker involves creating a Docker image and 28 "openbmc/ubuntu-robot-qemu". You can check images using "docker images" 39 ## Code update process using robot test code 65 Example to run BMC code update using witherspoon-20170614071422.all.tar image 93 ###### _Note: This runs a Docker container using openbmc/ubuntu-robot-qemu image._ 95 ###### _Robot test code is extracted and ran on this container using run-robot.sh script._
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | selection-api-configuration.rst | 19 control the rounding behaviour using 50 coordinates are obtained using ``V4L2_SEL_TGT_COMPOSE_BOUNDS``. All 62 control rounding behaviour using 65 For capture devices the default composing rectangle is queried using 70 ``V4L2_SEL_TGT_COMPOSE_PADDED``. It contains all pixels defined using 90 cropping coordinates are obtained using ``V4L2_SEL_TGT_CROP_BOUNDS``. 93 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 103 For output devices the default cropping rectangle is queried using 134 and the height of rectangles obtained using ``V4L2_SEL_TGT_CROP`` and 136 scaling is applied. The application can compute the scaling ratios using
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | images.rst | 20 file before using the BitBake command to build the image: 38 all the pieces required to run builds using the build system as well 39 as the build system itself. You can boot and run the image using 61 for development work using the host. The image includes headers and 73 suitable for development using the target. 79 for development work using the host. The image includes headers and 100 and is suitable for development using the target. 108 development using the host. The image includes libraries needed to 115 and is suitable for development using the target. 132 ":ref:`dev-manual/wayland:using wayland and weston`"
|
/openbmc/linux/drivers/slimbus/ |
H A D | Kconfig | 21 programmed using Linux kernel. 32 Component is programmed using Linux kernel. 34 communicating with slave HW directly over the bus using messaging
|
/openbmc/qemu/docs/system/ |
H A D | target-s390x.rst | 11 When using KVM as accelerator, QEMU can emulate CPUs up to the generation 12 of the host. When using the default cpu model with TCG as accelerator, 20 z/VM; virtio devices (especially using virtio-ccw) make up the bulk of
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | drivers-on-gpio.rst | 2 Subsystem drivers using GPIO 7 drivers can quite easily interconnect with other kernel subsystems using 25 up to three buttons by simply using GPIOs and no mouse port. You can cut the 54 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using 58 to this SPI by using the mmc_spi host from the MMC/SD card subsystem. 60 - w1-gpio: drivers/w1/masters/w1-gpio.c is used to drive a one-wire bus using 89 Consumer Electronics Control bus using only GPIO. It is used to communicate 94 AC charger or more complex tasks such as indicating charging status using 99 - gpio-mux: drivers/mux/gpio.c is used for controlling a multiplexer using 107 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | rt5682.txt | 32 1: using GPIO2 pin as dmic1 data pin 33 2: using GPIO5 pin as dmic1 data pin 36 0: using GPIO1 pin as dmic1 clock pin 37 1: using GPIO3 pin as dmic1 clock pin 41 1: using JD1 as JD source
|
/openbmc/qemu/ |
H A D | qemu.sasl | 5 # If you are only using TLS, then you can turn on any mechanisms 8 # If you are only using UNIX sockets then encryption is not 20 # If using TLS with VNC, or a UNIX socket only, it is possible to 37 # If using scram-sha-256 for username/passwds, then this is the file
|
/openbmc/linux/arch/sparc/crypto/ |
H A D | Kconfig | 37 Architecture: sparc64 using crypto instructions, when available 57 Architecture: sparc64 using crypto instructions, when available 67 Architecture: sparc64 using crypto instructions, when available 77 Architecture: sparc64 using crypto instructions
|
/openbmc/linux/drivers/nfc/microread/ |
H A D | Kconfig | 15 This module adds support for the i2c interface of adapters using 16 Inside microread chipsets. Select this if your platform is using 27 This module adds support for the mei interface of adapters using
|