Searched refs:accessed (Results 1 – 25 of 333) sorted by relevance
12345678910>>...14
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fsi/ |
| D | ibm,p9-occ.txt | 4 This is the binding for the P9 On-Chip Controller accessed over FSI from a
6 nodes. The OCC is not an FSI slave device itself, rather it is accessed
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 30 In this table, horizontally, devices can be accessed from resources by their
31 volume number. Likewise, peer_devices can be accessed from connections by
37 devices can be accessed by their minor device number via the drbd_devices idr.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | demux.rst | 14 It can be accessed through ``/dev/adapter?/demux?``. Data types and and
15 ioctl definitions can be accessed by including ``linux/dvb/dmx.h`` in
|
| D | ca.rst | 10 can be accessed through ``/dev/dvb/adapter?/ca?``. Data types and and ioctl
11 definitions can be accessed by including ``linux/dvb/ca.h`` in your
|
| D | audio.rst | 10 TV hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data
11 types and and ioctl definitions can be accessed by including
|
| D | video.rst | 10 TV hardware. It can be accessed through **/dev/dvb/adapter0/video0**. Data
11 types and and ioctl definitions can be accessed by including
|
| D | frontend.rst | 30 The frontend can be accessed through ``/dev/dvb/adapter?/frontend?``.
31 Data types and ioctl definitions can be accessed by including
|
| /kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-file_endian.txt | 7 raw data being accessed by the tep handler.
27 being accessed by the tep handler. The _tep_ argument is trace event parser
31 accessed by the tep handler. The _tep_ argument is trace event parser context.
|
| /kernel/linux/linux-5.10/arch/alpha/lib/ |
| D | memchr.S | 120 # Make $18 point to last quad to be accessed (the
127 # At least two quads remain to be accessed.
133 # At least three quads remain to be accessed
|
| D | ev6-memchr.S | 139 # Make $18 point to last quad to be accessed (the
145 # At least two quads remain to be accessed.
150 # At least three quads remain to be accessed
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 11 accessed by a workload and which are idle. This information can be useful for
32 A page is considered idle if it has not been accessed since it was marked idle
33 (for more details on what "accessed" actually means see the :ref:`Implementation
84 considered referenced if it has been recently accessed via a process address
86 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
96 - a page is accessed by a device driver using get_user_pages()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | edac.rst | 54 The data accessed by the memory controller is contained into one dimm
62 The data size accessed by the memory controller is interlaced into two
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
70 accessed. Common chip-select rows for single channel are 64 bits, for
86 sets of memory devices. The two rows cannot be accessed concurrently.
93 of memory devices. The two rows cannot be accessed concurrently.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | resource-names.txt | 2 normally accessed by index. However, some devices will have multiple
3 values which are more naturally accessed by name. Device nodes can
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | i2c-topology.rst | 15 that has to be operated before the device can be accessed.
237 When any device is accessed, all other devices are locked out for
261 When device D1 is accessed, accesses to D2 are locked out for the
282 When device D1 is accessed, accesses to D2 and D3 are locked out
316 When D1 is accessed, accesses to D2 are locked out for the full
321 When D3 or D4 are accessed, everything else is locked out. For D3
346 When D1 is accessed, accesses to D2, D3 and D4 are locked out. But
370 When any device is accessed, accesses to all other devices are locked
394 When D1 or D2 are accessed, accesses to D3 and D4 are locked out while
395 accesses to D5 may interleave. When D3 or D4 are accessed, accesses to
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kasan.rst | 133 access, a stack trace of where the accessed memory was allocated (in case bad
136 the accessed slab object and information about the accessed memory page.
138 In the last section the report shows memory state around the accessed address.
151 the accessed address is partially accessible.
154 accessed address (see Implementation details section).
208 is being accessed is equal to tag of the pointer that is used to access this
227 that all addresses accessed by instrumented code have a valid shadow
232 could be accessed by the kernel.
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | tagged-address-abi.rst | 46 1. User addresses not accessed by the kernel but used for address space
67 2. User addresses accessed by the kernel (e.g. ``write()``). This ABI
119 indirectly as arguments to be accessed by the kernel.
122 indirectly as arguments to be accessed by the kernel.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/ |
| D | apm-xgene-hwmon.txt | 3 APM X-Gene SOC sensors are accessed over the "SLIMpro" mailbox.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-xgene-slimpro.txt | 3 An I2C controller accessed over the "SLIMpro" mailbox.
|
| /kernel/linux/linux-5.10/arch/arc/mm/ |
| D | tlbex.S | 309 ; Get the PTE corresponding to V-addr accessed, r2 is setup with EFA
322 ; Let Linux VM know that the page was accessed
343 ; Get the PTE corresponding to V-addr accessed
371 ; UPDATE_PTE: Let Linux VM know that page was accessed/dirty
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 122 This node's read bandwidth in MB/s when accessed from
129 This node's read latency in nanoseconds when accessed
136 This node's write bandwidth in MB/s when accessed from
164 The number of bytes accessed from the next cache level on a
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/devices/ |
| D | arm-vgic-v3.rst | 86 __u32 value. 64-bit registers must be accessed by separately accessing the
100 differently when accessed via this interface compared to their
105 redistributor is accessed. The mpidr is ignored for the distributor.
148 and ISPENDR registers.) For a level triggered interrupt the value accessed
192 All system regs accessed through this API are (rw, 64-bit) and
199 Error -ENXIO is returned when accessed in AArch32 mode.
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-region.rst | 11 region can then be accessed via the devlink region interface.
13 Region snapshots are collected by the driver, and can be accessed via read
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | snps,archs-intc.txt | 12 intc accessed via the special ARC AUX register interface, hence "reg" property
|
| D | snps,arc700-intc.txt | 15 intc accessed via the special ARC AUX register interface, hence "reg" property
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | hptiop.rst | 11 For RR44xx Intel IOP based adapters, the controller IOP is accessed via PCI BAR0 and BAR2
36 For Intel IOP based adapters, the controller IOP is accessed via PCI BAR0:
54 For Marvell not Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
78 For Marvell Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
|
12345678910>>...14