Searched refs:accessed (Results 1 – 25 of 278) sorted by relevance
12345678910>>...12
| /Linux-v4.19/Documentation/blockdev/drbd/ |
| D | data-structure-v9.txt | 26 In this table, horizontally, devices can be accessed from resources by their
27 volume number. Likewise, peer_devices can be accessed from connections by
33 devices can be accessed by their minor device number via the drbd_devices idr.
|
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| 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 | 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 | 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
|
| /Linux-v4.19/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
|
| /Linux-v4.19/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.
|
| /Linux-v4.19/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()
|
| /Linux-v4.19/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
|
| D | common-properties.txt | 15 know the peripheral always needs to be accessed in BE mode.
18 peripheral always needs to be accessed in LE mode.
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-topology | 14 that has to be operated before the device can be accessed.
217 When any device is accessed, all other devices are locked out for
241 When device D1 is accessed, accesses to D2 are locked out for the
262 When device D1 is accessed, accesses to D2 and D3 are locked out
296 When D1 is accessed, accesses to D2 are locked out for the full
301 When D3 or D4 are accessed, everything else is locked out. For D3
326 When D1 is accessed, accesses to D2, D3 and D4 are locked out. But
350 When any device is accessed, accesses to all other devices are locked
374 When D1 or D2 are accessed, accesses to D3 and D4 are locked out while
375 accesses to D5 may interleave. When D3 or D4 are accessed, accesses to
|
| /Linux-v4.19/Documentation/devicetree/bindings/hwmon/ |
| D | apm-xgene-hwmon.txt | 3 APM X-Gene SOC sensors are accessed over the "SLIMpro" mailbox.
|
| /Linux-v4.19/Documentation/devicetree/bindings/i2c/ |
| D | i2c-xgene-slimpro.txt | 3 An I2C controller accessed over the "SLIMpro" mailbox.
|
| /Linux-v4.19/Documentation/scsi/ |
| D | hptiop.txt | 6 For RR44xx Intel IOP based adapters, the controller IOP is accessed via PCI BAR0 and BAR2:
25 For Intel IOP based adapters, the controller IOP is accessed via PCI BAR0:
40 For Marvell not Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
58 For Marvell Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
|
| /Linux-v4.19/arch/arc/mm/ |
| D | tlbex.S | 313 ; Get the PTE corresponding to V-addr accessed, r2 is setup with EFA
326 ; Let Linux VM know that the page was accessed
347 ; Get the PTE corresponding to V-addr accessed
375 ; UPDATE_PTE: Let Linux VM know that page was accessed/dirty
|
| /Linux-v4.19/Documentation/virtual/kvm/devices/ |
| D | arm-vgic-v3.txt | 74 __u32 value. 64-bit registers must be accessed by separately accessing the
88 differently when accessed via this interface compared to their
93 redistributor is accessed. The mpidr is ignored for the distributor.
135 and ISPENDR registers.) For a level triggered interrupt the value accessed
173 All system regs accessed through this API are (rw, 64-bit) and
180 Error -ENXIO is returned when accessed in AArch32 mode.
|
| /Linux-v4.19/drivers/firmware/google/ |
| D | Kconfig | 32 pointer is accessed through the ACPI "GOOGCB00" object.
42 is accessed through the device tree node /firmware/coreboot.
|
| /Linux-v4.19/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
|
| /Linux-v4.19/drivers/visorbus/ |
| D | Kconfig | 11 network cards that do not have SR-IOV support, and to be accessed using
|
| /Linux-v4.19/arch/openrisc/boot/dts/ |
| D | or1ksim.dts | 34 * OR1K PIC is built into CPU and accessed via special purpose
|
| D | simple_smp.dts | 46 * OR1K PIC is built into CPU and accessed via special purpose
|
| /Linux-v4.19/Documentation/dev-tools/ |
| D | kasan.rst | 122 access caused it. It's followed by the description of the accessed slub object
124 the description of the accessed memory page.
126 In the last section the report shows memory state around the accessed address.
139 the accessed address is partially accessible.
|
12345678910>>...12
