| /kernel/linux/linux-4.19/Documentation/media/uapi/cec/ |
| D | cec-ioc-adap-g-phys-addr.rst | 14 CEC_ADAP_G_PHYS_ADDR, CEC_ADAP_S_PHYS_ADDR - Get or set the physical address
38 To query the current physical address applications call
40 driver stores the physical address.
42 To set a new physical address applications store the physical address in
50 To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.
58 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
61 The physical address is a 16-bit number where each group of 4 bits
62 represent a digit of the physical address a.b.c.d where the most
67 is supported. The physical address a device shall use is stored in the
71 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/ |
| D | cec-ioc-adap-g-phys-addr.rst | 15 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/admin-guide/mm/ |
| D | concepts.rst | 14 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-4.19/Documentation/admin-guide/mm/ |
| D | concepts.rst | 14 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
52 the physical memory. The page tables organized hierarchically.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | memory-model.rst | 6 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
56 actual physical pages. In such case, the architecture specific
65 systems with physical memory starting at address different from 0.
70 The DISCONTIGMEM model treats the physical memory as a collection of
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | psp-sev.h | 97 * @tmr_address: system physical address used for SEV-ES
137 * @address: physical address of firmware image
148 * @address: physical address of region to place unique CPU ID(s)
220 * @dh_cert_address: physical address of DH certificate blob
222 * @session_address: physical address of session parameters
240 * @address: physical address of memory region to encrypt
253 * @address: physical address of memory region to encrypt
267 * @address: physical address containing the measurement blob
281 * @hdr_address: physical address containing the packet header
283 * @guest_address: system physical address of guest memory region
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | psp-sev.h | 93 * @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-4.19/Documentation/blockdev/ |
| D | README.DAC960 | 300 available) for each physical device found connected to the controller:
312 Physical Devices:
339 drives are offline or critical or any non-standby physical drives are dead.
365 The "kill" command marks the physical drive <channel>:<target-id> as DEAD.
371 The "make-online" command changes the physical drive <channel>:<target-id>
372 from status DEAD to status ONLINE. In cases where multiple physical drives
377 Warning: make-online should only be used on a dead physical drive that is
384 The "make-standby" command changes physical drive <channel>:<target-id>
393 The "rebuild" command initiates an asynchronous rebuild onto physical drive
416 DAC960PJ controller. The physical drives are configured into a single drive
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/ubi/ |
| D | ubi-media.h | 57 * 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 …]
|
| D | io.c | 92 * 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 …]
|
| D | wl.c | 12 * 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-4.19/drivers/mtd/ubi/ |
| D | ubi-media.h | 57 * 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 …]
|
| D | wl.c | 25 * physical eraseblocks and erase counters and knows nothing about logical
26 * eraseblocks, volumes, etc. From this sub-system's perspective all physical
27 * eraseblocks are of two types - used and free. Used physical eraseblocks are
28 * those that were "get" by the 'ubi_wl_get_peb()' function, and free physical
31 * Physical eraseblocks returned by 'ubi_wl_get_peb()' have only erase counter
32 * header. The rest of the physical eraseblock contains only %0xFF bytes.
34 * When physical eraseblocks are returned to the WL sub-system by means of the
40 * physical eraseblocks with low erase counter to free physical eraseblocks
43 * If the WL sub-system fails to erase a physical eraseblock, it marks it as
47 * in a physical eraseblock, it has to be moved. Technically this is the same
[all …]
|
| D | io.c | 105 * ubi_io_read - read data from a physical eraseblock.
108 * @pnum: physical eraseblock number to read from
109 * @offset: offset within the physical eraseblock from where to read
112 * This function reads data from offset @offset of physical eraseblock @pnum
219 * ubi_io_write - write data to a physical eraseblock.
222 * @pnum: physical eraseblock number to write to
223 * @offset: offset within the physical eraseblock where to write
227 * of physical eraseblock @pnum. If all the data were successfully written,
229 * error code. If %-EIO is returned, the physical eraseblock most probably went
265 * We write to the data area of the physical eraseblock. Make in ubi_io_write()
[all …]
|
| /kernel/linux/linux-4.19/include/xen/interface/hvm/ |
| D | start_info.h | 29 * 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.
55 * | paddr | Physical address of the module.
59 * | cmdline_paddr | Physical address of the command line,
84 uint64_t modlist_paddr; /* Physical address of an array of */
86 uint64_t cmdline_paddr; /* Physical address of the command line. */
87 uint64_t rsdp_paddr; /* Physical address of the RSDP ACPI data */
92 uint64_t paddr; /* Physical address of the module. */
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_encoder_phys.h | 26 * 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-4.19/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_encoder_phys.h | 35 * enum dpu_enc_split_role - Role this physical encoder will play in a
49 * enum dpu_enc_enable_state - current enabled state of the physical encoder
71 * provides for the physical encoders to use to callback.
89 * struct dpu_encoder_phys_ops - Interface the physical encoders provide to
115 * @trigger_start: Process start event on physical encoder
204 * struct dpu_encoder_phys - physical encoder that drives a single INTF block
226 * @vsync_cnt: Vsync count for the physical encoder
227 * @underrun_cnt: Underrun count for the physical encoder
273 * @base: Baseclass physical encoder structure
286 * @base: Baseclass physical encoder structure
[all …]
|
| /kernel/linux/linux-4.19/include/net/caif/ |
| D | cfcnfg.h | 17 * 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/ |
| D | cfcnfg.h | 17 * 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/ |
| D | bus-virt-phys-mapping.rst | 21 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 …]
|
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
11 a "Physical Response Unit" which executes specific requests by employing
16 physical system memory and, for read requests, send the result of
17 the physical memory read back to the requester.
26 of physical address space. This can be a problem on IA64 machines where
31 physical addresses above 4 GB, but this feature is currently not enabled by
43 The firewire-ohci driver in drivers/firewire uses filtered physical
45 Pass the remote_dma=1 parameter to the driver to get unfiltered physical DMA.
81 disable all physical DMA on each bus reset.
107 controller implements a writable Physical Upper Bound register. This is
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | bus-virt-phys-mapping.txt | 21 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 …]
|
| D | debugging-via-ohci1394.txt | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
11 a "Physical Response Unit" which executes specific requests by employing
16 physical system memory and, for read requests, send the result of
17 the physical memory read back to the requester.
26 of physical address space. This can be a problem on IA64 machines where
31 physical addresses above 4 GB, but this feature is currently not enabled by
43 The firewire-ohci driver in drivers/firewire uses filtered physical
45 Pass the remote_dma=1 parameter to the driver to get unfiltered physical DMA.
81 disable all physical DMA on each bus reset.
107 controller implements a writable Physical Upper Bound register. This is
[all …]
|
| /kernel/linux/linux-5.10/include/xen/interface/hvm/ |
| D | start_info.h | 29 * 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-4.19/Documentation/arm/ |
| D | Porting | 8 virtual address to a physical address. Normally, it is simply:
18 virtual or physical addresses here, since the MMU will be off at
39 Physical address to place the initial RAM disk. Only relevant if
50 Physical address of the struct param_struct or tag list, giving the
58 Physical start address of the first bank of RAM.
62 boot phase, virtual address PAGE_OFFSET will be mapped to physical
110 `pram' specifies the physical start address of RAM. Must always
113 `pio' is the physical address of an 8MB region containing IO for
|