| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe_property_parameters.rst | 164 The acceptable values are defined by :c:type:`fe_spectral_inversion`.
192 The acceptable values are defined by :c:type:`fe_code_rate`.
207 The acceptable values are defined by :c:type:`fe_sec_voltage`.
227 The acceptable values are defined by :c:type:`fe_pilot`.
239 The acceptable values are defined by :c:type:`fe_rolloff`.
273 The acceptable values are defined by :c:type:`fe_delivery_system`.
721 The acceptable values are defined by :c:type:`atscmh_rs_frame_mode`.
733 The acceptable values are defined by :c:type:`atscmh_rs_frame_ensemble`.
745 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
757 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
[all …]
|
| /openbmc/linux/fs/exportfs/ |
| H A D | expfs.c | 40 * Check if the dentry or any of it's aliases is acceptable.
44 int (*acceptable)(void *context, struct dentry *dentry), in find_acceptable_alias()
50 if (acceptable(context, result)) in find_acceptable_alias()
60 if (dentry != result && acceptable(context, dentry)) { in find_acceptable_alias()
448 int (*acceptable)(void *, struct dentry *), in exportfs_decode_fh_raw()
471 if (!acceptable) in exportfs_decode_fh_raw()
489 if (!acceptable(context, result)) { in exportfs_decode_fh_raw()
503 * or any alias for it is acceptable. This is always true in exportfs_decode_fh_raw()
510 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh_raw()
576 * And finally make sure the dentry is actually acceptable in exportfs_decode_fh_raw()
[all …]
|
| /openbmc/linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A D | AddingTestCases.txt | 51 more acceptable exit codes for this command.
65 of 0 is acceptable.
72 more acceptable exit codes for this command.
89 It's possible to include acceptable exit codes with the setup/teardown command
92 acceptable exit codes for the command.
|
| /openbmc/linux/drivers/media/i2c/ |
| H A D | aptina-pll.c | 71 * We're looking for the highest acceptable P1 value for which a in aptina_pll_calculate()
85 * The first naive approach is to iterate over all p1 values acceptable in aptina_pll_calculate()
86 * according to (1) and all mf values acceptable according to (2), and in aptina_pll_calculate()
91 * we can compute the mf increment between two acceptable values in aptina_pll_calculate()
100 * acceptable p1 and mf values by modifying the minimum and maximum in aptina_pll_calculate()
119 * range is not empty, any value in the mf range is acceptable. We thus in aptina_pll_calculate()
|
| /openbmc/openbmc-tools/tof-voters/libvoters/subcmd/ |
| H A D | analyze-commits.py | 10 import libvoters.acceptable as acceptable namespace
75 if not acceptable.project(project):
86 if not acceptable.file(project, file_data["file"]):
|
| H A D | analyze-reviews.py | 10 import libvoters.acceptable as acceptable namespace
57 if not acceptable.project(project):
78 if not acceptable.file(project, comment["file"]):
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | dc395x.rst | 29 Default: 0, Acceptable values: 0 or 1
37 Default: 7, Acceptable values: 0 to 15
42 Default: 1, Acceptable value: 0 to 7
88 Default: 3, Acceptable values: 0-5
93 Default: 1, Acceptable values: 0-180
|
| /openbmc/phosphor-pid-control/pid/ |
| H A D | thermalcontroller.cpp | 106 bool acceptable = false; in inputProc() local
158 acceptable = true; in inputProc()
161 if (!acceptable) in inputProc()
163 // If none of the inputs were acceptable, use the setpoint as in inputProc()
166 // behavior until the inputs become acceptable. in inputProc()
|
| /openbmc/linux/include/linux/iio/common/ |
| H A D | inv_sensors_timestamp.h | 12 * @jitter: acceptable jitter in per-mille
46 * @min_period: minimal acceptable clock period
47 * @max_period: maximal acceptable clock period
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_cdclk.h | 39 /* minimum acceptable cdclk to satisfy bandwidth requirements */
41 /* minimum acceptable cdclk for each pipe */
43 /* minimum acceptable voltage level for each pipe */
|
| /openbmc/u-boot/drivers/ram/ |
| H A D | Kconfig | 16 If this is acceptable and you have a need to use RAM drivers in
25 If this is acceptable and you have a need to use RAM drivers in
|
| /openbmc/u-boot/drivers/clk/ |
| H A D | Kconfig | 18 If this is acceptable and you have a need to use clock drivers in
28 If this is acceptable and you have a need to use clock drivers in
|
| /openbmc/linux/fs/btrfs/ |
| H A D | block-rsv.h | 106 * value is acceptable, instead of accessing it directly and trigger data race
122 * acceptable, instead of accessing it directly and trigger data race warning
|
| /openbmc/pam-ipmi/src/pam_ipmicheck/ |
| H A D | pam_ipmicheck.c | 103 // verify the new password is acceptable. in pam_sm_chauthtok()
110 "(%zu) is not acceptable for IPMI", in pam_sm_chauthtok()
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | cmd.tcl | 43 …# acceptable_shell_rcs A list of acceptable shell rcs. If the shell return code is fou…
68 # Check whether return code is acceptable.
|
| H A D | redfish_plus.py | 27 …valid_status_codes A list of status codes that the caller considers acceptable. If t…
28 … a null list, then any status code is considered acceptable. Note that
91 are acceptable. The default value is [200]. See the
|
| /openbmc/linux/Documentation/networking/ |
| H A D | dccp.rst | 118 range 0..15 are acceptable. The default setting is 0 (full coverage),
122 sets a threshold, where again values 0..15 are acceptable. The default
125 coverage value are also acceptable. The higher the number, the more
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/ |
| H A D | README.md | 193 CertificateCollection with the certificate file. Acceptable body formats are:
194 raw pem text or json that is acceptable by action
254 allowed. In case of authority certificate type the delete option is acceptable
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-waitress_3.0.2.bb | 3 server with very acceptable performance."
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | license.py | 343 aren't acceptable.
346 of acceptable license flags, or all of the LICENSE_FLAGS if there
347 is no list of acceptable flags.
349 If everything is is acceptable, it returns None.
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | serial_zynq.c | 62 * Find acceptable values for baud generation. in _uart_zynq_serial_setbrg()
73 * an acceptable (<3%) error in _uart_zynq_serial_setbrg()
|
| /openbmc/openbmc/meta-openembedded/meta-networking/ |
| H A D | MAINTAINERS | 22 One pattern per line. Multiple F: lines acceptable.
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | jobs-to-kas | 5 # brackets. For example, the following are acceptable:
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc_message_registry.readmefirst.md | 14 acceptable)
|
| /openbmc/openbmc/poky/meta/recipes-core/glibc/glibc/ |
| H A D | 0022-Avoid-hardcoded-build-time-paths-in-the-output-binar.patch | 8 Upstream-Status: Inappropriate [would need reworking somehow to be acceptable upstream]
|