| /openbmc/linux/drivers/net/ethernet/sfc/ |
| H A D | enum.h | 14 * @LOOPBACK_GMAC: loopback within GMAC
16 * @LOOPBACK_XGXS: loopback within BPX after XGXS
17 * @LOOPBACK_XAUI: loopback within BPX before XAUI serdes
18 * @LOOPBACK_GMII: loopback within BPX after GMAC
19 * @LOOPBACK_SGMII: loopback within BPX within SGMII
20 * @LOOPBACK_XGBR: loopback within BPX within XGBR
21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
22 * @LOOPBACK_XAUI_FAR: loopback within BPX after XAUI serdes
23 * @LOOPBACK_GMII_FAR: loopback within BPX before SGMII
24 * @LOOPBACK_SGMII_FAR: loopback within BPX after SGMII
[all …]
|
| /openbmc/linux/drivers/net/ethernet/sfc/siena/ |
| H A D | enum.h | 14 * @LOOPBACK_GMAC: loopback within GMAC
16 * @LOOPBACK_XGXS: loopback within BPX after XGXS
17 * @LOOPBACK_XAUI: loopback within BPX before XAUI serdes
18 * @LOOPBACK_GMII: loopback within BPX after GMAC
19 * @LOOPBACK_SGMII: loopback within BPX within SGMII
20 * @LOOPBACK_XGBR: loopback within BPX within XGBR
21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
22 * @LOOPBACK_XAUI_FAR: loopback within BPX after XAUI serdes
23 * @LOOPBACK_GMII_FAR: loopback within BPX before SGMII
24 * @LOOPBACK_SGMII_FAR: loopback within BPX after SGMII
[all …]
|
| /openbmc/linux/drivers/net/ethernet/sfc/falcon/ |
| H A D | enum.h | 14 * @LOOPBACK_GMAC: loopback within GMAC
16 * @LOOPBACK_XGXS: loopback within BPX after XGXS
17 * @LOOPBACK_XAUI: loopback within BPX before XAUI serdes
18 * @LOOPBACK_GMII: loopback within BPX after GMAC
19 * @LOOPBACK_SGMII: loopback within BPX within SGMII
20 * @LOOPBACK_XGBR: loopback within BPX within XGBR
21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
22 * @LOOPBACK_XAUI_FAR: loopback within BPX after XAUI serdes
23 * @LOOPBACK_GMII_FAR: loopback within BPX before SGMII
24 * @LOOPBACK_SGMII_FAR: loopback within BPX after SGMII
[all …]
|
| /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/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/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/ |
| 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
139 Within OpenBMC there are two areas of "vendor specific" repositories:
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
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | chassis.hpp | 37 * A chassis within the system.
62 * @param number Chassis number within the system. Chassis numbers start at
65 * @param devices Devices within this chassis, if any. The vector should
105 * Close the devices within this chassis, if any.
112 * Configure the devices within this chassis, if any.
133 * Returns the devices within this chassis, if any.
156 * Returns the chassis number within the system.
178 * Chassis number within the system.
191 * Devices within this chassis, if any.
|
| /openbmc/u-boot/arch/x86/include/asm/arch-quark/ |
| H A D | msg_port.h | 11 * the internal message network within the host bridge (D0:F0). Accesses
42 * @reg: register number within a port
50 * @reg: register number within a port
60 * @reg: register number within a port
69 * @reg: register number within a port
79 * @reg: register number within a port
88 * @reg: register number within a port
98 * @reg: register number within a port
|
| /openbmc/linux/drivers/clk/ingenic/ |
| H A D | cgu.h | 19 * @reg: the offset of the PLL's control register within the CGU
42 * @bypass_reg: the offset of the bypass control register within the CGU
72 * @reg: offset of the mux control register within the CGU
74 * the lowest bit of the mux value within its control register)
85 * @reg: offset of the divider control register within the CGU
87 * the lowest bit of the divide value within its control register)
92 * @ce_bit: the index of the change enable bit within reg, or -1 if there
94 * @busy_bit: the index of the busy bit within reg, or -1 if there isn't one
95 * @stop_bit: the index of the stop bit within reg, or -1 if there isn't one
122 * @reg: offset of the gate control register within the CGU
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | Endpoint.interface.yaml | 4 functionality within a physical device that communicates using the MCTP
13 network within a platform. The network IDs are used by the MCTP stack
22 a particular MCTP endpoint within a system for MCTP communication and
24 that comprise an MCTP communication network within a system. MCTP EIDs
25 are only unique within a particular MCTP network. That is, they can be
|
| /openbmc/u-boot/include/ |
| H A D | bitfield.h | 10 * width bitfields within a word. One use of this would be to use data tables
11 * to determine how to reprogram fields within R/W hardware registers.
47 /* Extract the value of a bitfield found within a given register value */
54 * Replace the value of a bitfield found within a given register value
71 /* Extract the value of a bitfield found within a given register value */
80 * Replace the value of a bitfield found within a given register value
|
| /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/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/linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_runtime_jit.c | 86 __description("runtime/jit: tail_call within bounds, prog once")
103 __description("runtime/jit: tail_call within bounds, prog loop")
120 __description("runtime/jit: tail_call within bounds, no prog")
137 __description("runtime/jit: tail_call within bounds, key 2")
154 __description("runtime/jit: tail_call within bounds, key 2 / key 2, first branch")
179 __description("runtime/jit: tail_call within bounds, key 2 / key 2, second branch")
204 __description("runtime/jit: tail_call within bounds, key 0 / key 2, first branch")
229 __description("runtime/jit: tail_call within bounds, key 0 / key 2, second branch")
254 __description("runtime/jit: tail_call within bounds, different maps, first branch")
281 __description("runtime/jit: tail_call within bounds, different maps, second branch")
|
| /openbmc/linux/tools/include/linux/ |
| H A D | list.h | 250 * @entry: an entry within head, could be the head itself
349 * @member: the name of the list_head within the struct.
358 * @member: the name of the list_head within the struct.
369 * @member: the name of the list_head within the struct.
380 * @member: the name of the list_head within the struct.
391 * @member: the name of the list_head within the struct.
401 * @member: the name of the list_head within the struct.
409 * @member: the name of the list_head within the struct.
455 * @member: the name of the list_head within the struct.
466 * @member: the name of the list_head within the struct.
[all …]
|
| /openbmc/linux/Documentation/sound/soc/ |
| 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/linux/net/ipv4/ |
| H A D | tcp_lp.c | 13 * within cong_avoid.
16 * o Handling calculation of One-Way-Delay (OWD) within rtt_sample, since
18 * o Handle reaction for Early Congestion Indication (ECI) within
19 * pkts_acked, as mentioned within pseudo code.
47 * @LP_WITHIN_THR: are we within threshold?
48 * @LP_WITHIN_INF: are we within inference?
286 /* test if within inference */ in tcp_lp_pkts_acked()
292 /* test if within threshold */ in tcp_lp_pkts_acked()
308 * and will usually within threshold when within inference */ in tcp_lp_pkts_acked()
313 /* happened within inference in tcp_lp_pkts_acked()
|
| /openbmc/linux/fs/jfs/ |
| H A D | jfs_dmap.c | 112 * table used for determining buddy sizes within characters of
115 * binary buddy of free bits within the character.
367 /* block to be freed better be within the mapsize. */ in dbFree()
463 /* the blocks better be within the mapsize. */ in dbUpdatePMap()
498 /* determine the bit number and word within the dmap of in dbUpdatePMap()
500 * are to be updated within this dmap. in dbUpdatePMap()
515 /* determine the bit number within the word and in dbUpdatePMap()
516 * the number of bits within the word. in dbUpdatePMap()
609 * Within the allocation groups, we maintain a preferred
639 /* determine the average number of free blocks within the ags. */ in dbNextAG()
[all …]
|
| /openbmc/bmcweb/ |
| H A D | OEM_SCHEMAS.md | 13 and can be maintained forever. Within OpenBMC, we have no such group of
43 compared to the experts within DMTF. Getting a DMTF opinion almost always leads
45 code we write within the industry.
86 The OpenBMC project maintains OEM schemas within the OpenBMC namespace, which,
94 To avoid versioning complications with clients, schemas within the OpenBMC
97 for schema branching within a namespace, therefore, if a system intends to ship
|
| /openbmc/linux/include/linux/ |
| H A D | rio_drv.h | 51 * Reads 32 bits of data from the specified offset within the local
66 * Writes 32 bits of data to the specified offset within the local
81 * Reads 16 bits of data from the specified offset within the local
96 * Writes 16 bits of data to the specified offset within the local
112 * Reads 8 bits of data from the specified offset within the local
127 * Writes 8 bits of data to the specified offset within the local
142 * Reads 32 bits of data from the specified offset within the
158 * Writes 32 bits of data to the specified offset within the
174 * Reads 16 bits of data from the specified offset within the
190 * Writes 16 bits of data to the specified offset within the
[all …]
|
| /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/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/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
|
| /openbmc/linux/scripts/mod/ |
| H A D | list.h | 15 * @member: the name of the member within the struct.
156 * @member: the name of the list_head within the struct.
165 * @member: the name of the list_head within the struct.
175 * @member: the name of the list_head within the struct.
184 * @member: the name of the list_head within the struct.
193 * @member: the name of the list_head within the struct.
205 * @member: the name of the list_head within the struct.
|