Searched refs:discover (Results 1 – 25 of 39) sorted by relevance
12
/Linux-v4.19/net/tipc/ |
D | Makefile | 9 core.o link.o discover.o msg.o \
|
/Linux-v4.19/drivers/visorbus/ |
D | Kconfig | 13 discover devices on an s-Par guest, and must be present for any other
|
/Linux-v4.19/drivers/block/aoe/ |
D | aoechr.c | 62 discover(void) in discover() function 171 ret = discover(); in aoechr_write()
|
/Linux-v4.19/Documentation/aoe/ |
D | aoe.txt | 51 "echo > /dev/etherd/discover" tells the driver to find out what AoE 112 interfaces. The aoetools package provides an aoe-discover script 114 /dev/etherd/discover special file described above.
|
D | udev.txt | 19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220"
|
/Linux-v4.19/Documentation/media/uapi/v4l/ |
D | vidioc-subdev-g-selection.rst | 61 To discover which targets are supported, the user can perform
|
D | vidioc-g-edid.rst | 75 copying any data. This is an easy way to discover how many EDID blocks
|
D | open.rst | 89 code exists that uses sysfs to discover related devices (see
|
D | vidioc-querycap.rst | 116 device) and discover whether video, vbi and/or radio are also
|
/Linux-v4.19/Documentation/ABI/testing/ |
D | sysfs-bus-pci-devices-cciss | 39 Description: Kicks of a rescan of the controller to discover logical
|
D | sysfs-bus-pci | 66 re-discover previously removed devices. 106 and re-discover devices removed earlier from this 115 child buses, and re-discover devices removed earlier
|
/Linux-v4.19/Documentation/networking/dpaa2/ |
D | overview.rst | 40 | (create,discover,connect 67 The MC mediates operations such as create, discover, 105 of the DPRC, discover the hardware objects present (including mappable
|
/Linux-v4.19/Documentation/cpu-freq/ |
D | pcc-cpufreq.txt | 69 The ACPI PCCH() method is used to discover the location of the PCC shared 79 used to discover the offsets for the input and output buffers in the shared
|
/Linux-v4.19/drivers/nvdimm/ |
D | Kconfig | 9 NFIT, or otherwise can discover NVDIMM resources, a libnvdimm
|
/Linux-v4.19/Documentation/powerpc/ |
D | ptrace.txt | 16 Query for GDB to discover the hardware debug features. The main info to
|
D | pci_iov_resource_on_powernv.txt | 162 discover the BAR sizes and assign addresses for them. For VF devices, 164 discover sizes and assign addresses. The BARs in the VF's config space
|
/Linux-v4.19/include/linux/ |
D | rio.h | 535 int (*discover)(struct rio_mport *mport, u32 flags); member
|
/Linux-v4.19/Documentation/filesystems/ |
D | gfs2-uevents.txt | 48 without checking the environment variables to discover the state, we
|
/Linux-v4.19/Documentation/accelerators/ |
D | ocxl.rst | 55 device. So the host can discover AFUs by querying the config space.
|
/Linux-v4.19/Documentation/PCI/ |
D | acpi-info.txt | 13 described via ACPI. The OS can discover them via the standard PCI 14 enumeration mechanism, using config accesses to discover and identify
|
/Linux-v4.19/Documentation/driver-api/ |
D | dma-buf.rst | 61 the usual size discover pattern size = SEEK_END(0); SEEK_SET(0). Every other
|
/Linux-v4.19/Documentation/input/devices/ |
D | iforce-protocol.rst | 15 This document describes what I managed to discover about the protocol used to
|
/Linux-v4.19/Documentation/scsi/ |
D | FlashPoint.txt | 82 discover that the FlashPoint was not supported and would not be for quite
|
/Linux-v4.19/drivers/rapidio/ |
D | rio.c | 2107 rc = port->nscan->discover(port, RIO_SCAN_ENUM_NO_WAIT); in rio_mport_scan() 2142 work->mport->nscan->discover(work->mport, 0); in disc_work_handler()
|
D | rio-scan.c | 1124 .discover = rio_disc_mport,
|
12