| /openbmc/linux/drivers/char/tpm/ |
| H A D | Kconfig | 15 say Yes and it will be accessible from within Linux. For
55 within Linux. To compile this driver as a module, choose M here;
67 within Linux. To compile this driver as a module, choose M here;
75 say Yes and it will be accessible from within Linux.
85 say Yes and it will be accessible from within Linux.
97 within Linux on Socionext SynQuacer platform.
115 accessible from within Linux.
125 Specification 0.20 say Yes and it will be accessible from within
136 from within Linux.
145 say Yes and it will be accessible from within Linux. To
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices-system-cpu | 64 Description: internal kernel map of CPUs within the same core.
69 Description: human-readable list of CPUs within the same core.
86 Description: internal kernel map of CPUs within the same die.
94 Description: human-readable list of CPUs within the same die.
99 Description: internal kernel map of CPUs within the same cluster.
103 Description: human-readable list of CPUs within the same cluster.
108 Description: internal kernel map of cpuX's hardware threads within the same
113 Description: human-readable list of cpuX's hardware threads within the same
119 Description: internal kernel map of cpuX's hardware threads within the same
124 Description: human-readable list of cpuX's hardware threads within the same
|
| /openbmc/docs/designs/ |
| H A D | target-fail-monitoring.md | 15 is used within OpenBMC.
21 target or service within them hitting some sort of error condition. In some
25 critical that if a systemd target fails within OpenBMC, the user be notified.
28 a running service within that target fails. Some services are not all that
38 state management and systemd within OpenBMC.
52 The proposal within this document is to monitor for these other results and log
57 restarts within a 30 second window.
96 - Must be able to monitor any arbitrary systemd service within OpenBMC
162 Units have an OnError directive. Could put the error logging logic within that
166 Could implement this within the existing state manager applications since they
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mips/cavium/ |
| H A D | ciu.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 within the bank and may have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| H A D | ciu2.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 the bit within the bank and may also have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| /openbmc/linux/Documentation/devicetree/bindings/ptp/ |
| H A D | ptp-ines.txt | 7 port index within the IP core.
14 Required format of the port handle within the PHY node:
17 the port channel within the IP core
|
| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 31 within this document
47 If someone wishes to create a recipe within OpenBMC to point to an external
53 If a recipe is created within OpenBMC (in any meta-X layer) to point to an
58 within OpenBMC
112 For example, OpenPOWER systems have a separate power management device within
121 for hosting a hardware/vendor specific repository within the openbmc github
147 We need a policy within OpenBMC on how we handle each of these types of
153 repositories that are hosted within OpenBMC. Having the source under the OpenBMC
159 big changes like that on repositories hosted within OpenBMC directly (vs. trying
166 new code development within the project. How useful is the feature, how many
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | python-development-shell.rst | 6 Similar to working within a development shell as described in the
7 previous section, you can also spawn and work within an interactive
30 See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:functions you can call from within …
44 interpreter within the OpenEmbedded build environment. The
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 6 of components within the audio subsystem. This is noticeable on PCs when an
11 because the components within the subsystem are being dynamically powered
21 suppression. Pops can be reduced within playback by powering the audio
50 An unwanted zipper noise can occur within the audio playback or capture stream
|
| H A D | dapm.rst | 9 Linux devices to use the minimum amount of power within the audio
14 all power switching is done within the ASoC core. No code changes or
17 activity and audio mixer settings within the device.
19 DAPM spans the whole machine. It covers power control within the entire
23 There are 4 power domains within DAPM
109 Inter widget audio data buffer within a DSP.
116 Sample Rate Converter within DSP or CODEC
118 Asynchronous Sample Rate Converter within DSP or CODEC
170 audio paths within the audio subsystem. They have the following form:-
248 Widgets are connected to each other within the codec, platform and machine by
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | chassis.md | 5 A chassis within the system.
19 | number | yes | number | Chassis number within the system. Cha…
21 | devices | no | array of [devices](device.md) | One or more devices within the chassi…
|
| /openbmc/u-boot/doc/device-tree-bindings/clock/ |
| H A D | st,stm32-rcc.txt | 35 The secondary index is the bit number within the RCC register bank, starting
39 Where bit_offset is the bit offset within the register (LSB is 0, MSB is 31).
84 The index is the bit number within the RCC registers bank, starting from RCC
87 Where bit_offset is the bit offset within the register.
|
| /openbmc/phosphor-state-manager/ |
| H A D | README.md | 4 the state of different objects within OpenBMC. This currently includes the BMC,
16 applications running within an OpenBMC system. This tool itself runs within an
20 As with all OpenBMC applications, interfaces and properties within
32 ensure all generic services installed within the PSM targets complete
39 - Use systemd targets for everything and keep the code within PSM minimal
50 and `Ready` once all services within the default.target have executed. It is
87 and host (see `obmcutil --help` within an OpenBMC system).
99 The `PowerRestoreDelay` property within the interface defines a maximum time the
107 enabled within PSM that will not allow chassis or host operations (other then
142 Active state though so that the chassis object within PSM will correctly
|
| /openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/ |
| H A D | 0002-binutils-cross-Do-not-generate-linker-script-directo.patch | 6 We don't place target libraries within ${exec_prefix}, we'd always place these
7 within the target sysroot within the standard library directories. Worse, the
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | runqemu.README | 6 and x86 (32 and 64 bit) images. The scripts can be used within the OE build
24 When used within the build system, it will default to qemuarm, ext2 and the last kernel and
37 - You can access the host computer at 192.168.7.1 within the image.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 10 entry if it arrived within the configured timeout.
25 entry if it arrived within the configured timeout.
27 from this same entry too if it arrived within the configured
78 entry if it arrived on channel <m> within the configured
102 entry if it arrived on channel <m> within the configured
105 from this same entry too if it arrived within the configured
|
| H A D | sysfs-devices | 9 devices within this tree will change.
15 within the /sys/devices tree of the individual devices.
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 33 name and an integer GPIO name within the port. For example, GPIO_PA0, GPIO_PN6,
37 implemented GPIOs within each port varies. GPIO registers within a controller
41 the mapping from port name to register offset within a controller, are both
45 sorted within a particular controller. Drivers need to map between the DT GPIO
49 represents the aggregate status for all GPIOs within a set of ports. Thus, the
58 handle subsets of the interrupts within a port. The status of each of these
|
| /openbmc/openbmc-tools/expectedJsonChecker/ |
| H A D | README.md | 5 expected entries by using logical operations against entries within another file
9 Expected entries that only want to be found within the input JSON should use a
16 entries within the BMC's enumerated sensor JSON output against an expected set
18 different based on specific entries within inventory. So given a dump of a
20 expected set of entries that should be contained within the sensor data is
22 determine if all the expected set of entries are found within the sensor data.
30 Filters can be used for whether or not a set of entries within the expected JSON
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | st,stm32-rcc.txt | 42 The secondary index is the bit number within the RCC register bank, starting
46 Where bit_offset is the bit offset within the register (LSB is 0, MSB is 31).
127 The index is the bit number within the RCC registers bank, starting from RCC
130 Where bit_offset is the bit offset within the register.
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
| H A D | libxdamage_1.1.6.bb | 6 rectangular areas within the drawable. The rectangles are guaranteed to \
10 or to have them partially processed within the X server to reduce the \
|
| /openbmc/linux/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 42 the fixed fields within these two options are administered by the Defense
77 systems within a single Domain of Interpretation (DOI). A DOI is a
82 mapping to hosts within the authority's domain. These mappings may be
123 a mapping table within CIPSO hosts to map these numbers to their
139 to identify which mapping was used for the values within the option.
151 all tags, as well as fields within a tag, are not aligned on any particular
230 restriction of 40 bytes the value within this field is between 4 and 34.
316 restriction of 40 bytes the value within this field is between 4 and 34.
347 by their position within a bit field. The length of each category is 2
350 value. The categories MUST be listed in ascending order within the tag.
[all …]
|
| /openbmc/docs/development/ |
| H A D | README.md | 15 repository, build, and test your changes within QEMU.
20 changes within QEMU.
|
| /openbmc/linux/Documentation/devicetree/bindings/pci/ |
| H A D | ti-pci.txt | 37 should contain the register offset within syscon
47 they are locally accessed within the DIF CS space
49 they are locally accessed within the DIF CS2 space
55 should contain the register offset within syscon
|
| /openbmc/linux/Documentation/mm/ |
| H A D | page_frags.rst | 6 which resides within a 0 or higher order compound page. Multiple
7 fragments within that page are individually refcounted, in the page's
32 only usable within the softirq context.
|