Searched full:shared (Results 1 – 25 of 411) sorted by relevance
12345678910>>...17
| /Documentation/devicetree/bindings/mfd/ |
| D | axp20x.txt | 90 LDO2 : LDO : ldo24in-supply : shared supply
92 LDO4 : LDO : ldo24in-supply : shared supply
106 ALDO1 : LDO : aldoin-supply : shared supply
107 ALDO2 : LDO : aldoin-supply : shared supply
108 ALDO3 : LDO : aldoin-supply : shared supply
109 DLDO1 : LDO : dldoin-supply : shared supply
110 DLDO2 : LDO : dldoin-supply : shared supply
111 DLDO3 : LDO : dldoin-supply : shared supply
112 DLDO4 : LDO : dldoin-supply : shared supply
113 ELDO1 : LDO : eldoin-supply : shared supply
[all …]
|
| /Documentation/filesystems/ |
| D | sharedsubtree.txt | 1 Shared Subtrees
21 that got mounted recently. Shared subtree semantics provide the necessary
30 Shared subtree provides four different flavors of mounts; struct vfsmount to be
33 a. shared mount
39 2a) A shared mount can be replicated to as many mountpoints and all the
44 Let's say /mnt has a mount that is shared.
45 mount --make-shared /mnt
47 Note: mount(8) command now supports the --make-shared flag,
76 2b) A slave mount is like a shared mount except that mount and umount events
79 All slave mounts have a master mount which is a shared.
[all …]
|
| D | tmpfs.txt | 20 pages will be shown as "Shmem" in /proc/meminfo and "Shared" in
21 free(1). Notice that these counters also include shared memory
28 all. This is used for shared anonymous mappings and SYSV shared
36 POSIX shared memory (shm_open, shm_unlink). Adding the following
44 This mount is _not_ needed for SYSV shared memory. The internal
47 shared memory)
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | xen,shared-memory.txt | 5 to be a shared memory area across multiple virtual machines for
8 For each of these pre-shared memory regions, a range is exposed under
13 compatible = "xen,shared-memory-v1"
16 the base guest physical address and size of the shared memory region
19 64 bit integer offset within the owner virtual machine's shared
23 a string that identifies the shared memory region as specified in
|
| D | qcom,cmd-db.txt | 6 is stored in a shared memory region and is loaded by the remote processor.
9 controlling shared resources. Depending on the board configuration the shared
11 remote processor and made available in the shared memory.
|
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 102 * VMA policies are shared between all tasks that share a
124 Shared Policy
125 Conceptually, shared policies apply to "memory objects" mapped
126 shared into one or more tasks' distinct address spaces. An
127 application installs shared policies the same way as VMA
129 virtual addresses that map the shared object. However, unlike
131 range of a task's address space, shared policies apply
132 directly to the shared object. Thus, all tasks that attach to
134 shared object, by any task, will obey the shared policy.
136 As of 2.6.22, only shared memory segments, created by shmget() or
[all …]
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 37 outside the confinement of all-or-nothing shared resources of legacy
44 shared at the time of their creation. unshare() was conceptualized by
48 shared resources without creating a new process. unshare() is a natural
57 resources is not possible. Since namespaces are shared by default
60 from default shared namespace. The following lists two use-cases
74 of shared-tree feature in the Linux kernel, even regular Linux systems
85 decide what needs to be shared at the time of creating the process
111 be shared, similar flags in unshare(int flags) should specify
135 context that are currently being shared with other processes. Part
136 of execution context, such as the namespace, is shared by default
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | nvidia,tegra186-hsp.txt | 9 The features that HSP supported are shared mailboxes, shared semaphores,
41 For shared mailboxes, the second cell is composed of two fields:
43 A bit mask of flags that further specify how the shared mailbox will be
51 The index of the shared mailbox to use. The number of available mailboxes
|
| D | mailbox.txt | 26 - shmem : List of phandle pointing to the shared memory(SHM) area between the
27 users of these mailboxes for IPC, one for each mailbox. This shared
39 Example with shared memory(shmem):
|
| D | qcom,apcs-kpss-global.txt | 15 "qcom,sc7180-apss-shared"
16 "qcom,sdm845-apss-shared"
17 "qcom,sm8150-apss-shared"
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm-dsu-pmu.txt | 1 * ARM DynamIQ Shared Unit (DSU) Performance Monitor Unit (PMU)
3 ARM DyanmIQ Shared Unit (DSU) integrates one or more CPU cores
4 with a shared L3 memory system, control logic and external interfaces to
|
| /Documentation/devicetree/bindings/sound/ |
| D | wm8960.txt | 12 - wlf,shared-lrclk: This is a boolean property. If present, the LRCM bit of
18 DACLRC pin. If shared-lrclk is present, no need to enable DAC for captrue.
30 wlf,shared-lrclk;
|
| /Documentation/ |
| D | nommu-mmap.txt | 30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
67 that a copy is always taken and never shared.
73 mapping; shared across fork.
84 case, a shared-writable memory mapping will be possible. It will work
163 Interprocess shared memory
166 Both SYSV IPC SHM shared memory and POSIX shared memory is supported in NOMMU
191 Shared mappings may not be moved. Shareable mappings may not be moved either,
192 even if they are not currently shared.
221 is removed. An existing mapping will be shared, partially or not, if possible
240 In such a case, care must be taken lest userspace see a shared or a
[all …]
|
| D | tee.txt | 16 - Managing shared memory between Linux and the TEE
28 - TEE_IOC_SHM_ALLOC allocates shared memory and returns a file descriptor
30 descriptor any more, it should be closed. When shared memory isn't needed
80 range to used for shared memory between Linux and OP-TEE.
113 shared memory buffer representation.
|
| /Documentation/devicetree/bindings/net/ |
| D | cavium-mix.txt | 11 AGL registers. The third bank are the AGL registers shared by all
12 MIX devices present. The fourth bank is the AGL_PRT_CTL shared by
15 - cell-index: A single cell specifying which portion of the shared
|
| D | ti-bluetooth.txt | 9 * TI WiLink 7/8 (wl12xx/wl18xx) Shared Transport BT/FM/GPS devices
12 and GPS over what's called "shared transport". The shared transport is
|
| /Documentation/devicetree/bindings/dma/ |
| D | brcm,bcm2835-dma.txt | 17 Use "dma-shared-all" for the common interrupt line
18 that is shared by all dma channels.
46 /* unused shared irq for all channels */
63 "dma-shared-all";
|
| D | fsl-imx-sdma.txt | 30 1 Shared SSI
34 5 Shared UART
37 8 Shared CSPI
43 14 Shared Memory Stick Host Controller
52 23 Shared ASRC
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smem.txt | 1 Qualcomm Shared Memory Manager binding
3 This binding describes the Qualcomm Shared Memory Manager, used to share data
26 the shared memory
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | st,spear3xx-shirq.txt | 1 * SPEAr Shared IRQ layer (shirq)
3 SPEAr3xx architecture includes shared/multiplexed irqs for certain set
13 A single node in the device tree is used to describe the shared
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | index.rst | 8 DRBD is a shared-nothing, synchronously replicated block device. It
10 clusters and in this context, is a "drop-in" replacement for shared
|
| /Documentation/devicetree/bindings/thermal/ |
| D | exynos-thermal.txt | 17 instances of TMU and some registers are shared across all TMU's like
20 registers shared with the TMU instance.
34 -- 2. optional clock to access the shared registers of TMU channel
38 -- "tmu_triminfo_apbif" clock to access the shared triminfo register
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-xhci_hcd | 18 functionality and the shared root port will be assigned
20 will disable the DbC functionality and the shared root
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-sprd.txt | 5 interrupt is shared for all of the banks handled by the controller.
17 - interrupts: Should be the port interrupt shared by all the gpios.
|
| /Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 82 Reservation Map Location (Private or Shared)
85 A huge page mapping or segment is either private or shared. If private,
86 it is typically only available to a single address space (task). If shared,
94 - For shared mappings, the reservation map hangs off the inode. Specifically,
95 inode->i_mapping->private_data. Since shared mappings are always backed
103 Reservations are created when a huge page backed shared memory segment is
123 One of the big differences between PRIVATE and SHARED mappings is the way
126 - For shared mappings, an entry in the reservation map indicates a reservation
141 always the value (to - from). However, for shared mappings it is possible that
168 modified to reflect the reservations. In the case of a shared mapping, a
[all …]
|
12345678910>>...17