| /openbmc/linux/drivers/net/wireless/broadcom/b43/ |
| H A D | leds.c | 148 enum b43_led_behaviour behaviour, in b43_map_led() argument
156 switch (behaviour) { 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()
229 *behaviour = B43_LED_RADIO_A; in b43_led_get_sprominfo()
232 *behaviour = B43_LED_OFF; 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
125 switch (behaviour) { 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()
207 behaviour = B43legacy_LED_RADIO_A; in b43legacy_leds_init()
210 behaviour = B43legacy_LED_OFF; in b43legacy_leds_init()
[all …]
|
| /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/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/linux/arch/powerpc/platforms/pseries/ |
| H A D | setup.c | 562 if (result->behaviour & H_CPU_BEHAV_FLUSH_COUNT_CACHE) in init_cpu_char_feature_flags()
565 if (result->behaviour & H_CPU_BEHAV_FLUSH_LINK_STACK) in init_cpu_char_feature_flags()
574 if (!(result->behaviour & H_CPU_BEHAV_FAVOUR_SECURITY)) { in init_cpu_char_feature_flags()
577 } else if (result->behaviour & H_CPU_BEHAV_FAVOUR_SECURITY_H) in init_cpu_char_feature_flags()
582 if (!(result->behaviour & H_CPU_BEHAV_L1D_FLUSH_PR)) in init_cpu_char_feature_flags()
585 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY) in init_cpu_char_feature_flags()
588 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS) in init_cpu_char_feature_flags()
591 if (result->behaviour & H_CPU_BEHAV_NO_STF_BARRIER) in init_cpu_char_feature_flags()
594 if (!(result->behaviour & H_CPU_BEHAV_BNDS_CHK_SPEC_BAR)) in init_cpu_char_feature_flags()
|
| /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/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/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/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/qemu/hw/ppc/ |
| H A D | spapr_hcall.c | 1398 uint64_t behaviour = H_CPU_BEHAV_FAVOUR_SECURITY; in h_get_cpu_characteristics() local
1410 behaviour |= H_CPU_BEHAV_L1D_FLUSH_PR; in h_get_cpu_characteristics()
1413 behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY; in h_get_cpu_characteristics()
1414 behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS; in h_get_cpu_characteristics()
1418 behaviour |= H_CPU_BEHAV_L1D_FLUSH_PR; in h_get_cpu_characteristics()
1425 behaviour |= H_CPU_BEHAV_BNDS_CHK_SPEC_BAR; in h_get_cpu_characteristics()
1431 behaviour |= H_CPU_BEHAV_BNDS_CHK_SPEC_BAR; in h_get_cpu_characteristics()
1445 behaviour |= H_CPU_BEHAV_FLUSH_COUNT_CACHE; in h_get_cpu_characteristics()
1456 args[1] = behaviour; in h_get_cpu_characteristics()
|
| /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/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/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/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/dev-tools/ |
| H A D | ubsan.rst | 4 UBSAN is a runtime undefined behaviour checker.
20 UBSAN: Undefined behaviour in ../include/linux/bitops.h:110:33
|
| /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/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/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/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/Documentation/watchdog/ |
| H A D | watchdog-pm.rst | 12 handling to ensure a uniform behaviour for Linux systems.
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | mem_alignment.rst | 26 Please note that randomly changing the behaviour without good thought is
27 real bad - it changes the behaviour of all unaligned instructions in user
|
| /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/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-prctl_1.8.1.bb | 3 process' behaviour. Usage of the function is fairly messy though, due to \
|
| /openbmc/openbmc/poky/meta/recipes-extended/gperf/ |
| H A D | gperf_3.1.bb | 18 # it where to look explicitly (mirroring the behaviour of upstream's Makefile.devel).
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gimp/mypaint/libmypaint/ |
| H A D | 0001-make-build-compatible-w.-autoconf-2.7.patch | 6 Workaround for stricter behaviour (due to a bugfix) in 2.7,
|