| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | brcm,ns2-pinmux.txt | 3 The Northstar2 IOMUX controller supports group based mux configuration. There
13 Northstar2 IOMUX and pin configuration registers.
24 List of pin names to change configuration
|
| H A D | fsl,imx8m-pinctrl.yaml | 32 Pinctrl node's client devices use subnodes for desired pin configuration.
51 "conf_reg" indicates the offset of pad configuration register.
59 "pad_setting" indicates the pad configuration value to be
|
| H A D | renesas,rzv2m-pinctrl.yaml | 15 Pin multiplexing and GPIO configuration is performed on a per-pin basis.
61 Pin controller client devices use pin configuration subnodes (children
62 and grandchildren) for desired pin configuration.
69 alternate function configuration number using the RZV2M_PORT_PINMUX()
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-image-process.rst | 38 and the analogue crop rectangle configuration.
40 The configuration of the frame rate is performed by selecting the desired
57 configuration is also typically the default.
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/msm/ |
| H A D | qcom,saw2.txt | 11 SAW2 revisions differ in the register offset and configuration data. Also, the
12 same revision of the SAW in different SoCs may have different configuration
16 configuration and initialization data. The compatible string is used to
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | aspeed,sdhci.yaml | 19 The two slots are supported by a common configuration area. As the SDHCIs for
20 the slots are dependent on the common configuration area, they are described
31 description: Common configuration registers
|
| /openbmc/linux/drivers/staging/media/av7110/ |
| H A D | Kconfig | 31 or /lib/firmware (depending on configuration of firmware hotplug).
34 EXTRA_FIRMWARE configuration option to build it into your
36 configuration option string.
92 or /lib/firmware (depending on configuration of firmware hotplug).
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 14 .. _ref-varcontext-configuration:
16 BitBake's own configuration
31 BitBake configuration
90 starting with ``PREFERRED_``. Those are normally set in the configuration
|
| /openbmc/dbus-sensors/ |
| H A D | README.md | 48 that dynamically create and update sensors configuration when system
49 configuration gets updated.
59 ## configuration section in dbus-sensors
61 Sensor devices are described using Exposes records in configuration file. Name
111 You will then create an entity-manager configuration file that is of type "ADC"
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-params.rst | 9 level, it can be used to provide configuration that may affect multiple
20 Parameters may be set in different configuration modes.
22 .. list-table:: Possible configuration modes
46 Generic configuration parameters
48 The following is a list of generic configuration parameters that drivers may
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | README.md | 16 The `phosphor-fan-monitor` application is controlled by a configuration file
89 firmware image on the BMC when changing the configuration, such as for testing
172 configuration. It is suggested that the value of this `comments` attribute be an
174 ignored when the JSON configuration is processed.
177 configuration hierarchy_**
184 "Fan monitoring configuration of X-number of fans",
224 fan presence configuration instead of the config file located under the
|
| /openbmc/openbmc/poky/meta/recipes-core/sysvinit/sysvinit-inittab/ |
| H A D | inittab | 1 # /etc/inittab: init(8) configuration.
7 # Boot-time system configuration/initialization script.
|
| /openbmc/openbmc/poky/meta/recipes-support/apr/apr/ |
| H A D | 0005-configure.in-fix-LTFLAGS-to-make-it-work-with-ccache.patch | 9 | libtool: compile: unable to infer tagged configuration
11 | libtool: compile: unable to infer tagged configuration
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | device.cpp | 94 if (configuration) in configure()
96 configuration->execute(services, system, chassis, *this); in configure()
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/btrfsmaintenance/files/ |
| H A D | 0002-add-WantedBy-directive-to-btrfsmaintenance-refresh.s.patch | 7 configuration file deployed in the package, afterwards disable the
8 service, so that is only triggered when the configuration file has
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | ipcompliance.md | 18 the user acknowledges this risk by adding the following configuration:
22 You can provide this configuration as part of your `local.conf`, `distro.conf`,
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/ |
| H A D | fsl,layerscape-scfg.yaml | 14 SCFG is the supplemental configuration unit, that provides SoC specific
15 configuration and status registers for the chip. Such as getting PEX port
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/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
6 # which contains other examples of configuration which can be placed in this file
60 # from these files if no changes were made to the configuration. If changes were made
61 # to the configuration, only shared state files where the state was still valid would
89 # As an example of a subclass there is a "bleeding" edge policy configuration
96 # Package Management configuration
121 # Extra image configuration defaults
165 # Interactive shell configuration
223 # Qemu configuration
|
| /openbmc/openbmc/meta-amd/meta-daytonax/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
6 # which contains other examples of configuration which can be placed in this file
60 # from these files if no changes were made to the configuration. If changes were made
61 # to the configuration, only shared state files where the state was still valid would
89 # As an example of a subclass there is a "bleeding" edge policy configuration
96 # Package Management configuration
121 # Extra image configuration defaults
165 # Interactive shell configuration
223 # Qemu configuration
|
| /openbmc/linux/drivers/net/usb/ |
| H A D | kaweth.c | 231 struct kaweth_ethernet_configuration configuration; member
243 &kaweth->configuration, in kaweth_read_configuration()
244 sizeof(kaweth->configuration), in kaweth_read_configuration()
989 dev_info(dev, "Statistics collection: %x\n", kaweth->configuration.statistics_mask); in kaweth_probe()
990 …dev_info(dev, "Multicast filter limit: %x\n", kaweth->configuration.max_multicast_filters & ((1 <<… in kaweth_probe()
991 dev_info(dev, "MTU: %d\n", le16_to_cpu(kaweth->configuration.segment_size)); in kaweth_probe()
992 dev_info(dev, "Read MAC address %pM\n", kaweth->configuration.hw_addr); in kaweth_probe()
994 if(!memcmp(&kaweth->configuration.hw_addr, in kaweth_probe()
1047 eth_hw_addr_set(netdev, (u8 *)&kaweth->configuration.hw_addr); in kaweth_probe()
1051 netdev->mtu = le16_to_cpu(kaweth->configuration.segment_size); in kaweth_probe()
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | README.md | 16 The `phosphor-fan-presence-tach` application is controlled by a configuration
87 firmware image on the BMC when changing the configuration, such as for testing
150 configuration. It is suggested that the value of this `comments` attribute be an
152 ignored when the JSON configuration is processed.
155 configuration hierarchy_**
205 fan presence configuration instead of the config file located under the
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | st,stpmic1.yaml | 117 description: mask reset for this regulator, the regulator configuration
140 description: mask reset for this regulator, the regulator configuration
162 description: mask reset for this regulator, the regulator configuration
181 description: mask reset for this regulator, the regulator configuration
205 description: mask reset for this regulator, the regulator configuration
228 description: mask reset for this regulator, the regulator configuration
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | fimc.rst | 31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
94 In typical use case there could be a following capture pipeline configuration:
98 configuration flow must be from left to right, and the video node is
101 When we don't use sub-device user space API the whole configuration of all
104 the sub-devices (format, crop), to avoid resetting the subdevs' configuration
105 when the last configuration steps at the video node is performed.
|
| /openbmc/u-boot/board/keymile/kmp204x/ |
| H A D | pbi.cfg | 65 #Initialize eSPI controller, default configuration is slow for eSPI to
66 #load data, this configuration comes from u-boot eSPI driver.
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | ti,cdce706.txt | 15 configuration. Use clk_in0 and clk_in1 in case of independent
16 single-ended LVCMOS inputs configuration.
|