Searched full:behaviors (Results 1 – 25 of 83) sorted by relevance
1234
| /linux-6.8/Documentation/devicetree/bindings/devfreq/event/ |
| D | samsung,exynos-ppmu.yaml | 16 PPMU events provide information of the SoC's behaviors so that you may use to
17 analyze system performance, to make behaviors visible and to count usages of
|
| /linux-6.8/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 124 '0' means the device link can affect other device behaviors
130 up and doesn't not affect other behaviors of the devices.
|
| /linux-6.8/arch/m68k/include/asm/ |
| D | switch_to.h | 15 * and so we might get see unexpected behaviors when a task returns
|
| /linux-6.8/tools/perf/Documentation/ |
| D | Build.txt | 67 supported by GCC. UBSan detects undefined behaviors of programs at runtime.
|
| D | perf-kvm.txt | 31 perf.data.host, please input --host --no-guest. The behaviors are shown as
|
| /linux-6.8/Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,padding.yaml | 19 register must be cleared to 0, or undefined behaviors could happen.
|
| /linux-6.8/Documentation/process/ |
| D | code-of-conduct.rst | 51 contributor for other behaviors that they deem inappropriate, threatening,
|
| /linux-6.8/tools/testing/selftests/net/ |
| D | srv6_end_flavors_test.sh | 11 # or extend the existing SRv6 End, End.X and End.T behaviors. For the sake of
17 # The End, End.X, and End.T behaviors can support these flavors either
37 # SR node, it will be active only on such behaviors bound to a penultimate SID
502 # (i.e. behaviors) that each of them needs to perform. Every <nodeid:op>
|
| D | srv6_hl2encap_red_l2vpn_test.sh | 382 # Endpoint behaviors instaces are grouped together in the 'localsid'
393 # $3 - SRv6 routers configured for steering traffic (End behaviors)
634 # - rt-4,rt-3 (SRv6 End behaviors)
|
| D | srv6_hencap_red_l3vpn_test.sh | 455 # $3 - SRv6 routers configured for steering traffic (End behaviors)
613 # - rt-3,rt-4 (SRv6 End behaviors)
629 # - rt-4,rt-3 (SRv6 End behaviors)
|
| D | unicast_extensions.sh | 29 # of these behaviors for testing kernel patches that change them.
|
| /linux-6.8/drivers/gpu/drm/mediatek/ |
| D | mtk_padding.c | 65 * undefined behaviors could happen in mtk_padding_start()
|
| /linux-6.8/Documentation/block/ |
| D | pr.rst | 18 These behaviors are optional in SPC but will be automatically applied
|
| /linux-6.8/tools/lib/bpf/ |
| D | libbpf_legacy.h | 36 * Disable any libbpf 1.0 behaviors. This is the default before libbpf
|
| /linux-6.8/Documentation/bpf/ |
| D | map_cgroup_storage.rst | 19 ``BPF_MAP_TYPE_CGROUP_STORAGE`` map type. Some of its behaviors was changed in
|
| /linux-6.8/include/uapi/linux/ |
| D | i2c.h | 69 * passing certain @flags may have changed those standard protocol behaviors.
|
| /linux-6.8/Documentation/locking/ |
| D | locktorture.rst | 19 different critical region behaviors. The amount of contention on the lock
|
| /linux-6.8/drivers/gpu/drm/amd/display/dc/link/protocols/ |
| D | link_hpd.c | 31 * feature or signal specific HPD behaviors.
|
| /linux-6.8/drivers/acpi/ |
| D | button.c | 250 * trigger unexpected behaviors. in acpi_lid_notify_state()
253 * "close" will trigger unexpected behaviors. in acpi_lid_notify_state()
|
| /linux-6.8/drivers/misc/cxl/ |
| D | hcalls.c | 203 * certain coherent platform function behaviors.
476 * certain coherent platform facility behaviors.
|
| /linux-6.8/Documentation/hid/ |
| D | uhid.rst | 130 describes special behaviors of a device. The following flags are defined:
|
| /linux-6.8/Documentation/driver-api/usb/ |
| D | error-codes.rst | 13 behave the same except for transfer speed dependent behaviors and the
|
| D | URB.rst | 127 - For ISO there are two startup behaviors: Specified start_frame or ASAP.
|
| /linux-6.8/Documentation/filesystems/ |
| D | 9p.rst | 191 from a local filesystem behaviors.
|
| /linux-6.8/lib/ |
| D | stackinit_kunit.c | 432 /* Padding initialization depends on compiler behaviors. */
|
1234