| /openbmc/openbmc/meta-raspberrypi/recipes-bsp/gpio-shutdown/ |
| H A D | gpio-shutdown.bb | 25 # Systemd init does not require any configuration.
29 … bbwarn "Not using sysvinit or systemd. The gpio-shutdown may require additional configuration."
|
| /openbmc/openbmc/poky/meta/recipes-support/libproxy/ |
| H A D | libproxy_0.5.4.bb | 1 SUMMARY = "Library providing automatic proxy configuration management"
4 configuration via different mechanisms (e.g. environment variables or \
|
| /openbmc/openbmc/meta-ampere/meta-jade/conf/templates/default/ |
| H A D | local.conf.sample | 2 # This file is your local configuration file and is where all local user settings
4 # to the system might want to change but pretty much any configuration option can
38 # from these files if no changes were made to the configuration. If changes were made
39 # to the configuration, only shared state files where the state was still valid would
67 # As an example of a subclass there is a "bleeding" edge policy configuration
74 # Package Management configuration
99 # Extra image configuration defaults
143 # Interactive shell configuration
201 # Qemu configuration
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/conf/templates/default/ |
| H A D | local.conf.sample | 2 # This file is your local configuration file and is where all local user settings
4 # to the system might want to change but pretty much any configuration option can
38 # from these files if no changes were made to the configuration. If changes were made
39 # to the configuration, only shared state files where the state was still valid would
67 # As an example of a subclass there is a "bleeding" edge policy configuration
74 # Package Management configuration
99 # Extra image configuration defaults
143 # Interactive shell configuration
201 # Qemu configuration
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | sdhci-st.txt | 22 - pinctrl-0: Phandle referencing pin configuration of the sd/emmc controller.
62 /* Example stih416e eMMC configuration */
75 /* Example SD stih407 family configuration */
91 /* Example eMMC stih407 family configuration */
|
| /openbmc/linux/Documentation/usb/ |
| H A D | functionfs.rst | 6 unique behaviour. It may be added to an USB configuration only after
10 the configuration).
28 numbers and changing of the configuration (which means that
30 configuration changes to (say) endpoint 2)). "ep0" is used
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | vimc.rst | 26 Each subdevice will come with its default configuration (pixelformat, height,
28 configuration on each linked subdevice to stream frames through the pipeline.
29 If the configuration doesn't match, the stream will fail. The ``v4l-utils``
31 ``v4l2-ctl`` that can be used to configure the vimc configuration. This sequence
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/ |
| H A D | README.md | 27 the `ARM_SYSTEMREADY_FIRMWARE` variable set at the MACHINE configuration level
37 at the MACHINE configuration level for this test case.
114 1. Set the `ARM_SYSTEMREADY_FIRMWARE` variable at the MACHINE configuration
115 level to list the build dependencies. The configuration file of the
117 2. Set the `ARM_SYSTEMREADY_ACS_CONSOLE` variable at the MACHINE configuration
119 to the configuration file of the [`fvp-base`][] machine.
130 the above **Reuse** section) at the MACHINE configuration level from the BSP
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | nvidia,tegra124-mc.yaml | 65 nvidia,emem-configuration:
93 - nvidia,emem-configuration
134 nvidia,emem-configuration = <
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | presence_detection.md | 17 Device operations like [configuration](configuration.md),
33 be determined prior to the first device operation (such as configuration). When
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | faq.rst | 16 ":ref:`kernel-dev/common:changing the configuration`"
19 How do I create configuration fragments?
23 ":ref:`kernel-dev/common:creating configuration fragments`"
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/amd/ |
| H A D | pds_vdpa.rst | 19 and VF PCI handling as well as for device configuration services.
24 The ``pds_vdpa`` device is enabled via multiple configuration steps and
61 The driver is enabled via the standard kernel configuration system,
|
| /openbmc/linux/Documentation/devicetree/bindings/display/mediatek/ |
| H A D | mediatek,hdmi.yaml | 56 - description: phandle to system configuration registers
57 - description: register offset in the system configuration registers
59 phandle link and register offset to the system configuration registers.
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | fsl,imx7d-pinctrl.yaml | 37 Pinctrl node's client devices use subnodes for desired pin configuration.
55 "conf_reg" indicates the offset of pad configuration register.
63 "pad_setting" indicates the pad configuration value to be applied.
|
| H A D | pinctrl-st.txt | 107 Required properties for pin configuration node:
108 - st,pins : Child node with list of pins with configuration.
114 Every PIO is represented with 4-7 parameters depending on retime configuration.
121 -mode :pin configuration is selected from one of the below values.
129 Possible retime configuration are:
|
| /openbmc/bmcweb/config/ |
| H A D | meson.build | 97 configuration: conf_data,
107 configuration: configuration_data({
117 configuration: configuration_data({
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | test_utils.hpp | 75 std::unique_ptr<Configuration> configuration{}; local
79 std::move(presenceDetection), std::move(configuration),
|
| /openbmc/linux/arch/arm/boot/dts/nvidia/ |
| H A D | tegra30-pegatron-chagall.dts | 1772 nvidia,emc-configuration = < 0x00000001
1808 nvidia,emc-configuration = < 0x00000003
1844 nvidia,emc-configuration = < 0x00000006
1880 nvidia,emc-configuration = < 0x0000000c
1915 nvidia,emc-configuration = < 0x00000017
1956 nvidia,emc-configuration = < 0x00000001
1992 nvidia,emc-configuration = < 0x00000003
2028 nvidia,emc-configuration = < 0x00000006
2064 nvidia,emc-configuration = < 0x0000000c
2099 nvidia,emc-configuration = < 0x00000017
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/cirrus/ |
| H A D | cs89x0.rst | 75 such, the configuration procedures differ somewhat between the two types of
156 Utility if you want to change the adapter's configuration in EEPROM.
160 or for interface configuration when an EEPROM is not used. (CS8920-based
186 another adapter exists. To change the adapter's configuration, run the
222 configuration when an EEPROM is not used.
230 configuration options are available on the command line::
251 will override the corresponding configuration value stored in
271 e) The minimum command-line configuration required if an EEPROM is
293 determine configuration information which is passed to a driver
294 module when it is loaded. All the configuration options which are
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | tvp514x.txt | 17 - hsync-active: HSYNC Polarity configuration for endpoint.
19 - vsync-active: VSYNC Polarity configuration for endpoint.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-test/cunit/files/ |
| H A D | fixup-install-docdir.patch | 5 The default configuration macros for CUnit install the documentation and
9 Upstream-Status: Inappropriate - configuration for OE build environment
|
| /openbmc/openbmc/poky/meta/ |
| H A D | recipes.txt | 1 recipes-bsp - Anything with links to specific hardware or hardware configuration informati…
12 recipes-sato - The Sato demo/reference UI/UX, its associated apps and configuration
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-devtools/gator-daemon/ |
| H A D | gator-daemon_7.8.0.bb | 8 # configuration requirement specified here:
9 # https://github.com/ARM-software/gator#kernel-configuration
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/ |
| H A D | fsl,layerscape-dcfg.yaml | 14 DCFG is the device configuration unit, that provides general purpose
15 configuration and status for the device. Such as setting the secondary
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 21 configuration is derived using that build system and the filters shown
32 OpenEmbedded build system configuration into the extensible SDK
33 configuration. Typically, these variables are specific to the machine
35 of the extensible SDK configuration.
67 - If your SDK configuration inherits additional classes using the
155 to set the variable in your distribution's configuration file. Doing so
169 When you make changes to your configuration or to the metadata and if
225 distribution's configuration file. Doing so creates an SDK installer
265 to find the configuration. The variable you need to set is
278 configuration file. You can then pass the variable to the SDK by
[all …]
|