Searched full:64 (Results 1 – 25 of 629) sorted by relevance
12345678910>>...26
/Documentation/devicetree/bindings/opp/ |
D | qcom-nvmem-cpufreq.txt | 149 opp-hz = /bits/ 64 <307200000>; 155 opp-hz = /bits/ 64 <384000000>; 161 opp-hz = /bits/ 64 <422400000>; 167 opp-hz = /bits/ 64 <460800000>; 173 opp-hz = /bits/ 64 <480000000>; 179 opp-hz = /bits/ 64 <537600000>; 185 opp-hz = /bits/ 64 <556800000>; 191 opp-hz = /bits/ 64 <614400000>; 197 opp-hz = /bits/ 64 <652800000>; 203 opp-hz = /bits/ 64 <691200000>; [all …]
|
D | allwinner,sun50i-h6-operating-points.yaml | 69 opp-hz = /bits/ 64 <480000000>; 78 opp-hz = /bits/ 64 <720000000>; 87 opp-hz = /bits/ 64 <816000000>; 96 opp-hz = /bits/ 64 <888000000>; 105 opp-hz = /bits/ 64 <1080000000>; 114 opp-hz = /bits/ 64 <1320000000>; 123 opp-hz = /bits/ 64 <1488000000>;
|
D | opp.txt | 85 - opp-hz: Frequency in Hz, expressed as a 64-bit big-endian integer. This is a 222 opp-hz = /bits/ 64 <1000000000>; 229 opp-hz = /bits/ 64 <1100000000>; 235 opp-hz = /bits/ 64 <1200000000>; 301 opp-hz = /bits/ 64 <1000000000>; 308 opp-hz = /bits/ 64 <1100000000>; 314 opp-hz = /bits/ 64 <1200000000>; 377 opp-hz = /bits/ 64 <1000000000>; 384 opp-hz = /bits/ 64 <1100000000>; 390 opp-hz = /bits/ 64 <1200000000>; [all …]
|
/Documentation/devicetree/bindings/net/can/ |
D | bosch,m_can.yaml | 70 29-bit Filter 0-64 elements / 0-128 words 71 Rx FIFO 0 0-64 elements / 0-1152 words 72 Rx FIFO 1 0-64 elements / 0-1152 words 73 Rx Buffers 0-64 elements / 0-1152 words 74 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/devicetree/bindings/cpufreq/ |
D | cpufreq-mediatek.txt | 34 opp-hz = /bits/ 64 <598000000>; 39 opp-hz = /bits/ 64 <747500000>; 44 opp-hz = /bits/ 64 <1040000000>; 49 opp-hz = /bits/ 64 <1196000000>; 54 opp-hz = /bits/ 64 <1300000000>; 94 opp-hz = /bits/ 64 <507000000>; 99 opp-hz = /bits/ 64 <702000000>; 104 opp-hz = /bits/ 64 <1001000000>; 109 opp-hz = /bits/ 64 <1105000000>; 114 opp-hz = /bits/ 64 <1183000000>; [all …]
|
D | ti-cpufreq.txt | 71 opp-hz = /bits/ 64 <300000000>; 78 opp-hz = /bits/ 64 <275000000>; 85 opp-hz = /bits/ 64 <300000000>; 92 opp-hz = /bits/ 64 <500000000>; 98 opp-hz = /bits/ 64 <600000000>; 104 opp-hz = /bits/ 64 <600000000>; 110 opp-hz = /bits/ 64 <720000000>; 116 opp-hz = /bits/ 64 <720000000>; 122 opp-hz = /bits/ 64 <800000000>; 128 opp-hz = /bits/ 64 <1000000000>;
|
/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/ia64/ |
D | ia64.rst | 2 Linux kernel release for the IA-64 Platform 5 These are the release notes for Linux since version 2.4 for IA-64 6 platform. This document provides information specific to IA-64 13 - IA-64 kernel installation is the same as the other platforms, see 20 Compiling and running this kernel requires an IA-64 compliant GCC 22 IA-64 compliant GCC compiler. 34 the original README for details BUT make sure you have an IA-64 37 IA-64 Specifics
|
/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/gpu/ |
D | arm,mali-bifrost.yaml | 96 opp-hz = /bits/ 64 <533000000>; 100 opp-hz = /bits/ 64 <450000000>; 104 opp-hz = /bits/ 64 <400000000>; 108 opp-hz = /bits/ 64 <350000000>; 112 opp-hz = /bits/ 64 <266000000>; 116 opp-hz = /bits/ 64 <160000000>; 120 opp-hz = /bits/ 64 <100000000>;
|
D | arm,mali-midgard.yaml | 150 opp-hz = /bits/ 64 <533000000>; 154 opp-hz = /bits/ 64 <450000000>; 158 opp-hz = /bits/ 64 <400000000>; 162 opp-hz = /bits/ 64 <350000000>; 166 opp-hz = /bits/ 64 <266000000>; 170 opp-hz = /bits/ 64 <160000000>; 174 opp-hz = /bits/ 64 <100000000>;
|
/Documentation/devicetree/bindings/devfreq/ |
D | exynos-bus.txt | 204 opp-hz = /bits/ 64 <50000000>; 208 opp-hz = /bits/ 64 <100000000>; 212 opp-hz = /bits/ 64 <134000000>; 216 opp-hz = /bits/ 64 <200000000>; 220 opp-hz = /bits/ 64 <400000000>; 294 opp-hz = /bits/ 64 <50000000>; 298 opp-hz = /bits/ 64 <80000000>; 302 opp-hz = /bits/ 64 <100000000>; 306 opp-hz = /bits/ 64 <134000000>; 310 opp-hz = /bits/ 64 <200000000>; [all …]
|
/Documentation/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 …]
|
D | cpu-hotplug-spec.rst | 4 Firmware support for CPU hotplug under Linux/x86-64 7 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to 16 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable
|
/Documentation/admin-guide/cgroup-v1/ |
D | hugetlb.rst | 33 For a system supporting three hugepage sizes (64k, 32M and 1G), the control 44 hugetlb.64KB.limit_in_bytes 45 hugetlb.64KB.max_usage_in_bytes 46 hugetlb.64KB.usage_in_bytes 47 hugetlb.64KB.failcnt 48 hugetlb.64KB.rsvd.limit_in_bytes 49 hugetlb.64KB.rsvd.max_usage_in_bytes 50 hugetlb.64KB.rsvd.usage_in_bytes 51 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/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/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/userspace-api/media/v4l/ |
D | pixfmt-nv12mt.rst | 12 memory layout. Pixels are grouped in macroblocks of 64x32 size. The 20 grouped into 64x32 macroblocks. The three components are separated into 22 are grouped into 64x32 macroblocks. The CbCr plane has the same width, 24 The chroma plane is also grouped into 64x32 macroblocks.
|
D | pixfmt-meta-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)
|
/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/devicetree/bindings/input/ |
D | microchip,qt1050.txt | 40 Valid values: 1, 4, 16, 64, 256, 1024, 4096, 16384; default is 1. 43 Valid values: 1, 2, 4, 8, 16, 32, 64, 128; default is 1. 60 microchip,average-samples = <64>; 68 microchip,average-samples = <64>;
|
/Documentation/security/keys/ |
D | ecryptfs.rst | 50 keylen:= 64 55 Create an encrypted key "1000100010001000" of length 64 bytes with format 58 $ keyctl add encrypted 1000100010001000 "new ecryptfs user:test 64" @u 62 ecryptfs user:test 64 490045d4bfe48c99f0d465fbbbb79e7500da954178e2de0697
|
12345678910>>...26