| /linux/rust/kernel/io/ |
| H A D | resource.rs | 30 pub struct Region { struct
38 impl Deref for Region { argument
47 impl Drop for Region { implementation
67 unsafe impl Send for Region {} implementation
71 unsafe impl Sync for Region {} implementation
107 ) -> Option<Region> { in request_region() argument
123 Some(Region { in request_region()
|
| H A D | mem.rs | 16 Region,
176 _region: Region,
|
| /linux/Documentation/PCI/endpoint/ |
| H A D | pci-vntb-function.rst | 46 1) Config Region
53 Config Region:
108 BAR0 Config Region
121 BAR0 Config Region + Scratchpad
|
| H A D | pci-ntb-function.rst | 51 1) Config Region
58 Config Region:
61 Config Region is a construct that is specific to NTB implemented using NTB
63 exchange information with each other using this region. Config Region has
70 The format of Config Region is given below. All the fields here are 32 bits.
239 BAR0 Config Region
261 BAR0 Config Region + Self Scratchpad
271 Modeling Config/Scratchpad Region:
|
| /linux/Documentation/driver-api/fpga/ |
| H A D | intro.rst | 43 FPGA Region
49 The FPGA Region framework (fpga-region.c) associates managers and
53 The Device Tree FPGA Region support (of-fpga-region.c) handles
|
| /linux/drivers/fpga/ |
| H A D | Kconfig | 146 tristate "FPGA Region"
149 FPGA Region common code. An FPGA Region controls an FPGA Manager
154 tristate "FPGA Region Device Tree Overlay Support"
200 tristate "FPGA DFL FME Region Driver"
203 Say Y to enable FPGA Region driver for FPGA Management Engine.
|
| /linux/Documentation/networking/devlink/ |
| H A D | iosm.rst | 59 each having one secure bin file and at least one Loadmap/Region file. For flashing
91 b) Flashing the Loadmap/Region file
123 Region commands
|
| H A D | devlink-region.rst | 4 Devlink Region
13 Region snapshots are collected by the driver, and can be accessed via read
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-d4xx.rst | 68 - Left border of the AE Region of Interest (all ROI values are in pixels
71 - Right border of the AE Region of Interest
73 - Top border of the AE Region of Interest
75 - Bottom border of the AE Region of Interest
|
| /linux/arch/arm/mm/ |
| H A D | proc-arm740.S | 109 mcr p15, 0, r0, c2, c0 @ Region 1&2 cacheable
113 mov r0, #0x02 @ Region 1 write bufferred
|
| H A D | proc-arm940.S | 317 mcr p15, 0, r0, c2, c0, 0 @ Region 1&2 cacheable
322 mov r0, #0x02 @ Region 1 write bufferred
|
| /linux/samples/vfio-mdev/ |
| H A D | README.rst | 67 Region 0: I/O ports at c150 [size=8]
68 Region 1: I/O ports at c158 [size=8]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-edac-scrub | 55 Region-based scrub: returns the max of minimum scrub cycles
69 Region-based scrub: returns the min of maximum scrub cycles
|
| H A D | sysfs-bus-nfit | 59 in section 5.2.25.3 'NVDIMM Region Mapping' Structure of the
231 range. Used by NVDIMM Region Mapping Structure to uniquely refer
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 198 bool "CXL: Region Support"
216 bool "CXL: Region Cache Management Bypass (TEST)"
219 CXL Region management and security operations potentially invalidate
221 invalidate the affected cachelines. The CXL Region driver attempts
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | cxl-driver.rst | 402 Memory Region
404 A `Memory Region` is a logical construct that connects a set of CXL ports in
406 on these devices to the DAX subsystem via a `DAX Region`.
421 The interleave settings in a `Memory Region` describe the configuration of the
437 DAX Region
439 A `DAX Region` is used to convert a CXL `Memory Region` to a DAX device. A
587 `Memory Region` to bring this memory online with runtime programmed settings
609 set (e.g. the interleave settings defined by the associated `Memory Region`).
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | nvdimm.rst | 30 LIBNVDIMM/LIBNDCTL: Region
33 Why Not Encode the Region Type into the Region Name?
34 How Do I Determine the Major Type of a Region?
71 NVDIMM Control Region Structure defined in ACPI 6 Section 5.2.25.5.
380 LIBNVDIMM/LIBNDCTL: Region
|
| /linux/arch/arm/kernel/ |
| H A D | head-nommu.S | 272 ldr r5, =PLAT_PHYS_OFFSET @ Region start: PHYS_OFFSET
275 clz r6, r6 @ Region size must be 2^N...
322 clz r6, r6 @ Region size must be 2^N...
|
| /linux/Documentation/driver-api/cxl/platform/acpi/ |
| H A D | cedt.rst | 40 Window base address : 000000C050000000 <- Memory Region
|
| H A D | srat.rst | 38 Base Address : 000000C050000000 <- Physical Memory Region
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | xen.txt | 13 Region 0 is reserved for mapping grant table, it must be always present.
|
| /linux/Documentation/edac/ |
| H A D | scrub.rst | 294 "see Section 1.2 Region based scrubbing".
299 1.2. Region based scrubbing
311 Region-based scrubbing is used for the third use case described in
|
| /linux/Documentation/driver-api/cxl/linux/example-configurations/ |
| H A D | single-device.rst | 220 Finally we have the `Memory Region` associated with the `Root Decoder`
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | qcs8550.dtsi | 46 * | Remoteproc Region |
|
| /linux/Documentation/fpga/ |
| H A D | dfl.rst | 309 | (FPGA Base Region) | Framework
345 common interface function from FPGA Region to complete the partial
415 |Manager||Bridge||Region| |
423 | (FPGA Base Region) | | | (FPGA Base Region) |
|