Home
last modified time | relevance | path

Searched full:physical (Results 1 – 25 of 6337) sorted by relevance

12345678910>>...254

/kernel/linux/linux-6.6/Documentation/userspace-api/media/cec/
Dcec-ioc-adap-g-phys-addr.rst15 CEC_ADAP_G_PHYS_ADDR, CEC_ADAP_S_PHYS_ADDR - Get or set the physical address
40 To query the current physical address applications call
42 driver stores the physical address.
44 To set a new physical address applications store the physical address in
52 To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.
60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
63 The physical address is a 16-bit number where each group of 4 bits
64 represent a digit of the physical address a.b.c.d where the most
69 is supported. The physical address a device shall use is stored in the
73 different physical address of the form a.0.0.0 that the sources will
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/cec/
Dcec-ioc-adap-g-phys-addr.rst15 CEC_ADAP_G_PHYS_ADDR, CEC_ADAP_S_PHYS_ADDR - Get or set the physical address
40 To query the current physical address applications call
42 driver stores the physical address.
44 To set a new physical address applications store the physical address in
52 To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.
60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
63 The physical address is a 16-bit number where each group of 4 bits
64 represent a digit of the physical address a.b.c.d where the most
69 is supported. The physical address a device shall use is stored in the
73 different physical address of the form a.0.0.0 that the sources will
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/
Dconcepts.rst12 address to a physical address.
19 The physical memory in a computer system is a limited resource and
21 the amount of memory that can be installed. The physical memory is not
27 All this makes dealing directly with physical memory quite complex and
30 The virtual memory abstracts the details of physical memory from the
32 physical memory (demand paging) and provides a mechanism for the
38 address encoded in that instruction to a `physical` address that the
41 The physical system memory is divided into page frames, or pages. The
47 Each physical memory page can be mapped as one or more virtual
49 translation from a virtual address used by programs to the physical
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dconcepts.rst14 address to a physical address.
21 The physical memory in a computer system is a limited resource and
23 the amount of memory that can be installed. The physical memory is not
29 All this makes dealing directly with physical memory quite complex and
32 The virtual memory abstracts the details of physical memory from the
34 physical memory (demand paging) and provides a mechanism for the
40 address encoded in that instruction to a `physical` address that the
43 The physical system memory is divided into page frames, or pages. The
49 Each physical memory page can be mapped as one or more virtual
51 translation from a virtual address used by programs to the physical
[all …]
/kernel/linux/linux-5.10/Documentation/vm/
Dmemory-model.rst6 Physical Memory Model
9 Physical memory in a system may be addressed in different ways. The
10 simplest case is when the physical memory starts at address 0 and
26 All the memory models track the status of physical page frames using
30 mapping between the physical page frame number (PFN) and the
41 non-NUMA systems with contiguous, or mostly contiguous, physical
45 maps the entire physical memory. For most architectures, the holes
55 actual physical pages. In such case, the architecture specific
64 systems with physical memory starting at address different from 0.
69 The DISCONTIGMEM model treats the physical memory as a collection of
[all …]
/kernel/linux/linux-6.6/include/linux/
Dpsp-sev.h88 * @tmr_address: system physical address used for SEV-ES
103 * @tmr_address: system physical address used for SEV-ES
105 * @nv_address: system physical address used for PSP NV storage
150 * @address: physical address of firmware image
161 * @address: physical address of region to place unique CPU ID(s)
233 * @dh_cert_address: physical address of DH certificate blob
235 * @session_address: physical address of session parameters
253 * @address: physical address of memory region to encrypt
266 * @address: physical address of memory region to encrypt
280 * @address: physical address containing the measurement blob
[all …]
/kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dcounters.rst78 Physical port counters
82 additional counters like flow control, FEC and more. Physical port counters
86 A set of the physical port counters, per priority per port.
469 software counters. These packets are counted by physical port and vPort
491 physical port and vPort counters. You may open more rx queues and spread
507 counted by physical port and vPort counters.
517 are counted by physical port and vPort counters.
856 Physical Port Counters
858 The physical port counters are the counters on the external port connecting the
863 .. flat-table:: Physical Port Counter Table
[all …]
/kernel/linux/linux-6.6/Documentation/i2c/
Di2c-sysfs.rst13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
16 the concept of logical I2C buses in the kernel, by knowing the physical I2C
41 start with ``i2c-`` are I2C buses, which may be either physical or logical. The
59 (Physical) I2C Bus Controller
63 physical I2C bus controllers. The controllers are hardware and physical, and the
70 I2C Bus Physical Number
73 For each physical I2C bus controller, the system vendor may assign a physical
82 written upon virtual memory space, instead of physical memory space.
84 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
90 Physical I2C Bus
[all …]
/kernel/linux/linux-6.6/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_encoder_phys.h29 * enum dpu_enc_split_role - Role this physical encoder will play in a
43 * enum dpu_enc_enable_state - current enabled state of the physical encoder
64 * struct dpu_encoder_phys_ops - Interface the physical encoders provide to
85 * @trigger_start: Process start event on physical encoder
144 * struct dpu_encoder_phys - physical encoder that drives a single INTF block
163 * @vsync_cnt: Vsync count for the physical encoder
164 * @underrun_cnt: Underrun count for the physical encoder
208 * @base: Baseclass physical encoder structure
229 * @base: Baseclass physical encoder structure
279 * dpu_encoder_phys_vid_init - Construct a new video mode physical encoder
[all …]
/kernel/linux/linux-6.6/Documentation/mm/
Dmemory-model.rst4 Physical Memory Model
7 Physical memory in a system may be addressed in different ways. The
8 simplest case is when the physical memory starts at address 0 and
20 All the memory models track the status of physical page frames using
24 mapping between the physical page frame number (PFN) and the
35 non-NUMA systems with contiguous, or mostly contiguous, physical
39 maps the entire physical memory. For most architectures, the holes
49 actual physical pages. In such case, the architecture specific
58 systems with physical memory starting at address different from 0.
65 as hot-plug and hot-remove of the physical memory, alternative memory
[all …]
/kernel/linux/linux-5.10/include/linux/
Dpsp-sev.h93 * @tmr_address: system physical address used for SEV-ES
135 * @address: physical address of firmware image
146 * @address: physical address of region to place unique CPU ID(s)
218 * @dh_cert_address: physical address of DH certificate blob
220 * @session_address: physical address of session parameters
238 * @address: physical address of memory region to encrypt
251 * @address: physical address of memory region to encrypt
265 * @address: physical address containing the measurement blob
279 * @hdr_address: physical address containing the packet header
281 * @guest_address: system physical address of guest memory region
[all …]
/kernel/linux/linux-6.6/include/linux/firmware/intel/
Dstratix10-smc.h24 * EL1 and EL3 communicates pointer as physical address rather than the
106 * a1: 64bit physical address of the configuration data memory block
113 * a1: 64bit physical address of 1st completed memory block if any completed
115 * a2: 64bit physical address of 2nd completed memory block if any completed
117 * a3: 64bit physical address of 3rd completed memory block if any completed
138 * a1: 64bit physical address of 1st completed memory block.
139 * a2: 64bit physical address of 2nd completed memory block if
141 * a3: 64bit physical address of 3rd completed memory block if
171 * Sync call used by service driver at EL1 to query the physical address of
180 * a1: start of physical address of reserved memory block.
[all …]
/kernel/linux/linux-5.10/drivers/mtd/ubi/
Dubi-media.h57 * initialization UBI finds out that there are available physical eraseblocks
59 * (the physical eraseblocks reserved for bad eraseblocks handling and other
60 * reserved physical eraseblocks are not taken). So, if there is a volume with
72 * of good physical eraseblocks the NAND chip on the device will have, but this
78 * Note, first UBI reserves some amount of physical eraseblocks for bad
80 * means that the pool of reserved physical eraseblocks will always be present.
94 * physical eraseblocks, don't allow the wear-leveling
136 * physical eraseblock. These values have to be the same for all physical
165 * @copy_flag: if this logical eraseblock was copied from another physical
174 * @data_pad: how many bytes at the end of this physical eraseblock are not
[all …]
Dio.c92 * ubi_io_read - read data from a physical eraseblock.
95 * @pnum: physical eraseblock number to read from
96 * @offset: offset within the physical eraseblock from where to read
99 * This function reads data from offset @offset of physical eraseblock @pnum
206 * ubi_io_write - write data to a physical eraseblock.
209 * @pnum: physical eraseblock number to write to
210 * @offset: offset within the physical eraseblock where to write
214 * of physical eraseblock @pnum. If all the data were successfully written,
216 * error code. If %-EIO is returned, the physical eraseblock most probably went
252 * We write to the data area of the physical eraseblock. Make in ubi_io_write()
[all …]
Dwl.c12 * physical eraseblocks and erase counters and knows nothing about logical
13 * eraseblocks, volumes, etc. From this sub-system's perspective all physical
14 * eraseblocks are of two types - used and free. Used physical eraseblocks are
15 * those that were "get" by the 'ubi_wl_get_peb()' function, and free physical
18 * Physical eraseblocks returned by 'ubi_wl_get_peb()' have only erase counter
19 * header. The rest of the physical eraseblock contains only %0xFF bytes.
21 * When physical eraseblocks are returned to the WL sub-system by means of the
27 * physical eraseblocks with low erase counter to free physical eraseblocks
30 * If the WL sub-system fails to erase a physical eraseblock, it marks it as
34 * in a physical eraseblock, it has to be moved. Technically this is the same
[all …]
/kernel/linux/linux-6.6/drivers/mtd/ubi/
Dubi-media.h57 * initialization UBI finds out that there are available physical eraseblocks
59 * (the physical eraseblocks reserved for bad eraseblocks handling and other
60 * reserved physical eraseblocks are not taken). So, if there is a volume with
72 * of good physical eraseblocks the NAND chip on the device will have, but this
78 * Note, first UBI reserves some amount of physical eraseblocks for bad
80 * means that the pool of reserved physical eraseblocks will always be present.
94 * physical eraseblocks, don't allow the wear-leveling
136 * physical eraseblock. These values have to be the same for all physical
165 * @copy_flag: if this logical eraseblock was copied from another physical
174 * @data_pad: how many bytes at the end of this physical eraseblock are not
[all …]
Dio.c92 * ubi_io_read - read data from a physical eraseblock.
95 * @pnum: physical eraseblock number to read from
96 * @offset: offset within the physical eraseblock from where to read
99 * This function reads data from offset @offset of physical eraseblock @pnum
206 * ubi_io_write - write data to a physical eraseblock.
209 * @pnum: physical eraseblock number to write to
210 * @offset: offset within the physical eraseblock where to write
214 * of physical eraseblock @pnum. If all the data were successfully written,
216 * error code. If %-EIO is returned, the physical eraseblock most probably went
252 * We write to the data area of the physical eraseblock. Make in ubi_io_write()
[all …]
Dwl.c12 * physical eraseblocks and erase counters and knows nothing about logical
13 * eraseblocks, volumes, etc. From this sub-system's perspective all physical
14 * eraseblocks are of two types - used and free. Used physical eraseblocks are
15 * those that were "get" by the 'ubi_wl_get_peb()' function, and free physical
18 * Physical eraseblocks returned by 'ubi_wl_get_peb()' have only erase counter
19 * header. The rest of the physical eraseblock contains only %0xFF bytes.
21 * When physical eraseblocks are returned to the WL sub-system by means of the
27 * physical eraseblocks with low erase counter to free physical eraseblocks
30 * If the WL sub-system fails to erase a physical eraseblock, it marks it as
34 * in a physical eraseblock, it has to be moved. Technically this is the same
[all …]
/kernel/linux/linux-6.6/include/xen/interface/hvm/
Dstart_info.h12 * NOTE: nothing will be loaded at physical address 0, so a 0 value in any
26 * | modlist_paddr | Physical address of an array of modules
29 * | cmdline_paddr | Physical address of the command line,
32 * | rsdp_paddr | Physical address of the RSDP ACPI data structure.
34 * | memmap_paddr | Physical address of the (optional) memory map. Only
47 * | paddr | Physical address of the module.
51 * | cmdline_paddr | Physical address of the command line,
114 uint64_t modlist_paddr; /* Physical address of an array of */
116 uint64_t cmdline_paddr; /* Physical address of the command line. */
117 uint64_t rsdp_paddr; /* Physical address of the RSDP ACPI data */
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_encoder_phys.h26 * enum dpu_enc_split_role - Role this physical encoder will play in a
40 * enum dpu_enc_enable_state - current enabled state of the physical encoder
62 * provides for the physical encoders to use to callback.
80 * struct dpu_encoder_phys_ops - Interface the physical encoders provide to
106 * @trigger_start: Process start event on physical encoder
184 * struct dpu_encoder_phys - physical encoder that drives a single INTF block
204 * @vsync_cnt: Vsync count for the physical encoder
205 * @underrun_cnt: Underrun count for the physical encoder
249 * @base: Baseclass physical encoder structure
298 * dpu_encoder_phys_vid_init - Construct a new video mode physical encoder
[all …]
/kernel/linux/linux-6.6/include/net/caif/
Dcfcnfg.h17 * enum cfcnfg_phy_preference - Physical preference HW Abstraction
19 * @CFPHYPREF_UNSPECIFIED: Default physical interface
21 * @CFPHYPREF_LOW_LAT: Default physical interface for low-latency
23 * @CFPHYPREF_HIGH_BW: Default physical interface for high-bandwidth
54 * cfcnfg_add_phy_layer() - Adds a physical layer to the CAIF stack.
58 * @phy_layer: Specify the physical layer. The transmit function
82 * cfcnfg_set_phy_state() - Set the state of the physical interface device.
84 * @phy_layer: Physical Layer representation
/kernel/linux/linux-5.10/include/net/caif/
Dcfcnfg.h17 * enum cfcnfg_phy_preference - Physical preference HW Abstraction
19 * @CFPHYPREF_UNSPECIFIED: Default physical interface
21 * @CFPHYPREF_LOW_LAT: Default physical interface for low-latency
23 * @CFPHYPREF_HIGH_BW: Default physical interface for high-bandwidth
54 * cfcnfg_add_phy_layer() - Adds a physical layer to the CAIF stack.
58 * @phy_layer: Specify the physical layer. The transmit function
82 * cfcnfg_set_phy_state() - Set the state of the physical interface device.
84 * @phy_layer: Physical Layer representation
/kernel/linux/linux-5.10/Documentation/core-api/
Dbus-virt-phys-mapping.rst21 controller the physical address of the buffers, which is correct on x86
22 (because all bus master devices see the physical memory mappings directly).
31 - CPU untranslated. This is the "physical" address. Physical address
45 Now, on normal PCs the bus address is exactly the same as the physical
58 the viewpoint of the devices, you have the reverse, and the physical memory
61 So when the CPU wants any bus master to write to physical memory 0, it
67 physical address: 0
76 physical address: 0
80 (but there are also Alphas where the physical address and the bus address
125 And you generally **never** want to use the physical address, because you can't
[all …]
/kernel/linux/linux-5.10/include/xen/interface/hvm/
Dstart_info.h29 * NOTE: nothing will be loaded at physical address 0, so a 0 value in any
43 * | modlist_paddr | Physical address of an array of modules
46 * | cmdline_paddr | Physical address of the command line,
49 * | rsdp_paddr | Physical address of the RSDP ACPI data structure.
51 * | memmap_paddr | Physical address of the (optional) memory map. Only
64 * | paddr | Physical address of the module.
68 * | cmdline_paddr | Physical address of the command line,
131 uint64_t modlist_paddr; /* Physical address of an array of */
133 uint64_t cmdline_paddr; /* Physical address of the command line. */
134 uint64_t rsdp_paddr; /* Physical address of the RSDP ACPI data */
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/include/aarch64/
Darch_timer.h13 PHYSICAL, enumerator
41 case PHYSICAL: in timer_get_cntct()
57 case PHYSICAL: in timer_set_cval()
72 case PHYSICAL: in timer_get_cval()
88 case PHYSICAL: in timer_set_tval()
104 case PHYSICAL: in timer_set_ctl()
119 case PHYSICAL: in timer_get_ctl()

12345678910>>...254