| /linux-4.4.14/drivers/memory/ |
| D | emif.c | 66 const struct lpddr2_addressing *addressing; member
415 const struct lpddr2_addressing *addressing) in get_sdram_ref_ctrl_shdw() argument
421 t_refi = addressing->tREFI_ns / 100; in get_sdram_ref_ctrl_shdw()
435 const struct lpddr2_addressing *addressing) in get_sdram_tim_1_shdw() argument
442 if (addressing->num_banks == B8) in get_sdram_tim_1_shdw()
468 const struct lpddr2_addressing *addressing) in get_sdram_tim_1_shdw_derated() argument
479 if (addressing->num_banks == B8) { in get_sdram_tim_1_shdw_derated()
508 const struct lpddr2_addressing *addressing, in get_sdram_tim_2_shdw() argument
520 val = DIV_ROUND_UP(addressing->tRFCab_ps + 10000, t_ck) - 1; in get_sdram_tim_2_shdw()
534 const struct lpddr2_addressing *addressing, in get_sdram_tim_3_shdw() argument
[all …]
|
| /linux-4.4.14/arch/m68k/math-emu/ |
| D | fp_decode.h | 112 | extract the addressing mode
128 | extract the register for the addressing mode
214 | addressing mode: data register direct
220 | addressing mode: address register indirect
244 | addressing mode: address register indirect with postincrement
263 | addressing mode: address register indirect with predecrement
289 | addressing mode: address register/programm counter indirect
331 | all other indirect addressing modes will finally end up here
345 | addressing mode: address register/programm counter indirect
355 3: | addressing mode: address register/programm counter memory indirect
|
| D | fp_move.S | 64 | encode addressing mode for dest
72 | addressing mode: data register direct
135 | addressing mode: address register indirect
140 | addressing mode: address register indirect with postincrement
145 | addressing mode: address register indirect with predecrement
150 | addressing mode: address register indirect with 16bit displacement
|
| D | fp_scan.S | 133 | decode addressing mode for source
141 | addressing mode: data register direct
171 | addressing mode: address register indirect
176 | addressing mode: address register indirect with postincrement
181 | addressing mode: address register indirect with predecrement
186 | addressing mode: address register/programm counter indirect
192 | all other indirect addressing modes will finally end up here
197 | all pc relative addressing modes and immediate/absolute modes end up here
211 | addressing mode: absolute short
216 | addressing mode: absolute long
[all …]
|
| D | fp_movem.S | 88 | addressing mode: address register indirect
93 | addressing mode: address register indirect with postincrement
102 | addressing mode: address register/programm counter indirect
|
| D | fp_cond.S | 105 | decode addressing mode
113 | addressing mode: data register direct
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | qnx6.txt | 50 data and the addressing levels in that specific tree.
53 Level 1 adds an additional indirect addressing level where each indirect
54 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
55 Level 2 adds an additional indirect addressing block level (so, already up
59 indirect addressing blocks or inodes.
87 For more than 16 blocks an indirect addressing in form of another tree is
127 Long filenames are stored in a separate addressing tree. The staring point
146 smaller than addressing space in the bitmap.
161 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
|
| D | fiemap.txt | 169 based addressing scheme. Since returning an extent for each block back to
|
| D | logfs.txt | 124 Another difference is the addressing of indirect blocks. In LogFS,
|
| D | f2fs.txt | 13 addressing the fundamental issues in LFS, which are snowball effect of wandering
|
| /linux-4.4.14/Documentation/scsi/ |
| D | aha152x.txt | 107 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
109 C/H/S addressing.
112 as base for requests in C/H/S addressing. SCSI only knows about the
116 geometry just to be able to support that addressing scheme. The geometry
122 instead of C/H/S addressing. Unfortunately C/H/S addressing is also used
126 Moreover there are certain limitations to the C/H/S addressing scheme,
|
| D | ChangeLog.sym53c8xx_2 | 105 - Add infrastructure for the forthcoming 64 bit DMA addressing support.
111 - Add support for 64 bit DMA addressing using segment registers.
|
| D | sym53c8xx_2.txt | 173 The LOAD/STORE instructions support absolute and DSA relative addressing
187 The 896 and 1010 chips support 64 bit PCI transactions and addressing,
188 while the 895A supports 32 bit PCI transactions and 64 bit addressing.
|
| D | ncr53c8xx.txt | 200 The LOAD/STORE instructions support absolute and DSA relative addressing
212 The 896 chip supports 64 bit PCI transactions and addressing, while the
213 895A supports 32 bit PCI transactions and 64 bit addressing.
1217 addressing logic when the DATA IN phase is entered and so prevents the bug
|
| D | ChangeLog.sym53c8xx | 68 addressing (FE_DAC) and 64 bit PCI interface (FE_64BIT).
354 one channel and has a 32 bit PCI bus. It does 64 bit PCI addressing
|
| D | ChangeLog.lpfc | 863 * Minimal support for SCSI flat space addressing/volume set
864 addressing. Use 16 bits of LUN address so that flat
865 addressing/VSA will work.
1381 * Add log message 249 to log any unsupported device addressing
|
| D | ChangeLog.ncr53c8xx | 159 one channel and has a 32 bit PCI bus. It does 64 bit PCI addressing
|
| D | scsi_mid_low_api.txt | 1218 unchecked_isa_dma - 1=>only use bottom 16 MB of ram (ISA DMA addressing
|
| /linux-4.4.14/arch/sh/mm/ |
| D | Kconfig | 73 # Physical addressing modes
85 bool "Support 32-bit physical addressing through PMB"
90 If you say Y here, physical addressing will be extended to
92 29-bit physical addressing will be used.
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head.S | 157 sam31 # switch to 31 bit addressing mode
267 # startup-code at 0x10000, running in absolute addressing mode
284 # kdump startup-code at 0x10010, running in 64 bit absolute addressing mode
297 sam64 # switch to 64 bit addressing mode
|
| D | head_kdump.S | 25 sam64 # Switch to 64 bit addressing
|
| D | base.S | 109 sam64 # Switch to 64 bit addressing mode
|
| D | head64.S | 89 # startup-code, running in absolute addressing mode
|
| D | relocate_kernel.S | 48 sam64 # switch to 64 bit addressing mode
|
| /linux-4.4.14/drivers/media/dvb-frontends/drx39xyj/ |
| D | drx_dap_fasi.h | 98 #error At least one of short- or long-addressing format must be allowed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | brcm,bcmgenet.txt | 42 - #address-cells: address cell for MDIO bus addressing, should be 1
43 - #size-cells: size of the cells for MDIO bus addressing, should be 0
|
| /linux-4.4.14/Documentation/ |
| D | DMA-API-HOWTO.txt | 146 DMA addressing limitations
148 Does your device have any DMA addressing limitations? For example, is
158 support 64-bit addressing (DAC) for all transactions. And at least
164 support the DMA addressing limitation your device has. It is good
212 The standard 32-bit addressing device would do something like this:
220 is to try for 64-bit addressing, but back down to a 32-bit mask that
222 platform is not capable of 64-bit addressing. Rather, it may fail in
223 this case simply because 32-bit addressing is done more efficiently
224 than 64-bit addressing. For example, Sparc64 PCI SAC addressing is
225 more efficient than DAC addressing.
[all …]
|
| D | bus-virt-phys-mapping.txt | 18 Essentially, the three ways of addressing memory are (this is "real memory",
|
| D | IPMI.txt | 143 The IPMI addressing works much like IP addresses, you have an overlay
199 data portion is just the data to be send (do NOT put addressing info
|
| D | vfio.txt | 45 meant for translation (ie. solving the addressing problems of devices
|
| D | DMA-API.txt | 141 Part Ic - DMA addressing limitations
|
| D | kernel-parameters.txt | 1545 than 32-bit addressing. The default is to look
|
| /linux-4.4.14/arch/mips/sgi-ip27/ |
| D | Kconfig | 2 prompt "Node addressing mode"
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | ev6-memset.S | 83 subq $3,8,$3 # E : Invert (for addressing uses)
260 subq $3,8,$3 # E : Invert (for addressing uses)
447 subq $3,8,$3 # E : Invert (for addressing uses)
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | snps-dwapb-gpio.txt | 6 - #address-cells : should be 1 (for addressing port subnodes).
|
| /linux-4.4.14/Documentation/mtd/ |
| D | spi-nor.txt | 16 which the controller driver is aware of the opcodes, addressing, and other
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | hdio.txt | 31 HDIO_GET_ADDRESS get sector addressing mode
56 HDIO_SET_ADDRESS change lba addressing modes
114 purely by sector number nowadays (lba addressing), and the
443 The value of the current addressing mode:
594 if LBA48 addressing is enabled for the drive
1024 HDIO_SET_ADDRESS change lba addressing modes
1032 New value for addressing mode
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 53 hierarchical bus addressing. CCI interfaces
54 addresses refer to the parent node addressing
|
| D | vexpress-sysreg.txt | 60 bus via "system control" interface, addressing devices with site number,
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | abituguru-datasheet | 58 The uGuru has a number of different addressing levels. The first addressing
70 terminoligy for the addressing within a bank this is not 100% correct, in
71 bank 0x24 for example the addressing within the bank selects a PWM output not
|
| /linux-4.4.14/arch/arm64/boot/dts/amd/ |
| D | amd-seattle-soc.dtsi | 58 /* DDR range is 40-bit addressing */
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig | 82 Select if you want MMU-based virtualised addressing space
|
| /linux-4.4.14/fs/f2fs/ |
| D | Kconfig | 7 addressing the fundamental issues in LFS, which are snowball effect
|
| /linux-4.4.14/Documentation/arm/ |
| D | memory.txt | 10 The ARM CPU is capable of addressing a maximum of 4GB virtual memory
|
| /linux-4.4.14/drivers/ide/ |
| D | ide-disk.c | 612 ide_devset_get_flag(addressing, IDE_DFLAG_LBA48);
641 ide_ext_devset_rw(address, addressing);
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | CHANGES | 41 3) For an opclass three FP instruction where the effective addressing
|
| D | fpsp.doc | 37 using unimplemented addressing modes. In addition, this package
|
| /linux-4.4.14/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 15 * Try to use LBA instead of track or MSF addressing
89 * Switch to using MSF addressing for audio commands.
|
| /linux-4.4.14/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 387 * 10-27-04 01.05.03 Added defines for new SAS PHY page addressing mode.
558 * WWID addressing.
562 * support Enclosure/Slot addressing rather than WWID
563 * addressing.
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 47 r0-r15 (or gpr0-gpr15), used for arithmetic and addressing.
152 Used to set addressing mode
158 32 1=31 bit addressing mode 0=24 bit addressing mode (for backward
223 The limitation of Intels addressing technique is that the linux
224 kernel uses a very simple real address to virtual addressing technique
248 Our addressing scheme is basically as follows:
264 addressing mode to decide whether we are looking at user or kernel space.
881 modify the PSW to the other addressing mode, display the stuff & then
1028 5=addressing exception
1127 psw to user space addressing so we could get at the first parameter of the open
|
| D | cds.txt | 241 __u8 flags; /* flags, like IDA addressing, etc. */
253 CCW_FLAG_IDA - indirect addressing
|
| /linux-4.4.14/arch/cris/boot/rescue/ |
| D | head_v10.S | 333 btstq 26, $r1 ; Are we addressing first flash?
|
| /linux-4.4.14/fs/cramfs/ |
| D | README | 113 One part of that is addressing endianness. The two options here are
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 1901 # addressing mode was (a7)+. if so, we'll need to shift the
2132 # addressing mode was -(a7). if so, we'll need to shift the
2403 # addressing mode. #
2948 # which can use most addressing modes.
2980 # the instruction is an fmovm.x dynamic which can use many addressing
3293 # if the effective addressing mode was -() or ()+, then the address #
3949 # stacked for the exception is incorrect for -(an) and (an)+ addressing #
|
| D | isp.S | 478 # mul64() may use ()+ addressing and may, therefore, alter a7
491 # div64() may use ()+ addressing and may, therefore, alter a7.
|
| D | fpsp.S | 1902 # addressing mode was (a7)+. if so, we'll need to shift the
2133 # addressing mode was -(a7). if so, we'll need to shift the
2404 # addressing mode. #
2949 # which can use most addressing modes.
2981 # the instruction is an fmovm.x dynamic which can use many addressing
3294 # if the effective addressing mode was -() or ()+, then the address #
18116 # addressing mode is pre-decrement. write the result byte. if the write
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | skeleton.S | 434 | to extract the data register number when the 'Dn' addressing mode is
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig | 292 generate accesses to the data using GR16-relative addressing which
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | platform.txt | 17 is direct addressing from a CPU bus. Rarely, a platform_device will
|
| /linux-4.4.14/arch/mn10300/ |
| D | Kconfig | 219 addressing each time.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 62 - How does the kernel fall short in addressing that problem now?
|
| D | 4.Coding | 221 and try to avoid "fixes" which make the warning go away without addressing
|
| D | 2.Process | 476 never any shortage of issues in need of fixing; by addressing these issues,
|
| /linux-4.4.14/lib/ |
| D | Kconfig | 476 particularly the AC timing parameters and addressing
|
| D | Kconfig.debug | 350 defined weak to work around addressing range issue which
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 122 classful addressing.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 58 exposed by the GPIO interfaces, such as addressing, power management, and more.
|
| D | gpio-legacy.txt | 546 not exposed by the GPIO interfaces, such as addressing, power management,
|
| /linux-4.4.14/arch/arm/crypto/ |
| D | sha1-armv4-large.S | 35 @ instructions with 3 arguments, no [fixed] rotate, addressing
|
| /linux-4.4.14/Documentation/networking/ |
| D | can.txt | 161 medium that has no MAC-layer addressing like ethernet. The CAN-identifier
188 change (except for the according addressing information):
258 interface (which is different from TCP/IP due to different addressing
|
| D | filter.txt | 245 The next table shows addressing formats from the 2nd column:
|
| /linux-4.4.14/arch/x86/math-emu/ |
| D | README | 148 check the addressing, and which runs successfully in real mode,
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig | 1714 benefit is to increase physical addressing equal to or greater
1716 64-bit addressing which in turn makes the PTEs 64-bit in size.
2979 64-bit binaries using 32-bit quantities for addressing and certain
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 1051 int "DMA addressing mode"
1068 The still experimental value 2 (64 bit DMA addressing with 16
1070 PCI address bits past bit 39 to be set for the addressing of
|
| /linux-4.4.14/net/ipv4/ |
| D | Kconfig | 7 This is code for addressing several networked computers at once,
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 196 switches, these functions would utilize direct or indirect PHY addressing mode
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 119 relatively small addressing window (like 64Mib) might run out of
308 Select if you want MMU-based virtualised addressing space
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 637 * Only the first bit of SEQADDR1 holds addressing information
|
| D | aic7xxx.seq | 1289 * operations, which use 32bit addressing, can assume
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 308 addressing to allocate within the first 16MB of address space.
1887 built using 2GiB addressing, and PHYSICAL_ALGIN must be at a
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 463 addressing mode), whatever the calling software requested. But
|