Home
last modified time | relevance | path

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

12

/drivers/staging/media/av7110/
Daudio.rst10 TV hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data
11 types and ioctl definitions can be accessed by including
Dvideo.rst10 TV hardware. It can be accessed through **/dev/dvb/adapter0/video0**. Data
11 types and ioctl definitions can be accessed by including
/drivers/net/wwan/
DKconfig34 and FIREHOSE. These protocols can be accessed directly from userspace
59 These protocols can be accessed directly from userspace
/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.
107 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/leds/
DKconfig115 LED HW controller accessed via MMIO registers.
124 LED HW controller accessed via MMIO registers.
493 LED driver chips accessed via the I2C bus. Supported
513 LED driver chip accessed via the I2C bus. Supported
576 accessed via the I2C bus.
658 LED driver chips accessed via the I2C bus.
712 fancy LED driver chips accessed via the I2C bus.
/drivers/md/
Ddm-bufio.c148 unsigned accessed; member
347 b->accessed = 1; in adjust_total_allocated()
542 b->accessed = 1; in __relink_lru()
2007 if (b->accessed) { in do_global_cleanup()
2008 b->accessed = 0; in do_global_cleanup()
/drivers/mtd/maps/
DKconfig163 which are accessed as separate MTD devices.
179 By default the flash is split into 3 partitions which are accessed
299 This provides a driver for the flash accessed using Intel's
/drivers/gpu/drm/
Ddrm_gem.c593 bool dirty, bool accessed) in drm_gem_put_pages() argument
618 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/
DKconfig71 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/
DKconfig189 macvtap', and then be accessed through the tap user space interface.
227 ipvtap', and then be accessed through the tap user space interface.
533 Xen domains. These devices can be accessed by any operating
/drivers/iio/pressure/
DKconfig74 It can be accessed over I2C bus.
/drivers/net/mdio/
DKconfig129 to I2C to allow PHYs connected in I2C mode to be accessed
/drivers/bus/
DKconfig54 accessed via corresponding sysfs nodes.
/drivers/memory/
DKconfig89 of 256M bytes of any of these memories can be accessed at a given

12