Home
last modified time | relevance | path

Searched refs:VA (Results 1 – 25 of 54) sorted by relevance

123

/linux-6.1.9/Documentation/devicetree/bindings/sound/
Dcs42l56.txt9 - VA-supply, VCP-supply, VLDO-supply : power supplies for the device,
31 0 = 0.5 x VA
32 1 = 0.6 x VA
33 2 = 0.7 x VA
34 3 = 0.8 x VA
35 4 = 0.83 x VA
36 5 = 0.91 x VA
62 VA-supply = <&reg_audio>;
Dcs42l52.txt30 0 = 0.5 x VA
31 1 = 0.6 x VA
32 2 = 0.7 x VA
33 3 = 0.8 x VA
34 4 = 0.83 x VA
35 5 = 0.91 x VA
Dgoogle,sc7280-herobrine.yaml107 "VA DMIC0", "MIC BIAS3",
108 "VA DMIC1", "MIC BIAS3",
109 "VA DMIC2", "MIC BIAS4",
110 "VA DMIC3", "MIC BIAS4",
Dcirrus,cs4234.yaml39 VA-supply:
53 - VA-supply
69 VA-supply = <&vdd3v3>;
Dcs42xx8.txt14 - VA-supply, VD-supply, VLS-supply, VLC-supply: power supplies for the device,
29 VA-supply = <&reg_audio>;
Dcirrus,cs42l51.yaml38 VA-supply:
66 VA-supply = <&reg_audio>;
Dcs53l30.txt9 - VA-supply, VP-supply : power supplies for the device,
42 VA-supply = <&cs53l30_va>;
Dcs43130.txt10 - VA-supply, VP-supply, VL-supply, VCP-supply, VD-supply:
55 VA-supply = <&dummy_vreg>;
Dcs35l32.txt10 - VA-supply, VP-supply : power supplies for the device,
61 VA-supply = <&reg_audio>;
Dcirrus,cs35l41.yaml33 VA-supply:
34 description: voltage regulator phandle for the VA supply
186 VA-supply = <&dummy_vreg>;
Dcirrus,cs42l42.yaml45 VA-supply:
194 - VA-supply
208 VA-supply = <&dummy_vreg>;
Dcs35l33.txt9 - VA-supply, VP-supply : power supplies for the device,
89 - cirrus,vp-hg-va : VA calculation reference for automatic VPhg tracking
100 VA-supply = <&ldo5_reg>;
Dqcom,sm8250.yaml151 "VA DMIC0", "vdd-micb",
152 "VA DMIC1", "vdd-micb";
206 link-name = "VA Capture";
/linux-6.1.9/arch/arm64/boot/dts/qcom/
Dsc7280-herobrine-villager-r1.dts28 "VA DMIC0", "vdd-micb",
29 "VA DMIC1", "vdd-micb",
30 "VA DMIC2", "vdd-micb",
31 "VA DMIC3", "vdd-micb",
Dsc7280-crd-r3.dts96 "VA DMIC0", "MIC BIAS1",
97 "VA DMIC1", "MIC BIAS1",
98 "VA DMIC2", "MIC BIAS3",
99 "VA DMIC3", "MIC BIAS3",
Dsc7280-herobrine-audio-wcd9385.dtsi19 "VA DMIC0", "MIC BIAS1",
20 "VA DMIC1", "MIC BIAS1",
21 "VA DMIC2", "MIC BIAS3",
22 "VA DMIC3", "MIC BIAS3",
/linux-6.1.9/arch/powerpc/xmon/
Dppc-opc.c729 #define VA UI7 + 1 macro
733 #define VB VA + 1
3089 {"vaddubm", VX (4, 0), VX_MASK, PPCVEC, 0, {VD, VA, VB}},
3090 {"vmul10cuq", VX (4, 1), VXVB_MASK, PPCVEC3, 0, {VD, VA}},
3091 {"vmaxub", VX (4, 2), VX_MASK, PPCVEC, 0, {VD, VA, VB}},
3092 {"vrlb", VX (4, 4), VX_MASK, PPCVEC, 0, {VD, VA, VB}},
3093 {"vcmpequb", VXR(4, 6,0), VXR_MASK, PPCVEC, 0, {VD, VA, VB}},
3094 {"vcmpneb", VXR(4, 7,0), VXR_MASK, PPCVEC3, 0, {VD, VA, VB}},
3095 {"vmuloub", VX (4, 8), VX_MASK, PPCVEC, 0, {VD, VA, VB}},
3096 {"vaddfp", VX (4, 10), VX_MASK, PPCVEC, 0, {VD, VA, VB}},
[all …]
/linux-6.1.9/Documentation/arm64/
Dmemory.rst103 52-bit VA support in the kernel
113 to the kasan shadow being a fraction of the entire kernel VA space,
115 kernel VA space for both 48/52-bit. (Switching from 48-bit to 52-bit,
125 As a single binary will need to support both 48-bit and 52-bit VA
130 code that does need to know the VA size the variables are
133 VA_BITS constant the *maximum* VA space size
135 VA_BITS_MIN constant the *minimum* VA space size
137 vabits_actual variable the *actual* VA space size
147 VA space maximum size of 48-bits, the kernel will, by default,
/linux-6.1.9/arch/arm/kernel/
Dphys2virt.S65 @ sub <VA>, <PA>, <reg>
69 @ add <PA>, <VA>, <reg>
73 @ adds <PAlo>, <VA>, <reg>
144 @ phys-to-virt: sub <VA>, <PA>, #offset<31:24>, lsl #24
145 @ sub <VA>, <PA>, #offset<23:16>, lsl #16
147 @ virt-to-phys (non-LPAE): add <PA>, <VA>, #offset<31:24>, lsl #24
148 @ add <PA>, <VA>, #offset<23:16>, lsl #16
151 @ adds <PAlo>, <VA>, <reg>, lsl #20
/linux-6.1.9/Documentation/loongarch/
Dintroduction.rst296 relationship between virtual address (VA) and physical address (PA)::
298 VA = PA + FixedOffset
300 Page-mapped virtual memory has arbitrary relationship between VA and PA, which
316 KPRANGE1, PA is equal to VA with bit30~31 cleared. For example, the uncached
317 direct-mapped VA of 0x00001000 is 0x80001000, and the cached direct-mapped
318 VA of 0x00001000 is 0xA0001000.
336 XKPRANGE, PA is equal to VA with bits 60~63 cleared, and the cache attribute
337 is configured by bits 60~61 in VA: 0 is for strongly-ordered uncached, 1 is
342 To put this in action: the strongly-ordered uncached direct-mapped VA (in
344 direct-mapped VA (in XKPRANGE) of 0x00000000_00001000 is 0x90000000_00001000,
[all …]
/linux-6.1.9/Documentation/xtensa/
Dmmu.rst24 - VA = virtual address (two upper nibbles of it);
37 VA PA PA PA PA VA PA PA
/linux-6.1.9/arch/s390/include/asm/
Dvx-insn.h598 .macro VA vr1, vr2, vr3, m4
607 VA \vr1, \vr2, \vr3, 0
610 VA \vr1, \vr2, \vr3, 1
613 VA \vr1, \vr2, \vr3, 2
616 VA \vr1, \vr2, \vr3, 3
619 VA \vr1, \vr2, \vr3, 4
/linux-6.1.9/Documentation/translations/zh_CN/mm/
Dzsmalloc.rst28 映射，因为这在32位系统上会导致问题，因为内核空间映射的VA区域非常小。因此，在使用分配
/linux-6.1.9/Documentation/translations/zh_CN/loongarch/
Dintroduction.rst262 直接映射虚拟内存通过CSR.DMWn（n=0~3）来进行配置，虚拟地址（VA）和物理地址（PA）
265 VA = PA + 固定偏移
267 分页映射的虚拟地址（VA）和物理地址（PA）有任意的映射关系，这种关系记录在TLB和页
/linux-6.1.9/Documentation/gpu/rfc/
Di915_vm_bind.rst27 * Multiple Virtual Address (VA) mappings can map to the same physical pages
29 * VA mapping can map to a partial section of the BO (partial binding).
65 In VM_BIND mode, VA allocation is completely managed by the user instead of
66 the i915 driver. Hence all VA assignment, eviction are not applicable in
71 So, a lot of existing code supporting execbuf2 ioctl, like relocations, VA

123