Searched refs:pairing (Results 1 – 14 of 14) sorted by relevance
| /linux/arch/arm/common/ |
| H A D | bL_switcher.c | 522 int pairing = bL_switcher_cpu_pairing[cpu]; in bL_switcher_get_logical_index() local 523 if (pairing == -1) in bL_switcher_get_logical_index() 526 (mpidr == cpu_logical_map(pairing))) in bL_switcher_get_logical_index() 755 int pairing; in bL_switcher_cpu_pre() local 760 pairing = bL_switcher_cpu_pairing[cpu]; in bL_switcher_cpu_pre() 762 if (pairing == -1) in bL_switcher_cpu_pre()
|
| /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()
|
| /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 | 345 The B/C pairing is an example of the MP pattern using smp_wmb() on the 382 This pairing of a control dependency in CPU0() with a full memory 385 The A/D pairing from the ring-buffer use case shown earlier also
|
| /linux/Documentation/devicetree/bindings/arm/bcm/ |
| H A D | brcm,brcmstb.txt | 40 - brcm,write-pairing: 42 supports write-pairing. 59 brcm,write-pairing;
|
| /linux/drivers/mtd/ |
| H A D | mtdcore.c | 510 if (master->pairing && master->pairing->get_info) in mtd_wunit_to_pairing_info() 511 return master->pairing->get_info(master, wunit, info); in mtd_wunit_to_pairing_info() 555 if (master->pairing && master->pairing->get_wunit) in mtd_pairing_info_to_wunit() 556 return mtd->pairing->get_wunit(master, info); in mtd_pairing_info_to_wunit() 576 if (!master->pairing || !master->pairing->ngroups) in mtd_pairing_groups() 579 return master->pairing->ngroups; in mtd_pairing_groups() 732 !master->pairing || master->_writev)) in add_mtd_device()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-pci-host-bridge | 28 device in the Selective IDE Stream pairing. Specifically, "R"
|
| /linux/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 50 Please note that the proper pairing of save/restore functions
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 104 to the userspace by always pairing "closed" input events with complement
|
| /linux/Documentation/fb/ |
| H A D | udlfb.rst | 8 pairing that with a hardware framebuffer (16MB) on the other end of the
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | SafeSetID.rst | 74 without pairing them with other namespace types, which is not always an option.
|
| /linux/Documentation/iio/ |
| H A D | ad4695.rst | 108 ``REFGND``. (Offset is always 0 when pairing with ``REFGND``.)
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 57 - SMP barrier pairing. 394 address-dependency barriers; see the "SMP barrier pairing" subsection. 435 write barriers; see the "SMP barrier pairing" subsection. 456 see the "SMP barrier pairing" subsection. 943 always be paired. A lack of appropriate pairing is almost certainly an error.
|
| /linux/Documentation/RCU/ |
| H A D | checklist.rst | 270 of course a must. One example of non-obvious pairing is
|