| /openbmc/u-boot/Documentation/devicetree/bindings/ram/ |
| H A D | fsl,mpc83xx-mem-controller.txt | 19 - p_impedance_override: DDR driver software p-impedance override; possible
26 - n_impedance_override: DDR driver software n-impedance override; possible
33 - odt_termination_value: ODT termination value for I/Os; possible values:
36 - ddr_type: Selects voltage level for DDR pads; possible
41 possible values:
44 - m_odr: Disable memory transaction reordering; possible
48 - clock_adjust: Clock adjust; possible values:
53 - ext_refresh_rec: Extended refresh recovery time; possible values:
55 - read_to_write: Read-to-write turnaround; possible values:
57 - write_to_read: Write-to-read turnaround; possible values:
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/core/tests/cases/ |
| H A D | depends.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
25 self.assertTrue(True, msg='How is this possible?')
29 self.assertTrue(True, msg='How is this possible?')
33 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
41 self.assertTrue(True, msg='How is this possible?')
|
| H A D | oetag.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
24 self.assertTrue(True, msg='How is this possible?')
30 self.assertTrue(True, msg='How is this possible?')
34 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
|
| /openbmc/pldm/pldmtool/oem/ibm/ |
| H A D | oem_ibm_state_set.hpp | 9 /** @brief PLDM OEM IBM Code Update possible state set values
21 /** @brief PLDM OEM IBM Verification possible state set values
31 /** @brief PLDM OEM IBM system power state possible state set values
38 /** @brief PLDM OEM IBM boot state possible state set values
60 /** @brief Map for PLDM OEM IBM firmware update possible state values
70 /** @brief Map for PLDM OEM IBM verification state possible state values
79 /** @brief Map for PLDM OEM IBM systerm power state possible state values
84 /** @brief Map for PLDM OEM IBM boot state possible state values
90 /** @brief Map for populating PLDM OEM IBM state sets with possible state values
|
| /openbmc/pldm/libpldmresponder/ |
| H A D | bios_enum_attribute.hpp | 75 /** @brief Get index of the given value in possible values
77 * @param[in] pVs - The possible values
78 * @return Index of the given value in possible values
83 /** @brief Get handles of possible values
85 * @param[in] pVs - The possible values
107 /** @brief Get index of the current value in possible values
108 * @return The index of the current value in possible values
112 /** @brief Get index of the property value in possible values
115 * @return The index of the property value in possible values
|
| /openbmc/linux/include/linux/ |
| H A D | rpmsg.h | 218 /* This shouldn't be possible */ in rpmsg_unregister_device()
227 /* This shouldn't be possible */ in __register_rpmsg_driver()
235 /* This shouldn't be possible */ in unregister_rpmsg_driver()
241 /* This shouldn't be possible */ in rpmsg_destroy_ept()
250 /* This shouldn't be possible */ in rpmsg_create_ept()
258 /* This shouldn't be possible */ in rpmsg_send()
267 /* This shouldn't be possible */ in rpmsg_sendto()
277 /* This shouldn't be possible */ in rpmsg_send_offchannel()
285 /* This shouldn't be possible */ in rpmsg_trysend()
294 /* This shouldn't be possible */ in rpmsg_trysendto()
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-flash.rst | 62 to the flash controller. Setting this control may not be possible in
97 this is a sensor, which makes it possible to synchronise the
106 control may not be possible in presence of some faults. See
123 if possible.
128 if possible. Setting this control may not be possible in presence of
134 possible.
143 and returns the chip to a usable state if possible.
174 which strobing the flash at full current will not be possible.The
187 after strobe during which another strobe will not be possible. This
|
| H A D | ext-ctrls-codec.rst | 96 of possible VBI formats depends on the driver. The currently defined
122 MPEG Audio sampling frequency. Possible values are:
146 streams. Possible values are:
173 MPEG-1/2 Layer I bitrate. Possible values are:
218 MPEG-1/2 Layer II bitrate. Possible values are:
263 MPEG-1/2 Layer III bitrate. Possible values are:
311 AC-3 bitrate. Possible values are:
366 MPEG Audio mode. Possible values are:
393 in stereo. Layer III is not (yet) supported. Possible values are:
418 Audio Emphasis. Possible values are:
[all …]
|
| H A D | vidioc-g-selection.rst | 73 choose a crop/compose rectangle as close as possible to the requested
89 capture/output window or TV display. The closest possible values of
99 3. Keep center of adjusted rectangle as close as possible to the
102 4. Keep width and height as close as possible to original ones.
104 5. Keep horizontal and vertical offset as close as possible to original
181 It is not possible to adjust struct :c:type:`v4l2_rect`
189 It is not possible to apply change of the selection rectangle at the
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-ccp | 18 Possible values:
29 Possible values:
40 Possible values:
51 Possible values:
63 Possible values:
74 Possible values:
85 Possible values:
|
| H A D | sysfs-class-net | 6 Indicates the name assignment type. Possible values are:
20 Indicates the address assignment type. Possible values are:
85 Possible values are:
129 Indicates whether the interface is in dormant state. Possible
144 Indicates whether the interface is under test. Possible
160 Indicates the interface latest or current duplex value. Possible
177 include/uapi/linux/if.h for a list of all possible values and
216 to determine the interface usability. Possible values:
251 Possible values are:
299 include/uapi/linux/if_arp.h for all possible values.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | stericsson,u8500-clks.yaml | 52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
67 second cell indicates which clock inside the PRCC block it wants, possible
80 which PRCC block the consumer wants to use, possible values are 1, 2, 3
82 it wants to control, possible values are 0 thru 31.
122 possible values are 0 (CLKOUT1) and 1 (CLKOUT2).
124 possible values are 0 thru 7, see the defines for the different
|
| /openbmc/linux/tools/memory-model/ |
| H A D | lock.cat | 83 let all-possible-rfe-lf =
85 * Given an LF event r, compute the possible rfe edges for that event
89 let possible-rfe-lf r =
93 in map possible-rfe-lf (LF \ range(rfi-lf))
96 with rfe-lf from cross(all-possible-rfe-lf)
109 let all-possible-rf-ru =
110 let possible-rf-ru r =
114 in map possible-rf-ru RU
117 with rf-ru from cross(all-possible-rf-ru)
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-01 | 13 # * What values are possible for CORE?
16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend-stat-properties.rst | 39 frontend, but it was not possible to collect it (could be a
61 Possible scales for this metric are:
80 Possible scales for this metric are:
111 Possible scales for this metric are:
139 Possible scales for this metric are:
168 Possible scales for this metric are:
196 Possible scales for this metric are:
217 Possible scales for this metric are:
239 Possible scales for this metric are:
|
| H A D | fe_property_parameters.rst | 79 Most of the digital TV standards offers more than one possible
121 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
125 Terrestrial Standard Possible values for bandwidth
293 Possible values: 0, 1, -1 (AUTO)
307 Possible values: 0, 1, -1 (AUTO)
344 Possible values: 0 .. 41, -1 (AUTO)
360 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1
377 Possible values: 1 .. 13
443 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``,
457 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK``
[all …]
|
| /openbmc/phosphor-settingsd/ |
| H A D | README-settings-manager.md | 9 - The above makes it possible to not even create settings objects that do not
12 - It should be possible, for example, for host0/ and host1/ on a system with two
16 - It should be possible to specify default settings for a system at build-time,
41 It is possible to specify this policy file via a bitbake recipe for a system
|
| /openbmc/linux/drivers/acpi/ |
| H A D | pci_link.c | 61 u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; member
82 * set context (link) possible list from resource list
112 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
138 link->irq.possible[i] = p->interrupts[i]; in acpi_pci_link_check_possible()
167 acpi_handle_debug(handle, "Found %d possible IRQs\n", in acpi_pci_link_get_possible()
411 * Note that PCI IRQ routers have a list of possible IRQs,
469 if (link->irq.possible[i] == irq) in acpi_irq_pci_sharing_penalty()
501 * reflect the possible and active irqs in the penalty table -- in acpi_irq_penalty_init()
510 if (link->irq.possible[i] < ACPI_MAX_ISA_IRQS) in acpi_irq_penalty_init()
512 possible[i]] += in acpi_irq_penalty_init()
[all …]
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | enum-bad-name.json | 2 # FIXME reports 'not\possible' instead of 'not\\possible'
3 { 'enum': 'MyEnum', 'data': [ 'not\\possible' ] }
|
| /openbmc/linux/Documentation/networking/ |
| H A D | mpls-sysctl.rst | 12 possible to configure forwarding for label values equal to or
16 is possible and expected as the platform labels are locally
26 Possible values: 0 - 1048575
46 Possible values: 1 - 255
|
| H A D | ipv6.rst | 27 The possible values and their effects are:
38 it will not be possible to open an IPv6 socket.
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /openbmc/linux/rust/alloc/ |
| H A D | README.md | 8 Please note that these files should be kept as close as possible to
24 upstream as possible and avoid as much divergence as possible, which
28 in-tree that would be as small and as close as possible to upstream.
|
| /openbmc/linux/include/linux/mtd/ |
| H A D | pfow.h | 38 /* command execution register, the only possible value is 0x01 */
48 /* They are possible values of PFOW command code register */
60 /* Defines possible value of PFOW command execution register */
63 /* Defines possible value of PFOW program/erase suspend register */
66 /* Possible values of PFOW device status register */
97 /* The superset of all possible error bits in DSR */
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | link_power_management_policy.rst | 8 There are 3 possible options:
14 least possible power when possible. This may
23 when possible, but do not enter the lowest power
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Accelerator.interface.yaml | 3 used to perform some functions more efficiently than is possible in software
4 running on a general-purpose CPU. Examples of possible hardware accelerators
17 Possible accelerator type
|