| /openbmc/pldm/configurations/ |
| H A D | meson.build | 15 install_subdir('../oem/ibm/configurations/fru', install_dir: package_datadir)
17 '../oem/ibm/configurations/events',
21 '../oem/ibm/configurations/bios',
25 '../oem/ibm/configurations/fru_master.json',
29 '../oem/ibm/configurations/entityMap.json',
33 '../oem/ibm/configurations/fileTable.json',
37 '../oem/ibm/configurations/host_eid',
|
| /openbmc/linux/include/linux/mfd/wm8994/ |
| H A D | pdata.h | 33 * DRC configurations are specified with a label and a set of register
38 * Configurations may be generated by hand or by using the DRC control
48 * ReTune Mobile configurations are specified with a label, sample
51 * Configurations are expected to be generated using the ReTune Mobile
61 * Multiband compressor configurations are specified with a label and
62 * two sets of values to write. Configurations are expected to be
76 * VSS HPF configurations are specified with a label and two values to
77 * write. Configurations are expected to be generated using the
87 * VSS configurations are specified with a label and array of values
88 * to write. Configurations are expected to be generated using the
[all …]
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 14 programming of the CoreSight system with pre-defined configurations that
20 be defined and enabled as named configurations.
73 Configurations section in Basic Concepts
133 Viewing Configurations and Features
136 The set of configurations and features that are currently loaded into the
148 configurations features
153 $ cd configurations/
209 Using Configurations in perf
212 The configurations loaded into the CoreSight configuration management are
240 When configurations are selected in this way, then the trace sink used is
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/proftpd/files/ |
| H A D | close-RequireValidShell-check.patch | 10 sample-configurations/basic.conf | 1 +
13 diff --git a/sample-configurations/basic.conf b/sample-configurations/basic.conf
15 --- a/sample-configurations/basic.conf
16 +++ b/sample-configurations/basic.conf
|
| /openbmc/u-boot/include/configs/ |
| H A D | socfpga_arria10_socdk.h | 16 * U-Boot general configurations
19 /* Memory configurations */
25 * U-Boot environment configurations
29 * Serial / UART configurations
41 * Flash configurations
|
| H A D | socfpga_stratix10_socdk.h | 14 * U-Boot general configurations
26 * U-Boot console configurations
38 * U-Boot run time memory configurations
49 * U-Boot environment configurations
124 * External memory configurations
138 * Serial / UART configurations
144 * Timer & watchdog configurations
149 * SDMMC configurations
155 * Flash configurations
|
| /openbmc/linux/Documentation/usb/ |
| H A D | gadget_configfs.rst | 18 A gadget is seen by its host as a set of configurations, each of which contains
24 Creating a gadget means deciding what configurations there will be
103 2. Creating the configurations
106 Each gadget will consist of a number of configurations, their corresponding
155 4. Associating the functions with their configurations
159 configurations specified and a number of functions available. What remains
161 function can be used in multiple configurations). This is achieved with
178 configurations and functions.
236 Remove functions from configurations::
249 Remove strings directories in configurations:
[all …]
|
| /openbmc/openbmc/poky/scripts/lib/resulttool/ |
| H A D | manualexecution.py | 60 configurations = {}
61 configurations['LAYERS'] = layers
62 configurations['STARTTIME'] = datetime.datetime.now().strftime('%Y%m%d%H%M%S')
63 configurations['TEST_TYPE'] = 'manual'
64 configurations['TEST_MODULE'] = test_module
66 extra_config = set(store_map['manual']) - set(configurations)
84 configurations[config] = value_conf
85 return configurations
127 configurations = self._get_config(config_options, test_module)
128 result_id = 'manual_%s_%s' % (test_module, configurations['STARTTIME'])
[all …]
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/configuration/ |
| H A D | entity-manager_%.bbappend | 6 rm -f ${D}${datadir}/entity-manager/configurations/*.json
7 install -d ${D}${datadir}/entity-manager/configurations
8 … install -m 0444 ${UNPACKDIR}/ethanolx-baseboard.json ${D}${datadir}/entity-manager/configurations
9 install -m 0444 ${UNPACKDIR}/ethanolx-chassis.json ${D}${datadir}/entity-manager/configurations
|
| /openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/configuration/ |
| H A D | entity-manager_%.bbappend | 7 rm -f ${D}${datadir}/entity-manager/configurations/*.json
8 install -d ${D}${datadir}/entity-manager/configurations
9 … install -m 0444 ${UNPACKDIR}/daytonax-baseboard.json ${D}${datadir}/entity-manager/configurations
10 install -m 0444 ${UNPACKDIR}/daytonax-chassis.json ${D}${datadir}/entity-manager/configurations
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 7 configurations.
26 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
27 path. In other configurations, other clocks (such as tx_125, rmii) may
31 In some configurations (e.g. GMII/RGMII), this clock is derived from the
32 PHY's RX clock output. In other configurations, other clocks (such as
44 The master bus interface clock. Only required in configurations that use a
56 Note: Support for additional IP configurations may require adding the
59 Configurations exist where multiple similar clocks are used at once, e.g. all
64 This will allow easy support for configurations that support multiple PHY
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 10 configurations.
29 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
30 path. In other configurations, other clocks (such as tx_125, rmii) may
34 In some configurations (e.g. GMII/RGMII), this clock is derived from the
35 PHY's RX clock output. In other configurations, other clocks (such as
47 The master bus interface clock. Only required in configurations that use a
59 Note: Support for additional IP configurations may require adding the
62 Configurations exist where multiple similar clocks are used at once, e.g. all
67 This will allow easy support for configurations that support multiple PHY
|
| /openbmc/linux/Documentation/arch/xtensa/ |
| H A D | booting.rst | 11 - For configurations without MMU, with region protection or with MPU the
13 - For configurations with region translarion MMU or with MMUv3 and CONFIG_MMU=n
16 - For configurations with MMUv2 the address must be a virtual address in the
18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
|
| /openbmc/linux/drivers/hwtracing/coresight/ |
| H A D | coresight-syscfg.h | 18 * When unloading configurations cannot be activated.
29 * Contains lists of the loaded configurations and features, plus a list of CoreSight devices
39 * @load_order_list: Ordered list of owners for dynamically loaded configurations.
41 * @cfgfs_subsys: configfs subsystem used to manage configurations.
86 * unload of configurations and features. Caller loading a config
|
| H A D | coresight-syscfg.c | 16 * cscfg_ API manages configurations and features for the entire coresight
19 * It allows the loading of configurations and features, and loads these into
502 /* next any configurations to check feature dependencies */ in cscfg_load_owned_cfgs_feats()
518 /* set configurations as available to activate at the end of the load process */
532 * Create and register each of the configurations and features with configfs.
564 * To facilitate dynamic loading and unloading, features and configurations
567 * As later loaded configurations can use earlier loaded features, creating load
642 * cscfg_unload_config_sets - unload a set of configurations by owner.
645 * the load owner of that set. Later loaded configurations can depend on
649 * 1) no configurations are active.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | pstore-blk.rst | 20 divides all configurations into two parts, configurations for user and
21 configurations for driver.
23 Configurations for user determine how pstore/blk works, such as pmsg_size,
27 Configurations for driver are all about block device and non-block device,
30 Configurations for user
33 All of these configurations support both Kconfig and module parameters, but
40 The detail of each configurations may be of interest to you.
154 Configurations for driver
|
| /openbmc/entity-manager/scripts/ |
| H A D | validate_configs.py | 4 A tool for validating entity manager configurations.
51 "(__file__/../../configurations/**.json)"
58 "A file with a list of configurations to ignore should "
102 configs_dir = os.sep + os.path.join(*source_dir, "configurations")
109 sys.stderr.write("Could not guess location of configurations\n")
|
| /openbmc/linux/Documentation/arch/arm/pxa/ |
| H A D | mfp.rst | 16 out of the GPIO controller. In addition to pin-mux configurations, the MFP
95 NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
99 2. prepare an array for the initial pin configurations, e.g.::
123 a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
127 b) when there is only one possible pin configurations for a component,
195 configurations, these definitions are processor and platform independent, and
211 configurations
215 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
264 Examples of pin configurations are::
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | source_file_format.txt | 87 To identify FIT sub-nodes representing images, hashes, configurations (which
109 o configurations
135 - configurations : Contains a set of available configuration nodes and
205 6) '/configurations' node
208 The 'configurations' node is optional. If present, it allows to create a
209 convenient, labeled boot configurations, which combine together kernel images
212 The 'configurations' node has has the following structure:
214 o configurations
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | maint-appx.rst | 17 list all necessary patches, configurations, branches, tags, and feature
24 images based on their configurations and features.
67 To see the features and configurations for a particular Yocto Linux
131 all the branches, tags, patches and configurations that need to be
154 combination of all supported boards and configurations.
186 has configurations and features grouped under the
188 configurations for the BeagleBone Board assuming a
|
| /openbmc/u-boot/doc/ |
| H A D | README.srio-pcie-boot-corenet | 62 Then, it will finish necessary configurations for slave's boot from
73 necessary configurations.
85 1. Slave's RCW with SRIO or PCIE boot configurations, and all cores in holdoff
86 configurations.
106 UCode, ENV stored in master's NorFlash, and any other configurations
|
| /openbmc/linux/tools/power/cpupower/man/ |
| H A D | cpupower-set.1 | 3 cpupower\-set \- Set processor power related kernel or hardware configurations
10 \fBcpupower set \fP sets kernel configurations or directly accesses hardware
14 are applied on all cores. How to modify single core configurations is
|
| /openbmc/linux/arch/arm/mach-s3c/ |
| H A D | Kconfig.s3c64xx | 80 Common setup code for S3C64XX KEYPAD GPIO configurations
85 Common setup code for S3C64XX SDHCI GPIO configurations
90 Common setup code for SPI GPIO configurations
|
| /openbmc/entity-manager/ |
| H A D | .prettierignore | 1 configurations/*
2 !configurations/**/*.md
|
| H A D | README.md | 6 the number of independent system configurations one needs to create.
62 more readily, and system configurations can be "verified" rather than
66 are located in the ./configurations directory in the entity manager
69 contains all hardware configurations that OpenBMC supports, to allows an easy
76 configurations, and use them to execute and enable the features that they
|