| /openbmc/linux/security/selinux/ss/ |
| H A D | avtab.c | 80 if (key->specified & AVTAB_XPERMS) { in avtab_insert_node()
111 u16 specified = key->specified & ~(AVTAB_ENABLED|AVTAB_ENABLED_OLD); in avtab_insert() local
123 (specified & cur->key.specified)) { in avtab_insert()
125 if (specified & AVTAB_XPERMS) in avtab_insert()
157 u16 specified = key->specified & ~(AVTAB_ENABLED|AVTAB_ENABLED_OLD); in avtab_insert_nonunique() local
168 (specified & cur->key.specified)) in avtab_insert_nonunique()
191 u16 specified = key->specified & ~(AVTAB_ENABLED|AVTAB_ENABLED_OLD); in avtab_search_node() local
202 (specified & cur->key.specified)) in avtab_search_node()
219 avtab_search_node_next(struct avtab_node *node, u16 specified) in avtab_search_node_next() argument
226 specified &= ~(AVTAB_ENABLED|AVTAB_ENABLED_OLD); in avtab_search_node_next()
[all …]
|
| H A D | conditional.c | 107 avnode->key.specified &= ~AVTAB_ENABLED; in evaluate_cond_node()
109 avnode->key.specified |= AVTAB_ENABLED; in evaluate_cond_node()
116 avnode->key.specified &= ~AVTAB_ENABLED; in evaluate_cond_node()
118 avnode->key.specified |= AVTAB_ENABLED; in evaluate_cond_node()
274 if (k->specified & AVTAB_TYPE) { in cond_insertf()
290 if (avtab_search_node_next(node_ptr, k->specified)) { in cond_insertf()
566 node = avtab_search_node_next(node, key->specified)) { in cond_compute_xperms()
567 if (node->key.specified & AVTAB_ENABLED) in cond_compute_xperms()
583 node = avtab_search_node_next(node, key->specified)) { in cond_compute_av()
585 (node->key.specified & (AVTAB_ALLOWED|AVTAB_ENABLED))) in cond_compute_av()
[all …]
|
| H A D | avtab.h | 47 u16 specified; /* what field is specified */ member
59 u8 specified; /* ioctl, netfilter, ... */ member
120 struct avtab_node *avtab_search_node_next(struct avtab_node *node, u16 specified);
|
| /openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | max6697.txt | 21 Set to disable SMBus timeout. If not specified, SMBus timeout will be
25 Extended temperature will be disabled if not specified.
29 Beta compensation will be disabled if not specified.
33 If not specified, alert will be enabled for all channels.
38 If not specified, over-temperature reporting will be enabled for all
44 specified as boolean, otherwise as per bit mask specified.
46 If not specified, resistance cancellation will be disabled for all
53 specified.
|
| /openbmc/pldm/tools/fw-update/ |
| H A D | README.md | 29 - In case there are more than one images, they should be specified in the _same
35 Some fields corresponding to the PLDM firmware update package must be specified
50 - whether those fields need to be specified in the JSON, or are generated by the
58 - PackageHeaderIdentifier: Supported, must be specified in metadata file
59 - PackageHeaderFormatRevision: Supported, must be specified in metadata file
63 'T' for full ISO-8601 compliance). If not specified in the metadata file,
70 - PackageVersionString: Supported, must be specified in metadata file
83 - DeviceUpdateOptionFlags: Supported, must be specified in metadata file
89 - ApplicableComponents: Supported, must be specified in metadata file
92 - ComponentImageSetVersionString: Supported, must be specified in metadata
[all …]
|
| /openbmc/linux/drivers/gpu/drm/tests/ |
| H A D | drm_cmdline_parser_test.c | 21 KUNIT_EXPECT_FALSE(test, mode.specified); in drm_test_cmdline_force_e_only()
39 KUNIT_EXPECT_FALSE(test, mode.specified); in drm_test_cmdline_force_D_only_not_digital()
61 KUNIT_EXPECT_FALSE(test, mode.specified); in drm_test_cmdline_force_D_only_hdmi()
83 KUNIT_EXPECT_FALSE(test, mode.specified); in drm_test_cmdline_force_D_only_dvi()
101 KUNIT_EXPECT_FALSE(test, mode.specified); in drm_test_cmdline_force_d_only()
119 KUNIT_EXPECT_TRUE(test, mode.specified); in drm_test_cmdline_res()
141 KUNIT_EXPECT_TRUE(test, mode.specified); in drm_test_cmdline_res_vesa()
163 KUNIT_EXPECT_TRUE(test, mode.specified); in drm_test_cmdline_res_vesa_rblank()
185 KUNIT_EXPECT_TRUE(test, mode.specified); in drm_test_cmdline_res_rblank()
207 KUNIT_EXPECT_TRUE(test, mode.specified); in drm_test_cmdline_res_bpp()
[all …]
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | rio_cm.rst | 48 in a RapidIO network associated with the specified mport device.
52 with the specified mport device.
57 Binds the specified channel data structure to the specified
60 Enables listening for connection requests on the specified
63 Accepts a connection request from peer on the specified
64 channel. If wait timeout for this request is specified by a caller it is
71 Sends a data message through the specified channel.
72 The handler for this request assumes that message buffer specified by
78 handler will wait for new message until timeout specified by a caller
82 Closes a specified channel and frees associated buffers.
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-vmbus | 5 This file allows the driver for a device to be specified which
7 specified, only a driver with a name matching the value written
9 device. The override is specified by writing a string to the
15 automatically load the specified driver. If no driver with a
19 "none". Only a single driver may be specified in the override,
|
| H A D | sysfs-bus-amba | 5 This file allows the driver for a device to be specified which
7 When specified, only a driver with a name matching the value
9 the device. The override is specified by writing a string to the
15 automatically load the specified driver. If no driver with a
19 Only a single driver may be specified in the override, there is
|
| H A D | sysfs-bus-platform | 5 This file allows the driver for a device to be specified which
7 When specified, only a driver with a name matching the value
9 to the device. The override is specified by writing a string
15 any attempt to automatically load the specified driver. If no
19 name such as "none". Only a single driver may be specified in
|
| H A D | sysfs-bus-vdpa | 43 This file allows the driver for a device to be specified.
44 When specified, only a driver with a name matching the value
46 the device. The override is specified by writing a string to the
52 automatically load the specified driver. If no driver with a
56 Only a single driver may be specified in the override, there is
|
| H A D | sysfs-bus-css | 38 Description: This file allows the driver for a device to be specified. When
39 specified, only a driver with a name matching the value written
41 device. The override is specified by writing a string to the
47 automatically load the specified driver. If no driver with a
51 "none". Only a single driver may be specified in the override,
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/firmware/ |
| H A D | sdei.txt | 11 privilege level of the SDEI firmware (specified as part of the binding
12 below) and passing arguments in a manner specified by the "SMC Calling
22 text to handle the specified event number.
32 * "smc" : SMC #0, with the register assignments specified in this
34 * "hvc" : HVC #0, with the register assignments specified in this
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-buildid-cache.txt | 26 Add specified file to the cache.
32 Add specified kcore file to the cache. For the current host that is
45 Remove a cached binary which has same build-id of specified file
49 Purge all cached binaries including older caches which have specified
56 List missing build ids in the cache for the specified file.
59 Update specified file of the cache. Note that this doesn't remove
83 If the URLs is not specified, the value of DEBUGINFOD_URLS
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-mmap.rst | 32 When the ``MAP_FIXED`` flag is specified, ``start`` must be a
33 multiple of the pagesize and mmap will fail when the specified
55 the one specified. If the specified address cannot be used,
56 :c:func:`mmap()` will fail. If ``MAP_FIXED`` is specified,
81 ``offset`` in the memory of the device specified by ``fd`` into the
83 address is a hint only, and is usually specified as 0.
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | qcom,apq8084-pinctrl.txt | 83 Definition: List of gpio pins affected by the properties specified in
97 specified pins. Functions are only valid for gpio pins.
125 Definition: The specified pins should be configured as no pull.
130 Definition: The specified pins should be configured as pull down.
135 Definition: The specified pins should be configured as pull up.
140 Definition: The specified pins are configured in output mode, driven
147 Definition: The specified pins are configured in output mode, driven
154 Definition: Selects the drive strength for the specified pins, in mA.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-navigation/libspatialite/libspatialite/ |
| H A D | libspatialite_geos.patch | 16 - # GEOSCONFIG was not specified, so search within the current path
23 - # GEOSCONFIG was specified; display a message to the user
28 - AC_MSG_RESULT([Using user-specified geos-config file: $GEOSCONFIG])
30 - AC_MSG_ERROR([the user-specified geos-config file $GEOSCONFIG does not exi…
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| H A D | cc770.txt | 21 controller is half of that value. If not specified, a default
25 If not specified or if the specified value is 0, the CLKOUT pin
28 - bosch,slew-rate : slew rate of the CLKOUT signal. If not specified,
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | kdump.rst | 46 The crashkernel memory must be reserved at the user-specified region or
57 with the specified size.
60 the high memory area for an available region of the specified size. If
83 searching the low memory with the specified size in crashkernel=,high.
88 - If crashkernel=,low is not specified, the default low memory
91 - if crashkernel=0,low is specified, it means that the low memory
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | runqemu.README | 19 If <machine> isn't specified, the script will try to detect the machine name
22 If <filesystem> isn't specified, nfs booting will be assumed.
28 Full usage instructions can be seen by running the command with no options specified.
39 - The script extracts the root filesystem specified under pseudo and sets up a userspace
|
| H A D | combo-layer.conf.example | 36 # (master if not specified)
38 # file_filter: only include the specified file(s)
71 # init" at the specified revision(s). More than one can be specified
74 # The specified commits themselves do not get imported. Instead, an
|
| /openbmc/linux/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-prog.rst | 70 specified show information only about given programs,
99 **visual** is specified, *PROG* must match a single program.
101 If **file** is specified, the binary image will instead be
104 If **visual** is specified, control flow graph (CFG) will be
109 be displayed. If **linum** is specified, the filename, line
115 If *FILE* is specified image will be written to a file,
117 *PROG* must match a single program when **file** is specified.
122 be displayed. If **linum** is specified, the filename, line
137 **type** is optional, if not specified program type will be
141 of existing maps. It can be specified multiple times, each
[all …]
|
| /openbmc/linux/Documentation/leds/ |
| H A D | ledtrig-transient.rst | 72 - activate allows activating and deactivating the timer specified by
75 - state allows user to specify a transient state to be held for the specified
84 activate state indicates a timer with a value of specified
97 to LED_OFF and 1 maps to LED_FULL. The specified state is
106 changing the state to the specified state.
115 specified value as needed. When timer expires, state is restored to the
123 any, continues to run for the specified time.
126 continues to run for the specified time.
128 held for the specified duration.
130 held for the specified duration.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | func-mmap.rst | 30 When the ``MAP_FIXED`` flag is specified, ``start`` must be a
31 multiple of the pagesize and mmap will fail when the specified
70 the one specified. If the specified address cannot be used,
71 :c:func:`mmap()` will fail. If ``MAP_FIXED`` is specified,
102 ``offset`` in the memory of the device specified by ``fd`` into the
104 address is a hint only, and is usually specified as 0.
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | pmbus_write_vout_command.md | 33 specified using the "exponent" property. The exponent value can normally be
38 If you wish to verify that the specified volts value was successfully written to
56 … | Volts value to write, expressed as a decimal number. If not specified, the "volts" pro…
58 …onent value for linear data format. Can be positive or negative. If not specified, the exponent va…
59 …VOUT_COMMAND is verified by reading it from the device. If false or not specified, the updated val…
|