/openbmc/linux/arch/arm/common/ |
H A 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()
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tmate/ |
H A D | tmate_2.4.0.bb | 2 DESCRIPTION = "Tmate is a fork of tmux. It provides an instant pairing solution."
|
/openbmc/linux/Documentation/devicetree/bindings/soc/mediatek/ |
H A D | mediatek,pwrap.yaml | 58 - description: IP pairing registers 89 - description: IP pairing reset
|
/openbmc/linux/include/linux/mtd/ |
H A 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()
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A 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
|
H 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
|
/openbmc/linux/Documentation/devicetree/bindings/arm/bcm/ |
H A D | brcm,brcmstb.txt | 40 - brcm,write-pairing: 42 supports write-pairing. 59 brcm,write-pairing;
|
/openbmc/linux/drivers/mtd/ |
H A 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() 681 !master->pairing || master->_writev)) in add_mtd_device()
|
/openbmc/linux/Documentation/core-api/ |
H A D | gfp_mask-from-fs-io.rst | 50 Please note that the proper pairing of save/restore functions
|
/openbmc/qemu/docs/system/ |
H A D | virtio-net-failover.rst | 51 is only for pairing the devices within QEMU. The guest kernel module
|
/openbmc/qemu/docs/devel/ |
H A D | atomics.rst | 233 In this case, correctness is easy to check for using the "pairing" 294 Acquire/release pairing and the *synchronizes-with* relation 346 Synchronization between threads basically descends from this pairing of
|
/openbmc/linux/Documentation/firmware-guide/acpi/ |
H A D | acpi-lid.rst | 104 to the userspace by always pairing "closed" input events with complement
|
/openbmc/docs/designs/ |
H A D | multihost-physical-led.md | 29 Based on the current design in phosphor-led-sysfs application, pairing groups
|
/openbmc/linux/Documentation/admin-guide/LSM/ |
H A D | SafeSetID.rst | 74 without pairing them with other namespace types, which is not always an option.
|
/openbmc/linux/Documentation/fb/ |
H A D | udlfb.rst | 8 pairing that with a hardware framebuffer (16MB) on the other end of the
|
/openbmc/linux/Documentation/ |
H A 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.
|
/openbmc/linux/Documentation/bpf/ |
H A D | kfuncs.rst | 196 another helper). This flag is often used in pairing with KF_ACQUIRE flag, but
|
/openbmc/linux/Documentation/RCU/ |
H A D | checklist.rst | 257 of course a must. One example of non-obvious pairing is
|
/openbmc/linux/drivers/hid/ |
H A D | Kconfig | 598 Logitech receivers are capable of pairing multiple Logitech compliant
|