Searched full:64 (Results 1 – 25 of 866) sorted by relevance
12345678910>>...35
| /Documentation/devicetree/bindings/interconnect/ |
| D | mediatek,cci.yaml | 79 opp-hz = /bits/ 64 <273000000>;
83 opp-hz = /bits/ 64 <338000000>;
87 opp-hz = /bits/ 64 <403000000>;
91 opp-hz = /bits/ 64 <463000000>;
95 opp-hz = /bits/ 64 <546000000>;
99 opp-hz = /bits/ 64 <624000000>;
103 opp-hz = /bits/ 64 <689000000>;
107 opp-hz = /bits/ 64 <767000000>;
111 opp-hz = /bits/ 64 <845000000>;
115 opp-hz = /bits/ 64 <871000000>;
[all …]
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-mediatek.txt | 41 opp-hz = /bits/ 64 <598000000>;
46 opp-hz = /bits/ 64 <747500000>;
51 opp-hz = /bits/ 64 <1040000000>;
56 opp-hz = /bits/ 64 <1196000000>;
61 opp-hz = /bits/ 64 <1300000000>;
101 opp-hz = /bits/ 64 <507000000>;
106 opp-hz = /bits/ 64 <702000000>;
111 opp-hz = /bits/ 64 <1001000000>;
116 opp-hz = /bits/ 64 <1105000000>;
121 opp-hz = /bits/ 64 <1183000000>;
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | blocks.rst | 7 sectors between 1KiB and 64KiB, and the number of sectors must be an
11 page size (i.e. 64KiB blocks on a i386 which only has 4KiB memory
12 pages). By default a filesystem can contain 2^32 blocks; if the '64bit'
13 feature is enabled, then a filesystem can have 2^64 blocks. The location
27 - 64KiB
79 For 64-bit filesystems, limits are as follows:
89 - 64KiB
91 - 2^64
92 - 2^64
93 - 2^64
[all …]
|
| /Documentation/devicetree/bindings/net/can/ |
| D | bosch,m_can.yaml | 71 29-bit Filter 0-64 elements / 0-128 words
72 Rx FIFO 0 0-64 elements / 0-1152 words
73 Rx FIFO 1 0-64 elements / 0-1152 words
74 Rx Buffers 0-64 elements / 0-1152 words
75 Tx Event FIFO 0-32 elements / 0-64 words
89 - description: 29-bit Filter 0-64 elements / 0-128 words
91 maximum: 64
92 - description: Rx FIFO 0 0-64 elements / 0-1152 words
94 maximum: 64
95 - description: Rx FIFO 1 0-64 elements / 0-1152 words
[all …]
|
| /Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 150 MODULATION = QAM/64
178 MODULATION = QAM/64
193 MODULATION = QAM/64
208 MODULATION = QAM/64
223 MODULATION = QAM/64
238 MODULATION = QAM/64
253 MODULATION = QAM/64
268 MODULATION = QAM/64
283 MODULATION = QAM/64
298 MODULATION = QAM/64
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nuvoton,sgpio.yaml | 20 to 64 output pins, and up to 64 input pins, the pin is only for GPI or GPO.
53 maximum: 64
60 maximum: 64
85 nuvoton,input-ngpios = <64>;
86 nuvoton,output-ngpios = <64>;
|
| /Documentation/arch/x86/x86_64/ |
| D | mm.rst | 13 from the top of the 64-bit address space. It's easier to understand the layout
17 64-bit address space (ffffffffffffffff).
24 It also shows it nicely how incredibly large 64-bit address space is.
35 …0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
45 …ffff888000000000 | -119.5 TB | ffffc87fffffffff | 64 TB | direct mapping of all physical memory…
63 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
81 from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PB starting
91 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
94 …0100000000000000 | +64 PB | feffffffffffffff | ~16K PB | ... huge, still almost 64 bits wide h…
95 … | | | | virtual memory addresses up to the -64 PB
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 34 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
46 hugetlb.64KB.limit_in_bytes
47 hugetlb.64KB.max_usage_in_bytes
48 hugetlb.64KB.numa_stat
49 hugetlb.64KB.usage_in_bytes
50 hugetlb.64KB.failcnt
51 hugetlb.64KB.rsvd.limit_in_bytes
52 hugetlb.64KB.rsvd.max_usage_in_bytes
53 hugetlb.64KB.rsvd.usage_in_bytes
54 hugetlb.64KB.rsvd.failcnt
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | nvidia,tegra20-ictlr.txt | 34 reg = <0x60004000 64>,
35 <0x60004100 64>,
36 <0x60004200 64>,
37 <0x60004300 64>;
|
| D | marvell,gicp.txt | 25 marvell,spi-ranges = <64 64>, <288 64>;
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2.yaml | 59 opp-hz = /bits/ 64 <1000000000>;
66 opp-hz = /bits/ 64 <1100000000>;
72 opp-hz = /bits/ 64 <1200000000>;
142 opp-hz = /bits/ 64 <1000000000>;
149 opp-hz = /bits/ 64 <1100000000>;
155 opp-hz = /bits/ 64 <1200000000>;
222 opp-hz = /bits/ 64 <1000000000>;
229 opp-hz = /bits/ 64 <1100000000>;
235 opp-hz = /bits/ 64 <1200000000>;
248 opp-hz = /bits/ 64 <1300000000>;
[all …]
|
| D | allwinner,sun50i-h6-operating-points.yaml | 76 opp-hz = /bits/ 64 <480000000>;
85 opp-hz = /bits/ 64 <1080000000>;
94 opp-hz = /bits/ 64 <1488000000>;
110 opp-hz = /bits/ 64 <480000000>;
118 opp-hz = /bits/ 64 <792000000>;
127 opp-hz = /bits/ 64 <1512000000>;
|
| /Documentation/sound/cards/ |
| D | hdspm.rst | 29 * Single Speed -- 1..64 channels
34 all 64 channels are available for the mixer, so channel count
66 * buffer-sizes -- 64,128,256,512,1024,2048,8192 Samples
75 64 Byte accurate. SO it is not really usable for the
83 (Hint: Experimenting I found that the pointer is maximum 64 to
84 large never to small. So if you subtract 64 you always have a
174 * TX 64 channel
176 * Name -- "TX 64 channels mode"
182 Using 64-channel-modus (1) or 56-channel-modus for
242 fader and 64-127 the playback to outputs fader. Value 0
[all …]
|
| /Documentation/admin-guide/auxdisplay/ |
| D | ks0108.rst | 33 :Width: 64
34 :Height: 64
37 :Addresses: 64 each page
39 :Memory size: 8 * 64 * 1 = 512 bytes
|
| /Documentation/devicetree/bindings/gpu/ |
| D | arm,mali-midgard.yaml | 173 opp-hz = /bits/ 64 <533000000>;
177 opp-hz = /bits/ 64 <450000000>;
181 opp-hz = /bits/ 64 <400000000>;
185 opp-hz = /bits/ 64 <350000000>;
189 opp-hz = /bits/ 64 <266000000>;
193 opp-hz = /bits/ 64 <160000000>;
197 opp-hz = /bits/ 64 <100000000>;
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | qcom,x1e80100-mdss.yaml | 150 opp-hz = /bits/ 64 <200000000>;
155 opp-hz = /bits/ 64 <325000000>;
160 opp-hz = /bits/ 64 <375000000>;
165 opp-hz = /bits/ 64 <514000000>;
230 opp-hz = /bits/ 64 <160000000>;
235 opp-hz = /bits/ 64 <270000000>;
240 opp-hz = /bits/ 64 <540000000>;
245 opp-hz = /bits/ 64 <810000000>;
|
| D | qcom,sm7150-mdss.yaml | 189 opp-hz = /bits/ 64 <19200000>;
194 opp-hz = /bits/ 64 <200000000>;
199 opp-hz = /bits/ 64 <300000000>;
204 opp-hz = /bits/ 64 <344000000>;
209 opp-hz = /bits/ 64 <430000000>;
273 opp-hz = /bits/ 64 <180000000>;
278 opp-hz = /bits/ 64 <275000000>;
283 opp-hz = /bits/ 64 <358000000>;
437 opp-hz = /bits/ 64 <160000000>;
442 opp-hz = /bits/ 64 <270000000>;
[all …]
|
| D | qcom,sm7150-dpu.yaml | 118 opp-hz = /bits/ 64 <19200000>;
123 opp-hz = /bits/ 64 <200000000>;
128 opp-hz = /bits/ 64 <300000000>;
133 opp-hz = /bits/ 64 <344000000>;
138 opp-hz = /bits/ 64 <430000000>;
|
| D | qcom,sm8450-dpu.yaml | 114 opp-hz = /bits/ 64 <172000000>;
119 opp-hz = /bits/ 64 <200000000>;
124 opp-hz = /bits/ 64 <325000000>;
129 opp-hz = /bits/ 64 <375000000>;
134 opp-hz = /bits/ 64 <500000000>;
|
| D | qcom,sc7280-mdss.yaml | 241 opp-hz = /bits/ 64 <187500000>;
246 opp-hz = /bits/ 64 <300000000>;
251 opp-hz = /bits/ 64 <358000000>;
330 opp-hz = /bits/ 64 <160000000>;
335 opp-hz = /bits/ 64 <270000000>;
340 opp-hz = /bits/ 64 <540000000>;
345 opp-hz = /bits/ 64 <810000000>;
422 opp-hz = /bits/ 64 <160000000>;
427 opp-hz = /bits/ 64 <270000000>;
432 opp-hz = /bits/ 64 <540000000>;
[all …]
|
| /Documentation/arch/powerpc/ |
| D | kaslr-booke32.rst | 25 image. The memory will be split in 64M zones. We will use the lower 8
26 bit of the entropy to decide the index of the 64M zone. Then we chose a
27 16K aligned offset inside the 64M zone to put the kernel in::
31 |--> 64M <--|
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 21 64-bit-only CPU, then the onlining operation fails and the new CPU is
71 affinity mask contains 64-bit-only CPUs. In this situation, the kernel
90 A subsequent ``execve(2)`` of a 64-bit program by the 32-bit task will
110 ``execve(2)`` of a 32-bit program from a 64-bit deadline task will
112 64-bit-only CPUs and admission control is enabled. Concurrent offlining
129 - A 64-bit task attached to a cpuset which allows only 64-bit CPUs
145 primary CPU (i.e. CPU 0) is 64-bit-only.
|
| /Documentation/scsi/ |
| D | aic7xxx.rst | 35 aic7891 20 PCI/64 40MHz 16Bit 16 3 4 5 6 7 8
36 aic7892 20 PCI/64-66 80MHz 16Bit 16 3 4 5 6 7 8
40 aic7897 20 PCI/64 40MHz 16Bit 16 2 3 4 5 6 7 8
41 aic7899 20 PCI/64-66 80MHz 16Bit 16 2 3 4 5 6 7 8
49 4. 64 Byte SCB Support - Allows disconnected, untagged request table
110 AHA-2940U2 OEM aic7891 PCI/64
114 AHA-2950U2B aic7891 PCI/64 LVD-HD68F LVD-HD68F
117 AHA-3950U2B aic7897 PCI/64
118 AHA-3950U2D aic7897 PCI/64
119 AHA-29160 aic7892 PCI/64-66
[all …]
|
| /Documentation/arch/riscv/ |
| D | vm-layout.rst | 21 RISC-V Linux Kernel 64bit
24 The RISC-V privileged architecture document states that the 64bit addresses
42 …0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
53 ffffffc600000000 | -232 GB | ffffffd5ffffffff | 64 GB | vmalloc/ioremap space
79 …0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
91 … ffffaf8000000000 | -80.5 TB | ffffef7fffffffff | 64 TB | direct mapping of all physical memory
112 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
115 …0100000000000000 | +64 PB | feffffffffffffff | ~16K PB | ... huge, almost 64 bits wide hole of…
116 … | | | | virtual memory addresses up to the -64 PB
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-vsp1-hgo.rst | 25 additionally output the histogram with 64 or 256 bins, resulting in four
28 - In *64 bins normal mode*, the HGO operates on the three channels independently
29 to compute three 64-bins histograms. RGB, YCbCr and HSV image formats are
31 - In *64 bins maximum mode*, the HGO operates on the maximum of the (R, G, B)
32 channels to compute a single 64-bins histogram. Only the RGB image format is
44 .. flat-table:: VSP1 HGO Data - 64 Bins, Normal Mode (792 bytes)
95 .. flat-table:: VSP1 HGO Data - 64 Bins, Max Mode (264 bytes)
|
12345678910>>...35