Searched refs:pairing (Results 1 – 14 of 14) sorted by relevance
| /Linux-v6.6/arch/arm/common/ |
| D | bL_switcher.c | 524 int pairing = bL_switcher_cpu_pairing[cpu]; in bL_switcher_get_logical_index() local
525 if (pairing == -1) in bL_switcher_get_logical_index()
528 (mpidr == cpu_logical_map(pairing))) in bL_switcher_get_logical_index()
757 int pairing; in bL_switcher_cpu_pre() local
762 pairing = bL_switcher_cpu_pairing[cpu]; in bL_switcher_cpu_pre()
764 if (pairing == -1) in bL_switcher_cpu_pre()
|
| /Linux-v6.6/include/linux/mtd/ |
| D | mtd.h | 298 const struct mtd_pairing_scheme *pairing; member
456 const struct mtd_pairing_scheme *pairing) in mtd_set_pairing_scheme() argument
458 mtd->pairing = pairing; in mtd_set_pairing_scheme()
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | glossary.txt | 69 Cycle: Memory-barrier pairing is restricted to a pair of CPUs, as the
71 that is required. In other cases, the notion of pairing must be
133 Pairing: "Memory-barrier pairing" reflects the fact that synchronizing
137 pairing also occurs with other types of operations, so that a
|
| D | recipes.txt | 341 The B/C pairing is an example of the MP pattern using smp_wmb() on the
378 This pairing of a control dependency in CPU0() with a full memory
381 The A/D pairing from the ring-buffer use case shown earlier also
|
| /Linux-v6.6/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 40 - brcm,write-pairing:
42 supports write-pairing.
59 brcm,write-pairing;
|
| /Linux-v6.6/drivers/mtd/ |
| D | mtdcore.c | 459 if (master->pairing && master->pairing->get_info) in mtd_wunit_to_pairing_info()
460 return master->pairing->get_info(master, wunit, info); in mtd_wunit_to_pairing_info()
504 if (master->pairing && master->pairing->get_wunit) in mtd_pairing_info_to_wunit()
505 return mtd->pairing->get_wunit(master, info); in mtd_pairing_info_to_wunit()
525 if (!master->pairing || !master->pairing->ngroups) in mtd_pairing_groups()
528 return master->pairing->ngroups; in mtd_pairing_groups()
680 !master->pairing || master->_writev)) in add_mtd_device()
|
| /Linux-v6.6/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 50 Please note that the proper pairing of save/restore functions
|
| /Linux-v6.6/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 104 to the userspace by always pairing "closed" input events with complement
|
| /Linux-v6.6/Documentation/fb/ |
| D | udlfb.rst | 8 pairing that with a hardware framebuffer (16MB) on the other end of the
|
| /Linux-v6.6/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 74 without pairing them with other namespace types, which is not always an option.
|
| /Linux-v6.6/Documentation/ |
| D | memory-barriers.txt | 57 - SMP barrier pairing.
395 address-dependency barriers; see the "SMP barrier pairing" subsection.
431 write barriers; see the "SMP barrier pairing" subsection.
452 see the "SMP barrier pairing" subsection.
936 always be paired. A lack of appropriate pairing is almost certainly an error.
|
| /Linux-v6.6/Documentation/bpf/ |
| D | kfuncs.rst | 196 another helper). This flag is often used in pairing with KF_ACQUIRE flag, but
|
| /Linux-v6.6/Documentation/RCU/ |
| D | checklist.rst | 257 of course a must. One example of non-obvious pairing is
|
| /Linux-v6.6/drivers/hid/ |
| D | Kconfig | 598 Logitech receivers are capable of pairing multiple Logitech compliant
|
