Searched full:descriptor (Results 1 – 25 of 491) sorted by relevance
12345678910>>...20
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 14 descriptor pointers each channel fetch fifo can hold.
17 should be encoded following the SEC's Descriptor Header Dword
33 - fsl,descriptor-types-mask : The bitmask representing what descriptors
34 are available. It's a single 32-bit cell. Descriptor type information
35 should be encoded following the SEC's Descriptor Header Dword DESC_TYPE
39 bit 1 = set if SEC supports the ipsec_esp descriptor type
43 bit 5 = set if SEC supports the srtp descriptor type
45 bit 7 = set if SEC supports the pkeu_assemble descriptor type
47 bit 9 = set if SEC supports the pkeu_ptmul descriptor type
49 bit 11 = set if SEC supports the pkeu_ptadd_dbl descriptor type
[all …]
|
| /Documentation/usb/ |
| D | functionfs-desc.rst | 11 following the descriptor header.
20 most recent interface descriptor determines what type of class-specific
27 most recent interface descriptor. The following are some of the
30 DFU Functional Descriptor
34 is USB_SUBCLASS_DFU, a DFU functional descriptor can be provided.
35 The DFU functional descriptor is a described in the USB specification for
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 20 device descriptor parameters. The full information about
21 the descriptor could be found at UFS specifications 2.1.
30 device descriptor parameters. The full information about
31 the descriptor could be found at UFS specifications 2.1.
40 the UFS device descriptor parameters. The full information
41 about the descriptor could be found at UFS specifications 2.1.
50 This is one of the UFS device descriptor parameters.
51 The full information about the descriptor could be found
61 the UFS device descriptor parameters. The full information
62 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 32 presented in the USB device descriptor by this xhci debug
35 disabled state to prevent USB device descriptor change while
45 presented in the USB device descriptor by this xhci debug
48 disabled state to prevent USB device descriptor change while
57 presented in the USB device descriptor by this xhci debug
60 disabled state to prevent USB device descriptor change while
70 presented in the USB Interface descriptor by the xhci debug
73 disabled state to prevent USB descriptor change while
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-master-gpio.txt | 6 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock
7 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal
10 - enable-gpios = <gpio-descriptor>; : GPIO for enable signal
11 - trans-gpios = <gpio-descriptor>; : GPIO for voltage translator enable
12 - mux-gpios = <gpio-descriptor>; : GPIO for pin multiplexing with other
|
| D | fsi-master-ast-cf.txt | 10 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock
11 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal
12 - enable-gpios = <gpio-descriptor>; : GPIO for enable signal
13 - trans-gpios = <gpio-descriptor>; : GPIO for voltage translator enable
14 - mux-gpios = <gpio-descriptor>; : GPIO for pin multiplexing with other
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 23 - Get a descriptor for transaction
76 3. Get a descriptor for transaction
97 A non-NULL return of this transfer API represents a "descriptor" for
140 Once a descriptor has been obtained, the callback information can be
141 added and the descriptor must then be submitted. Some DMA engine
167 **Optional: per descriptor metadata**
174 attached to the descriptor.
189 after their transfer completion callback has run for the descriptor.
216 1. prepare the descriptor (dmaengine_prep_*)
219 descriptor
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | vfio.rst | 27 kvm_device_attr.addr points to an int32_t file descriptor for the
33 kvm_device_attr.addr points to an int32_t file descriptor for the
52 - @groupfd is a file descriptor for a VFIO group;
53 - @tablefd is a file descriptor for a TCE table allocated via
57 device file descriptor via VFIO_GROUP_GET_DEVICE_FD in order to support
59 callback. It is the same for device file descriptor via character device
66 KVM VM associated with this device, returns a file descriptor "pviommufd"
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-func-close.rst | 13 request-close - Close a request file descriptor
28 File descriptor returned by :ref:`MEDIA_IOC_REQUEST_ALLOC`.
33 Closes the request file descriptor. Resources associated with the request
45 ``fd`` is not a valid open file descriptor.
|
| D | request-func-poll.rst | 13 request-poll - Wait for some event on a file descriptor
28 List of file descriptor events to be watched
31 Number of file descriptor events at the \*ufds array
45 is non-zero). Request file descriptor set the ``POLLPRI`` flag in ``revents``
63 descriptor.
|
| D | media-func-close.rst | 28 File descriptor returned by :c:func:`open()`.
33 Closes the media device. Resources associated with the file descriptor
43 ``fd`` is not a valid open file descriptor.
|
| D | media-ioc-request-alloc.rst | 26 File descriptor returned by :c:func:`open()`.
36 ``errno`` is set to ``ENOTTY``. A request is accessed through a file descriptor
39 If the request was successfully allocated, then the request file descriptor
49 Finally, the file descriptor can be :ref:`polled <request-func-poll>` to wait
|
| D | request-api.rst | 49 for the media device node. This returns a file descriptor representing the
55 Standard V4L2 ioctls can then receive a request file descriptor to express the
66 queued by calling :ref:`MEDIA_REQUEST_IOC_QUEUE` on the request file descriptor.
97 User-space can :c:func:`poll()` a request file descriptor in
108 descriptor. Calling :ref:`ioctl VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` for a
119 :c:func:`close()` on a request file descriptor will make
120 that file descriptor unusable and the request will be freed once it is no
122 file descriptor is closed, then it won't be freed until the driver completed
173 its file descriptor, or start dequeuing CAPTURE buffers. Most likely, it will
190 request file descriptor, query control values at the time of its completion via
[all …]
|
| /Documentation/security/ |
| D | IMA-templates.rst | 25 definition of two new data structures: a template descriptor, to determine
32 measurement entries. Defining a new template descriptor requires
35 parameter. At boot time, IMA initializes the chosen template descriptor
42 descriptor chosen through the kernel configuration or through the newly
47 fields associated to the chosen template descriptor and store the result
52 the template descriptor used to produce that entry and call the show()
103 To specify the template descriptor to be used to generate measurement entries,
106 - select a template descriptor among those supported in the kernel
108 - specify a template descriptor name from the kernel command line through
110 - register a new template descriptor with custom format through the kernel
|
| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 10 the block group descriptor table unless the sparse_super feature flag
13 Notice how the group descriptor records the location of both bitmaps and
16 and the group descriptor table. The flex_bg mechanism uses this
30 block group descriptor was only 32 bytes long and therefore ends at
32 block group descriptor expands to at least the 64 bytes described below;
37 descriptor structure. If metadata_csum is set, then the block group
39 number, and the group descriptor structure. Both block and inode bitmap
43 The block group descriptor is laid out in ``struct ext4_group_desc``.
102 - Group descriptor checksum; crc16(sb_uuid+group_num+bg_desc) if the
|
| D | checksums.rst | 62 - UUID + the entire bitmap. Checksums are stored in the group descriptor,
63 and truncated if the group descriptor size is 32 bytes (i.e. ^64bit)
70 - If metadata_csum, then UUID + group number + the entire descriptor;
72 descriptor). In all cases, only the lower 16 bits are stored.
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.rst | 13 During normal operation autofs uses a file descriptor opened on the
15 operations. Using a file descriptor gives ioctl operations access to
21 file descriptor for these operations if we don't already have one open.
107 The current autofs implementation uses an ioctl file descriptor opened
109 descriptor are accounted for in checks made to determine if a mount is
202 The ioctlfd field is a mount point file descriptor of an autofs mount
206 mount point file descriptor, and when requesting the uid and gid of the
230 not a valid descriptor or doesn't correspond to an autofs mount point
231 an error of -EBADF, -ENOTTY or -EINVAL (not an autofs descriptor) is
261 with the ioctlfd field set to a valid autofs mount point descriptor
[all …]
|
| D | files.rst | 8 and file descriptor table (struct files) works.
10 Up until 2.6.12, the file descriptor table has been protected
13 of the table. ->count was used for sharing the file descriptor
17 a put_files_struct() frees the file descriptor (fd) table.
21 In the new lock-free model of file descriptor management,
23 based on RCU. The file descriptor table contains multiple
27 a lock-free reader, all the elements of the file descriptor
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 6 processors(PDSP), linking RAM, descriptor pools and infrastructure
10 reading descriptor address to a particular memory mapped location. The PDSPs
13 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
15 queue pool management (allocation, push, pop and notify) and descriptor
40 - Descriptor memory setup region.
53 as free descriptor queues or the
72 the buffer for descriptor information. This firmware
81 entries : Size of the accumulator descriptor list
91 - descriptor-regions : child node describing the memory regions for keystone
97 <"# of descriptors" "descriptor size">.
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 25 descriptor. The former is moved into the container by creating a character
26 device with the appropriate major and minor numbers while the file descriptor
29 commands via the file descriptor and use it for sending back responses.
35 The result of the ioctl are the file descriptor for the 'server side'
41 to the TPM. All commands from the driver can be read from the file descriptor
|
| /Documentation/arch/arm/keystone/ |
| D | knav-qmss.rst | 12 processors(PDSP), linking RAM, descriptor pools and infrastructure
16 reading descriptor address to a particular memory mapped location. The PDSPs
19 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
21 queue pool management (allocation, push, pop and notify) and descriptor
25 allocate descriptor pools, map the descriptors, push/pop to queues etc. For
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-close.rst | 28 File descriptor returned by :c:func:`open()`.
33 Closes the cec device. Resources associated with the file descriptor are
43 ``fd`` is not a valid open file descriptor.
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-close.rst | 28 File descriptor returned by :c:func:`open()`.
34 associated with the file descriptor are freed. However data format
45 ``fd`` is not a valid open file descriptor.
|
| /Documentation/iio/ |
| D | iio_dmabuf_api.rst | 35 IOCTLs have to be performed on the IIO buffer's file descriptor, which
39 Attach the DMABUF object, identified by its file descriptor, to the
44 Detach the given DMABUF object, identified by its file descriptor,
48 Note that closing the IIO buffer's file descriptor will
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-get-lineevent-ioctl.rst | 29 The file descriptor of the GPIO character device returned by `open()`.
45 file descriptor is closed. Once the file descriptor is closed, the state of
81 descriptor for the request.
|
12345678910>>...20