| /linux-5.19.10/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_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_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_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-5.19.10/Documentation/filesystems/ |
| D | qnx6.rst | 56 data and the addressing levels in that specific tree.
60 Level 1 adds an additional indirect addressing level where each indirect
61 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
62 Level 2 adds an additional indirect addressing block level (so, already up
66 indirect addressing blocks or inodes.
97 For more than 16 blocks an indirect addressing in form of another tree is
143 Long filenames are stored in a separate addressing tree. The staring point
165 smaller than addressing space in the bitmap.
183 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
|
| /linux-5.19.10/Documentation/scsi/ |
| D | aha152x.rst | 126 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
128 C/H/S addressing.
131 as base for requests in C/H/S addressing. SCSI only knows about the
135 geometry just to be able to support that addressing scheme. The geometry
141 instead of C/H/S addressing. Unfortunately C/H/S addressing is also used
145 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.
|
| /linux-5.19.10/Documentation/x86/x86_64/ |
| D | fsgs.rst | 7 memory can use segment register based addressing mode. The following
38 applications. GCC and Clang support GS based addressing via address space
85 more flexible usage of the FS/GS addressing modes in user space
141 Compiler support for FS/GS based addressing
144 GCC version 6 and newer provide support for FS/GS based addressing via
189 FS/GS based addressing with inline assembly
193 be used for FS/GS based addressing mode::
|
| /linux-5.19.10/drivers/memory/ |
| D | emif.c | 306 static u32 get_zq_config_reg(const struct lpddr2_addressing *addressing, in get_zq_config_reg() argument
311 val = EMIF_ZQCS_INTERVAL_US * 1000 / addressing->tREFI_ns; in get_zq_config_reg()
335 static u32 get_temp_alert_config(const struct lpddr2_addressing *addressing, in get_temp_alert_config() argument
348 interval /= addressing->tREFI_ns; /* Convert to refresh cycles */ in get_temp_alert_config()
717 const struct lpddr2_addressing *addressing; in emif_onetime_settings() local
721 addressing = get_addressing_table(device_info); in emif_onetime_settings()
734 zq = get_zq_config_reg(addressing, device_info->cs1_used, in emif_onetime_settings()
744 temp_alert_cfg = get_temp_alert_config(addressing, in emif_onetime_settings()
|
| /linux-5.19.10/Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 17 which the controller driver is aware of the opcodes, addressing, and other
67 flash chip such as addressing mode. Call it whenever detach the driver from
|
| /linux-5.19.10/arch/sh/mm/ |
| D | Kconfig | 70 # Physical addressing modes
81 bool "Support 32-bit physical addressing through PMB"
86 If you say Y here, physical addressing will be extended to
88 29-bit physical addressing will be used.
|
| /linux-5.19.10/Documentation/devicetree/bindings/mtd/ |
| D | jedec,spi-nor.yaml | 64 Some flash devices utilize stateful addressing modes (e.g., for 32-bit
65 addressing) which need to be managed carefully by a system. Because these
|
| /linux-5.19.10/arch/s390/boot/ |
| D | head.S | 42 sam64 # switch to 64 bit addressing mode
214 # normal startup-code, running in absolute addressing mode
231 # kdump startup-code, running in 64 bit absolute addressing mode
244 sam64 # switch to 64 bit addressing mode
|
| D | head_kdump.S | 25 sam64 # Switch to 64 bit addressing
|
| /linux-5.19.10/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-5.19.10/Documentation/networking/ |
| D | j1939.rst | 11 sophisticated addressing scheme and extends the maximum packet size above 8
32 addressing and transport methods used by J1939.
42 * **Dynamic addressing:** Address Claiming in J1939 is time critical.
46 results in a consistent J1939 bus with proper addressing.
135 Both static and dynamic addressing methods can be used.
141 For dynamic addressing, so-called Address Claiming, extra support is foreseen
|
| /linux-5.19.10/arch/mips/sgi-ip27/ |
| D | Kconfig | 3 prompt "Node addressing mode"
|
| /linux-5.19.10/arch/alpha/lib/ |
| D | ev6-memset.S | 84 subq $3,8,$3 # E : Invert (for addressing uses)
262 subq $3,8,$3 # E : Invert (for addressing uses)
450 subq $3,8,$3 # E : Invert (for addressing uses)
|
| /linux-5.19.10/Documentation/devicetree/bindings/mailbox/ |
| D | qcom-ipcc.yaml | 15 addressing scheme called protocol, client and signal. For example, consider an
|
| /linux-5.19.10/arch/s390/kernel/ |
| D | text_amode31.S | 123 sam64 # Switch to 64 bit addressing mode
|
| /linux-5.19.10/Documentation/core-api/ |
| D | dma-api-howto.rst | 149 DMA addressing capabilities
153 addressing. For a 64-bit capable device, this needs to be increased, and for
157 64-bit addressing (DAC) for all transactions. And at least one platform (SGI
162 your devices DMA addressing capabilities.
206 The standard 64-bit addressing device would do something like this::
213 If the device only supports 32-bit addressing for descriptors in the
231 dev_warn(dev, "mydev: 24-bit DMA addressing not available\n");
243 DMA addressing limitations, you may wish to probe each mask and
274 and thus retaining the 16MB DMA addressing limitations of ISA.
|
| /linux-5.19.10/Documentation/hwmon/ |
| D | abituguru-datasheet.rst | 59 The uGuru has a number of different addressing levels. The first addressing
71 terminology for the addressing within a bank this is not 100% correct, in
72 bank 0x24 for example the addressing within the bank selects a PWM output not
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/ |
| D | dsi-controller.yaml | 50 from 0 to 3, as DSI uses a 2-bit addressing scheme. Some DSI
|
| /linux-5.19.10/arch/m68k/ |
| D | Kconfig | 76 Select if you want MMU-based virtualised addressing space
|