Home
last modified time | relevance | path

Searched refs:addressing (Results 1 – 25 of 106) sorted by relevance

12345

/linux/arch/m68k/math-emu/
H A Dfp_decode.h112 | 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
H A Dfp_scan.S133 | 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 …]
H A Dfp_move.S64 | 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
H A Dfp_movem.S88 | addressing mode: address register indirect
93 | addressing mode: address register indirect with postincrement
102 | addressing mode: address register/programm counter indirect
H A Dfp_cond.S105 | decode addressing mode
113 | addressing mode: data register direct
/linux/Documentation/filesystems/
H A Dqnx6.rst56 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/Documentation/networking/
H A Diso15765-2.rst29 In its simplest form, ISO-TP is based on two kinds of addressing modes for the
32 * physical addressing is implemented by two node-specific addresses and is used
35 * functional addressing is implemented by one node-specific address and is used
38 Three different addressing formats can be employed:
55 is generating and the optional extended addressing. In the first case, the data
163 additional address component. This enables the "mixed" addressing format if
164 used alone, or the "extended" addressing format if used in conjunction with
191 as extended addressing byte on the reception path. If used in conjunction
193 addressing format.
198 * ``CAN_ISOTP_SF_BROADCAST``: use 1-to-N functional addressing (cannot be
[all …]
/linux/Documentation/scsi/
H A Daha152x.rst126 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,
H A DChangeLog.sym53c8xx_2105 - Add infrastructure for the forthcoming 64 bit DMA addressing support.
111 - Add support for 64 bit DMA addressing using segment registers.
/linux/Documentation/arch/x86/x86_64/
H A Dfsgs.rst7 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/arch/arm/boot/dts/ti/omap/
H A Domap4-cpu-thermal.dtsi16 * See 44xx files for single sensor addressing, omap5 and dra7 need
17 * also sensor ID for addressing.
/linux/Documentation/driver-api/serial/
H A Dserial-rs485.rst110 The Linux kernel provides addressing mode for multipoint RS-485 serial
111 communications line. The addressing mode is enabled with
117 - ``SER_RS485_ADDRB``: Enabled addressing mode (sets also ADDRB in termios).
130 Note: not all devices supporting RS485 support multipoint addressing.
/linux/drivers/memory/
H A Demif.c298 static u32 get_zq_config_reg(const struct lpddr2_addressing *addressing, in get_zq_config_reg() argument
303 val = EMIF_ZQCS_INTERVAL_US * 1000 / addressing->tREFI_ns; in get_zq_config_reg()
327 static u32 get_temp_alert_config(const struct lpddr2_addressing *addressing, in get_temp_alert_config() argument
340 interval /= addressing->tREFI_ns; /* Convert to refresh cycles */ in get_temp_alert_config()
708 const struct lpddr2_addressing *addressing; in emif_onetime_settings() local
712 addressing = get_addressing_table(device_info); in emif_onetime_settings()
725 zq = get_zq_config_reg(addressing, device_info->cs1_used, in emif_onetime_settings()
735 temp_alert_cfg = get_temp_alert_config(addressing, in emif_onetime_settings()
/linux/arch/sh/mm/
H A DKconfig78 # Physical addressing modes
89 bool "Support 32-bit physical addressing through PMB"
94 If you say Y here, physical addressing will be extended to
96 29-bit physical addressing will be used.
/linux/arch/s390/boot/
H A Dhead.S42 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
H A Dhead_kdump.S25 sam64 # Switch to 64 bit addressing
/linux/Documentation/driver-api/cxl/conventions/
H A Dcxl-atl.rst59 Normalized addressing. This is documented in the *ACPI v6.5 Porting Guide*
73 For example, with Normalized addressing the HDM decoders could look as follows::
176 Operating System to detect Normalized addressing and for determining Endpoint
254 configuring HDM decoders on platforms with Normalized addressing. The GUID and
256 the OS identifies the PRM handler, the platform supports Normalized addressing
/linux/drivers/media/dvb-frontends/drx39xyj/
H A Ddrx_dap_fasi.h98 #error At least one of short- or long-addressing format must be allowed.
/linux/arch/alpha/lib/
H A Dev6-memset.S84 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/arch/mips/sgi-ip27/
H A DKconfig3 prompt "Node addressing mode"
/linux/Documentation/core-api/
H A Ddma-api-howto.rst201 DMA addressing capabilities
205 addressing. For a 64-bit capable device, this needs to be increased, and for
209 64-bit addressing (DAC) for all transactions. And at least one platform (SGI
214 your devices DMA addressing capabilities.
258 The 24-bit addressing device would do something like this::
265 The standard 64-bit addressing device would do something like this::
285 If the device only supports 32-bit addressing for descriptors in the
303 dev_warn(dev, "mydev: 24-bit DMA addressing not available\n");
315 DMA addressing limitations, you may wish to probe each mask and
346 and thus retaining the 16MB DMA addressing limitations of ISA.
/linux/arch/arm64/boot/dts/ti/
H A Dk3-j7200-mcu-wakeup.dtsi231 /* Proxy 0 addressing */
240 /* Proxy 0 addressing */
249 /* Proxy 0 addressing */
258 /* Proxy 0 addressing */
H A Dk3-j721s2-mcu-wakeup.dtsi80 /* Proxy 0 addressing */
89 /* Proxy 0 addressing */
98 /* Proxy 0 addressing */
107 /* Proxy 0 addressing */
H A Dk3-j784s4-j742s2-mcu-wakeup-common.dtsi80 /* Proxy 0 addressing */
89 /* Proxy 0 addressing */
98 /* Proxy 0 addressing */
107 /* Proxy 0 addressing */
/linux/Documentation/networking/device_drivers/ethernet/google/
H A Dgve.rst57 GVE supports two addressing modes: QPL and RDA.
61 For RDA ("raw DMA addressing") mode, the set of pages is dynamic.

12345