Searched refs:uses (Results 1 – 25 of 1168) sorted by relevance
12345678910>>...47
| /Linux-v5.10/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.txt | 4 this M4U have two generations of HW architecture. Generation one uses flat
5 pagetable, and only supports 4K size page mapping. Generation two uses the
59 "mediatek,mt2701-m4u" for mt2701 which uses generation one m4u HW.
60 "mediatek,mt2712-m4u" for mt2712 which uses generation two m4u HW.
61 "mediatek,mt6779-m4u" for mt6779 which uses generation two m4u HW.
62 "mediatek,mt7623-m4u", "mediatek,mt2701-m4u" for mt7623 which uses
64 "mediatek,mt8167-m4u" for mt8167 which uses generation two m4u HW.
65 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
66 "mediatek,mt8183-m4u" for mt8183 which uses generation two m4u HW.
|
| /Linux-v5.10/Documentation/devicetree/bindings/regulator/ |
| D | samsung,s5m8767.txt | 31 [1] If none of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
36 If either of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
41 - s5m8767,pmic-buck2-uses-gpio-dvs: 'buck2' can be controlled by gpio dvs.
42 - s5m8767,pmic-buck3-uses-gpio-dvs: 'buck3' can be controlled by gpio dvs.
43 - s5m8767,pmic-buck4-uses-gpio-dvs: 'buck4' can be controlled by gpio dvs.
85 s5m8767,pmic-buck2-uses-gpio-dvs;
86 s5m8767,pmic-buck3-uses-gpio-dvs;
87 s5m8767,pmic-buck4-uses-gpio-dvs;
|
| D | max8997-regulator.txt | 25 [1] If none of the 'max8997,pmic-buck[1/2/5]-uses-gpio-dvs' optional
30 If either of the 'max8997,pmic-buck[1/2/5]-uses-gpio-dvs' optional
38 - max8997,pmic-buck1-uses-gpio-dvs: 'buck1' can be controlled by gpio dvs.
39 - max8997,pmic-buck2-uses-gpio-dvs: 'buck2' can be controlled by gpio dvs.
40 - max8997,pmic-buck5-uses-gpio-dvs: 'buck5' can be controlled by gpio dvs.
96 max8997,pmic-buck1-uses-gpio-dvs;
97 max8997,pmic-buck2-uses-gpio-dvs;
98 max8997,pmic-buck5-uses-gpio-dvs;
|
| /Linux-v5.10/drivers/pci/controller/dwc/ |
| D | Kconfig | 36 This uses the DesignWare core.
51 This uses the DesignWare core.
117 DesignWare hardware and therefore the driver re-uses the
129 on DesignWare hardware and therefore the driver re-uses the
174 PCIe controller uses the DesignWare core plus Qualcomm-specific
185 DesignWare hardware and therefore the driver re-uses the
199 host mode. This uses the DesignWare core.
209 endpoint mode. This uses the DesignWare core.
219 The PCIe controller uses the DesignWare core plus Intel-specific
247 and therefore the driver re-uses the DesignWare core functions to
[all …]
|
| /Linux-v5.10/drivers/media/cec/platform/ |
| D | Kconfig | 23 This is a driver for Amlogic Meson SoCs AO CEC interface. It uses the
39 It uses the generic CEC framework interface.
61 This is a driver for Samsung S5P HDMI CEC interface. It uses the
72 This is a driver for STIH4xx HDMI CEC interface. It uses the
84 This is a driver for STM32 interface. It uses the
95 This is a driver for the Tegra HDMI CEC interface. It uses the
|
| /Linux-v5.10/Documentation/features/sched/membarrier-sync-core/ |
| D | arch-support.txt | 15 # x86-32 uses IRET as return from interrupt, which takes care of the IPI.
16 # However, it uses both IRET and SYSEXIT to go back to user-space. The IRET
19 # x86-64 uses IRET as return from interrupt, which takes care of the IPI.
|
| /Linux-v5.10/drivers/gnss/ |
| D | Kconfig | 24 Say Y here if you have a Mediatek-based GNSS receiver which uses a
36 Say Y here if you have a SiRFstar-based GNSS receiver which uses a
49 Say Y here if you have a u-blox GNSS receiver which uses a serial
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/ |
| D | ssd1307fb.txt | 23 - solomon,com-seq: Display uses sequential COM pin configuration
24 - solomon,com-lrremap: Display uses left-right COM pin remap
25 - solomon,com-invdir: Display uses inverted COM pin scan direction
38 - solomon,area-color-enable: Display uses color mode
|
| /Linux-v5.10/Documentation/devicetree/bindings/fpga/ |
| D | xlnx,zynqmp-pcap-fpga.txt | 2 The ZynqMP SoC uses the PCAP (Processor configuration Port) to configure the
3 Programmable Logic (PL). The configuration uses the firmware interface.
|
| /Linux-v5.10/Documentation/userspace-api/ioctl/ |
| D | ioctl-decoding.rst | 9 uses 3 bits to encode read/write and 13 bits for size.
14 31-30 00 - no parameters: uses _IO macro
|
| /Linux-v5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 14 # core requirement, and one uses "select" while the other uses "depends on" to
32 # with CORE, one uses "depends on" while the other uses "select". Another
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-system-ibm-rtl | 12 Users: The ibm-prtm userspace daemon uses this interface.
22 Users: The ibm-prtm userspace daemon uses this interface.
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/mediatek/ |
| D | mediatek,mipi0a.txt | 13 The mipi0a controller uses the common clk binding from
17 The mipi0a controller also uses the common power domain from
|
| D | mediatek,vcodecsys.txt | 12 The vcodecsys controller uses the common clk binding from
16 The vcodecsys controller also uses the common power domain from
|
| D | mediatek,infracfg.txt | 26 The infracfg controller uses the common clk binding from
29 Also it uses the common reset controller binding from
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | gfs2.rst | 12 file system, but also uses a lock module to allow the computers coordinate
17 GFS uses interchangeable inter-node locking mechanisms, the currently
24 - uses a distributed lock manager (dlm) for inter-node locking.
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | pwm-fan.rst | 4 This driver enables the use of a PWM module to drive a fan. It uses the
15 a PWM output. It uses the generic PWM interface, thus it can be used with
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | keystone-gate.txt | 3 Binding for Keystone gate control driver which uses PSC controller IP.
5 This binding uses the common clock binding[1].
|
| /Linux-v5.10/fs/squashfs/ |
| D | Kconfig | 8 filesystem for Linux. It uses zlib, lzo or xz compression to
77 By default Squashfs uses a single decompressor but it gives
84 This decompressor implementation uses up to two parallel
91 By default Squashfs uses a single decompressor but it gives
95 This decompressor implementation uses a maximum of one
96 decompressor per core. It uses percpu variables to ensure
222 SquashFS uses less memory at the expense of extra reads from disk.
|
| /Linux-v5.10/Documentation/devicetree/bindings/dma/ |
| D | sirfsoc-dma.txt | 28 channel request line is 9 of the 2nd dma controller, while write channel uses
30 dma controller, while write channel uses 13 of the 1st dma controller:
|
| /Linux-v5.10/arch/arc/lib/ |
| D | memcpy-700.S | 31 ; uses long immediate
37 ; uses long immediate
|
| /Linux-v5.10/arch/arm/crypto/ |
| D | Kconfig | 77 since it uses lookup tables. However, as countermeasures it
104 Use an implementation of AES in CBC, CTR and XTS modes that uses
115 that uses the 64x64 to 128 bit polynomial multiplication (vmull.p64)
117 uses the vmull.p8 instruction that is part of the basic NEON ISA.
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | mc13xxx.txt | 7 - fsl,mc13xxx-uses-adc : Indicate the ADC is being used
8 - fsl,mc13xxx-uses-codec : Indicate the Audio Codec is being used
9 - fsl,mc13xxx-uses-rtc : Indicate the RTC is being used
10 - fsl,mc13xxx-uses-touch : Indicate the touchscreen controller is being used
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | slimbus.rst | 11 MIPI (Mobile Industry Processor Interface) alliance. The bus uses master/slave
15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses
25 channel uses dedicated ports on the device.
51 Per specification, SLIMbus uses "clock gears" to do power management based on
107 mode. Controller uses this sequence when it decides to enter low-power mode so
|
| /Linux-v5.10/Documentation/ia64/ |
| D | aliasing.rst | 24 System memory typically uses the WB attribute. The UC attribute is
41 supported attributes for each region. At boot-time, the kernel uses
46 The kernel uses the efi_memmap table returned from GetMemoryMap() to
99 This uses remap_pfn_range(), which creates user mappings. These
120 "X" uses this to access VGA frame buffers. Using legacy_mem
142 This uses copy_from_user(), which implicitly uses a kernel
200 which uses a granule-sized UC mapping. This granule will cover some
|
12345678910>>...47
