Home
last modified time | relevance | path

Searched refs:accessed (Results 1 – 25 of 38) sorted by relevance

12

/drivers/block/rnbd/
DREADME11 transport. After being mapped, the remote block devices can be accessed
77 sector to be accessed, read-write flags and bi_size.
/drivers/visorbus/
DKconfig12 network cards that do not have SR-IOV support, and to be accessed using
/drivers/tty/hvc/
DKconfig22 which is accessed via the HMC.
128 from Linux partitions to be accessed through TTY device
/drivers/gpu/vga/
DKconfig9 are accessed at same time they need some kind of coordination. Please
/drivers/mtd/chips/
DKconfig167 erased. Each Protection Register can be accessed multiple times to
215 This option enables basic support for RAM chips accessed through
221 This option enables basic support for ROM chips accessed through
/drivers/soc/bcm/
DKconfig14 must be accessed using the RASPBERRYPI_POWER driver
/drivers/net/wireless/ath/wil6210/
DKconfig30 self-clear when accessed for debug purposes, it makes
/drivers/firmware/google/
DKconfig28 pointer is accessed through the ACPI "GOOGCB00" object or the
/drivers/infiniband/ulp/rtrs/
DREADME45 which of the memory chunks has been accessed and at which offset the message
126 been accessed and at what offset the RTRS_MSG_RDMA_WRITE can be found by
143 been accessed and at what offset the RTRS_MSG_RDMA_WRITE can be found by
/drivers/md/
Ddm-bufio.c146 unsigned accessed; member
345 b->accessed = 1; in adjust_total_allocated()
540 b->accessed = 1; in __relink_lru()
1967 if (b->accessed) { in do_global_cleanup()
1968 b->accessed = 0; in do_global_cleanup()
/drivers/leds/
DKconfig134 LED HW controller accessed via MMIO registers.
143 LED HW controller accessed via MMIO registers.
521 LED driver chips accessed via the I2C bus. Supported
541 LED driver chip accessed via the I2C bus. Supported
604 accessed via the I2C bus.
687 LED driver chips accessed via the I2C bus.
762 fancy LED driver chips accessed via the I2C bus.
/drivers/mtd/maps/
DKconfig186 which are accessed as separate MTD devices.
202 By default the flash is split into 3 partitions which are accessed
322 This provides a driver for the flash accessed using Intel's
/drivers/gpu/drm/
Ddrm_gem.c609 bool dirty, bool accessed) in drm_gem_put_pages() argument
634 if (accessed) in drm_gem_put_pages()
/drivers/staging/axis-fifo/
Daxis-fifo.txt4 be accessed from the AXI4 memory-mapped interface. This is useful for
/drivers/nvdimm/
DKconfig103 accessed via DAX (mmap(2)).
/drivers/misc/eeprom/
DKconfig70 All other features of this chip should be accessed via i2c-dev.
/drivers/char/ipmi/
DKconfig75 have a driver that must be accessed over an I2C bus instead of a
/drivers/net/
DKconfig188 macvtap', and then be accessed through the tap user space interface.
226 ipvtap', and then be accessed through the tap user space interface.
522 Xen domains. These devices can be accessed by any operating
/drivers/iio/pressure/
DKconfig74 It can be accessed over I2C bus.
/drivers/net/mdio/
DKconfig115 to I2C to allow PHYs connected in I2C mode to be accessed
/drivers/memory/
DKconfig89 of 256M bytes of any of these memories can be accessed at a given
/drivers/clocksource/
DKconfig288 This counter is accessed via couple of 32-bit memory-mapped registers.
664 is accessed via both the SBI and the rdcycle instruction. This is
/drivers/bus/
DKconfig54 accessed via corresponding sysfs nodes.
/drivers/iio/accel/
DKconfig274 It can be accessed using an (optional) SPI or I2C interface.
/drivers/gpu/drm/panel/
DKconfig333 AMOLED LCD panel. This panel can be accessed using SPI or

12