| /openbmc/linux/drivers/net/wireless/broadcom/b43/ |
| H A D | leds.c | 148 enum b43_led_behaviour behaviour, in b43_map_led() argument
154 /* Map the b43 specific LED behaviour value to the in b43_map_led()
156 switch (behaviour) { in b43_map_led()
194 b43warn(dev->wl, "LEDs: Unknown behaviour 0x%02X\n", in b43_map_led()
195 behaviour); in b43_map_led()
202 enum b43_led_behaviour *behaviour, in b43_led_get_sprominfo() argument
218 *behaviour = B43_LED_ACTIVITY; in b43_led_get_sprominfo()
221 *behaviour = B43_LED_RADIO_ALL; in b43_led_get_sprominfo()
224 *behaviour = B43_LED_RADIO_B; in b43_led_get_sprominfo()
226 *behaviour = B43_LED_ASSOC; in b43_led_get_sprominfo()
[all …]
|
| /openbmc/linux/drivers/net/wireless/broadcom/b43legacy/ |
| H A D | leds.c | 117 enum b43legacy_led_behaviour behaviour, in b43legacy_map_led() argument
123 /* Map the b43 specific LED behaviour value to the in b43legacy_map_led()
125 switch (behaviour) { in b43legacy_map_led()
170 b43legacywarn(dev->wl, "LEDs: Unknown behaviour 0x%02X\n", in b43legacy_map_led()
171 behaviour); in b43legacy_map_led()
181 enum b43legacy_led_behaviour behaviour; in b43legacy_leds_init() local
196 behaviour = B43legacy_LED_ACTIVITY; in b43legacy_leds_init()
199 behaviour = B43legacy_LED_RADIO_ALL; in b43legacy_leds_init()
202 behaviour = B43legacy_LED_RADIO_B; in b43legacy_leds_init()
204 behaviour = B43legacy_LED_ASSOC; in b43legacy_leds_init()
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | oxp-sensors.rst | 22 Some models have a toggle for changing the behaviour of the "Turbo/Silent"
42 "Turbo/Silent" button behaviour toggle is only supported on:
67 button behaviour function. Write "1" to activate the switch and "0" to
68 deactivate it. The specific keycodes and behaviour is specific to the device
|
| /openbmc/qemu/include/hw/ |
| H A D | ptimer.h | 38 * traditional ptimer behaviour from before policy flags were introduced.
40 * timer behaviour. For a new device using ptimers, you should not
41 * use PTIMER_POLICY_LEGACY, but instead check the actual behaviour
45 * and are in a position to check or test the real hardware behaviour,
104 * @policy: PTIMER_POLICY_* bits specifying behaviour
167 * Note that if your counter behaviour is specified as having a
204 * need to call one of them. If the counter behaviour is specified
236 * be used to emulate the behaviour of timers which immediately
|
| /openbmc/linux/arch/arm64/kvm/ |
| H A D | emulate-nested.c | 26 const enum trap_behaviour behaviour; member
118 .behaviour = BEHAVE_FORWARD_READ,
124 .behaviour = BEHAVE_FORWARD_ANY,
130 .behaviour = BEHAVE_FORWARD_READ,
136 .behaviour = BEHAVE_FORWARD_WRITE,
142 .behaviour = BEHAVE_FORWARD_WRITE,
148 .behaviour = BEHAVE_FORWARD_ANY,
154 .behaviour = BEHAVE_FORWARD_ANY,
160 .behaviour = BEHAVE_FORWARD_ANY,
166 .behaviour = BEHAVE_FORWARD_ANY,
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-kernel.md | 155 ### Syscall behaviour
189 [Tag behaviour for transmitted messages](#tag-behaviour-for-transmitted-messages)
224 transmission. Like other `SOCK_DGRAM` behaviour, this does not generate any MCTP
246 [Tag behaviour for transmitted messages](#tag-behaviour-for-transmitted-messages)
315 allocation is lost. This tag behaviour can be controlled through the
400 ##### `MCTP_TAG_CONTROL`: manage outgoing tag allocation behaviour
409 This allows an application to control the behaviour of allocated tags for
429 Changing the default tag control behaviour should only be required when:
615 /* Set up poll behaviour, and record our starting time for
693 #### Tag behaviour for transmitted messages
[all …]
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | nommu-mmap.rst | 12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
31 the no-MMU case doesn't support these, behaviour is identical to
272 Adjusting page trimming behaviour
277 fragmentation, and as such, is left configurable. The default behaviour is to
280 behaviour can either be disabled completely, or bumped up to a higher page
283 Page trimming behaviour is configurable via the sysctl ``vm.nr_trim_pages``.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | xfs.rst | 30 The default behaviour is for dynamic end-of-file
35 the dynamic behaviour.
45 The default behaviour is determined by the on-disk feature
46 bit indicating that ``attr2`` behaviour is active. If either
112 (in bytes) will be returned instead. Otherwise the behaviour
398 different error handlers for which behaviour can be configured.
447 If set to 0, the configured retry behaviour will continue until all
461 propagation behaviour for specific errors. There is also a "default" error
462 handler defined, which defines the behaviour for all errors that don't have
498 **Note:** The default behaviour for a specific error handler is dependent on both
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
| H A D | 0009-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch | 17 with (flag == 0) and (flag == AT_SYMLINK_NOFOLLOW) is the behaviour
23 just historical and not actually necessary or desired behaviour?
53 + behaviour for broken symlinks; laccess() on a broken symlink will succeed
58 + and not actually necessary or desired behaviour?
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/sdbus-c++/sdbus-c++-libsystemd/ |
| H A D | 0007-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch | 17 with (flag == 0) and (flag == AT_SYMLINK_NOFOLLOW) is the behaviour
23 just historical and not actually necessary or desired behaviour?
53 + behaviour for broken symlinks; laccess() on a broken symlink will succeed
58 + and not actually necessary or desired behaviour?
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | tagged-address-abi.rst | 54 NOTE: This behaviour changed in v5.6 and so some earlier kernels may
64 NOTE: This behaviour changed in v5.14 and so some earlier kernels may
101 - The syscall behaviour is undefined for invalid tagged pointers: it may
105 - The syscall behaviour for a valid tagged pointer is the same as for
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | tracepoints.rst | 47 convenient parameters or change their behaviour.
93 it. Else, zero. But this behaviour depends on implementations in driver
99 it. Else, zero. But this behaviour depends on implementations in driver
105 also calculated according to it. Else, zero. But this behaviour depends
|
| /openbmc/qemu/include/hw/ssi/ |
| H A D | ssi.h | 39 /* if you have standard or no CS behaviour, just override transfer.
51 /* if you have non-standard CS behaviour override this to take control
52 * of the CS behaviour at the device level. transfer, set_cs, and
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | cpu-cooling-api.rst | 78 - In running time the 'execution' behaviour (instruction types, memory
87 f(run) here represents the described execution behaviour and its
91 The detailed behaviour for f(run) could be modelled on-line. However,
|
| /openbmc/libpldm/include/libpldm/ |
| H A D | transport.h | 49 * behaviour is undefined.
91 * to use the transport instance asynchronously, as this discard behaviour will affect other
106 * behaviour is undefined.
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | fail_on_no_media.patch | 9 The current behaviour of busybox is to try all fstype when automounting
11 media exists, so change the behaviour of busybox to do the same.
|
| /openbmc/qemu/include/qemu/ |
| H A D | fifo32.h | 84 * Push a 32 bits data word to the FIFO. Behaviour is undefined if the FIFO
105 * Push a 32 bit word array to the FIFO. Behaviour is undefined if the FIFO
124 * Pop a 32 bits data word from the FIFO. Behaviour is undefined if the FIFO
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libstrictures/ |
| H A D | libstrictures-perl_2.000006.bb | 12 and then unknown (and probably undesired) subsequent behaviour. \
21 causes undesired behaviour this can be overridden by setting the \
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | ABI.rst | 15 then default to the previous behaviour if it is missing. If a binding
32 behaviour when a newly added property is missing.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | deterministic_imports.patch | 7 means behaviour seen on one system might not reproduce on another and is a real headache.
12 As a result, patch this to a behaviour which works for us.
|
| /openbmc/linux/drivers/mfd/ |
| H A D | si476x-cmd.c | 488 * #SI476X_DCLK_NOOP - do not modify the behaviour
494 * #SI476X_DFS_NOOP - do not modify the behaviour
500 * SI476X_DOUT_NOOP - do not modify the behaviour
508 * SI476X_XOUT_NOOP - do not modify the behaviour
545 * SI476X_IQCLK_NOOP - do not modify the behaviour
551 * SI476X_IQFS_NOOP - do not modify the behaviour
557 * SI476X_IOUT_NOOP - do not modify the behaviour
562 * SI476X_QOUT_NOOP - do not modify the behaviour
595 * SI476X_ICIN_NOOP - do not modify the behaviour
602 * SI476X_ICIP_NOOP - do not modify the behaviour
[all …]
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-flakey.rst | 6 unreliable behaviour periodically. It's been found useful in simulating
10 <up interval> seconds, then exhibits unreliable behaviour for <down
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | eventpoll.h | 65 /* Set the One Shot behaviour for the target file descriptor */
68 /* Set the Edge Triggered behaviour for the target file descriptor */
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | setuptools3_legacy.bbclass | 7 # This class is for packages which use the deprecated setuptools behaviour,
9 # This behaviour is deprecated in setuptools[1] and won't work in the future, so
|
| /openbmc/linux/Documentation/usb/ |
| H A D | functionfs.rst | 6 unique behaviour. It may be added to an USB configuration only after
59 parameter's value is just a one-element list, then the behaviour
|