Searched full:backend (Results 1 – 25 of 74) sorted by relevance
123
| /Documentation/ABI/stable/ |
| D | sysfs-bus-xen-backend | 1 What: /sys/bus/xen-backend/devices/*/devtype
9 What: /sys/bus/xen-backend/devices/*/nodename
15 backend device.
17 What: /sys/bus/xen-backend/devices/vbd-*/physical_device
23 physical device providing the storage for this backend
26 What: /sys/bus/xen-backend/devices/vbd-*/mode
34 What: /sys/bus/xen-backend/devices/vbd-*/statistics/f_req
41 What: /sys/bus/xen-backend/devices/vbd-*/statistics/oo_req
46 Number of requests delayed because the backend was too
49 What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_req
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-display-backend.yaml | 4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-backend.yaml#
7 title: Allwinner A10 Display Engine Backend
14 The display engine backend exposes layers and sprites to the system.
19 - allwinner,sun4i-a10-display-backend
20 - allwinner,sun5i-a13-display-backend
21 - allwinner,sun6i-a31-display-backend
22 - allwinner,sun7i-a20-display-backend
23 - allwinner,sun8i-a23-display-backend
24 - allwinner,sun8i-a33-display-backend
25 - allwinner,sun9i-a80-display-backend
[all …]
|
| D | allwinner,sun4i-a10-display-engine.yaml | 15 either directly the backend or the frontend) is represented as an
27 Frontend 0 [0] ------- [0] Backend 0 [0] ------- [0] TCON 0
33 Frontend 1 [1] ------- [1] Backend 1 [1] ------- [1] TCON 1
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | sigma-delta-modulator.yaml | 21 '#io-backend-cells':
31 vref-supply: [ '#io-backend-cells' ]
37 - required: ['#io-backend-cells']
44 // Backend binding example. SD modulator configured as an IIO backend device
48 #io-backend-cells = <0>;
|
| D | adi,axi-adc.yaml | 47 '#io-backend-cells':
66 #io-backend-cells = <0>;
|
| /Documentation/i2c/ |
| D | slave-interface.rst | 9 a hardware independent software backend providing the actual functionality. An
13 needed. The backend driver and the I2C bus driver communicate via events. Here
15 transported. The dotted line marks only one example. The backend could also
21 | Userspace +........+ Backend +-----------+ Driver +-----+ Controller |
27 Note: Technically, there is also the I2C core between the backend and the
43 Each backend should come with separate documentation to describe its specific
50 First, the events which are used by the bus driver and the backend will be
58 The bus driver sends an event to the backend using the following function::
66 is the return value from the backend. Mandatory events must be provided by the
67 bus drivers and must be checked for by backend drivers.
[all …]
|
| D | slave-eeprom-backend.rst | 2 Linux I2C slave EEPROM backend
7 This backend simulates an EEPROM on the connected I2C bus. Its memory contents
|
| D | index.rst | 51 slave-eeprom-backend
52 slave-testunit-backend
|
| /Documentation/filesystems/caching/ |
| D | backend-api.rst | 4 Cache Backend API
34 The cache backend and the network filesystem can both ask for cache cookies -
52 There are a few fields that the cache backend might be interested in. The
62 When a cache backend wants to bring a cache online, it should first register
73 If successful, the cache backend can then start setting up the cache. In the
74 event that the initialisation fails, the cache backend should call::
98 The cache backend can withdraw a cache from service by calling this function::
112 for withdrawal. This gets offloaded to a workqueue. The cache backend can
117 Once all the cookies are withdrawn, a cache backend can withdraw all the
150 There are a number of fields here that are of interest to the caching backend:
[all …]
|
| D | index.rst | 11 backend-api
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-xen-blkfront | 7 with the backend for indirect descriptors. The default value
9 memory usage. The backend picks the minimum of the frontend
10 and its default backend value.
|
| D | pstore | 44 Pstore only supports one backend at a time. If multiple
45 backends are available, the preferred backend may be
46 set by passing the pstore.backend= argument to the kernel at
|
| D | debugfs-iio-backend | 5 Name of Backend Y connected to device X.
11 Directly access the registers of backend Y. Typical usage is:
|
| D | debugfs-scmi-raw | 8 backend SCMI server for instance <n>.
23 backend SCMI server for instance <n>.
50 emitted by the backend SCMI server, for instance <n>, can be
75 backend SCMI server for instance <n> through the <m> transport
99 backend SCMI server for instance <n> through the <m> transport
|
| D | sysfs-devices-xenbus | 6 paravirtualized device frontend or backend.
13 frontend or backend.
|
| D | debugfs-iio-ad9467 | 38 where an IIO backend is available and supports the test tone,
|
| D | sysfs-driver-xen-blkback | 7 backend buffer.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | xen,grant-dma.yaml | 15 property, which also specifies the ID of the backend domain.
25 The single cell is the domid (domain ID) of the domain where the backend
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6usb.yaml | 7 title: Qualcomm ASoC DPCM USB backend DAI
14 backend DAI will communicate the required settings to initialize the
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | adi,axi-dac.yaml | 41 '#io-backend-cells':
59 #io-backend-cells = <0>;
|
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,ethdr.yaml | 20 one video backend and a mixer. ETHDR has two DMA function blocks, DS and ADL.
59 - description: video backend clock
65 - description: video backend async clock
93 - description: video backend async reset
|
| /Documentation/gpu/ |
| D | xen-front.rst | 21 Buffers allocated by the backend
25 :doc: Buffers allocated by the backend
|
| /Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 33 * GuC submission backend fully integrated with DRM scheduler
34 * All request queues removed from backend (e.g. all backpressure
38 * Lots of complexity of the GuC backend can be pulled out once
41 * Execlists backend will minimum required to hook in the DRM scheduler
|
| D | i915_gem_lmem.rst | 18 * Route shmem backend over to TTM SYSTEM for discrete
|
| /Documentation/power/powercap/ |
| D | dtpm.rst | 33 powercap entries in the sysfs directory and implement the backend
164 The DTPM framework has no power limiting backend support. It is
166 implement the backend part for the power limitation and create the
|
123