Home
last modified time | relevance | path

Searched refs:structure (Results 1 – 25 of 612) sorted by relevance

12345678910>>...25

/Linux-v5.4/drivers/infiniband/core/
Dpacker.c39 static u64 value_read(int offset, int size, void *structure) in value_read() argument
42 case 1: return *(u8 *) (structure + offset); in value_read()
43 case 2: return be16_to_cpup((__be16 *) (structure + offset)); in value_read()
44 case 4: return be32_to_cpup((__be32 *) (structure + offset)); in value_read()
45 case 8: return be64_to_cpup((__be64 *) (structure + offset)); in value_read()
64 void *structure, in ib_pack() argument
80 structure) << shift; in ib_pack()
97 structure) << shift; in ib_pack()
114 structure + desc[i].struct_offset_bytes, in ib_pack()
126 static void value_write(int offset, int size, u64 val, void *structure) in value_write() argument
[all …]
/Linux-v5.4/arch/arm/nwfpe/
DChangeLog12 - remove userRegisters pointer from this structure.
18 * The FPA11 structure is not a kernel-specific data structure.
21 FPA11 structure (size or position of elements contained
24 * Since 128-bit float requires the FPA11 structure to change
27 overflow the available space in the task structure.
36 * fpa11.c - Changes due to FPA11, FPREG structure alterations.
37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations.
38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations.
39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations.
40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations.
[all …]
/Linux-v5.4/Documentation/powerpc/
Dqe_firmware.rst89 structure signals the microcode which of these virtual traps is active.
91 This structure contains 6 words that the application should copy to some
92 specific been defined. This table describes the structure::
121 and has special instructions for the s/w associated with it. This structure is
183 This structure supports versioning, where the version of the structure is
184 embedded into the structure itself. To ensure forward and backwards
185 compatibility, all versions of the structure must use the same 'qe_header'
186 structure at the beginning.
189 The 'length' field is the size, in bytes, of the entire structure,
195 structure is a QE Firmware structure.
[all …]
/Linux-v5.4/Documentation/ioctl/
Dcdrom.rst64 DVD_READ_STRUCT Read structure
65 DVD_WRITE_STRUCT Write structure
151 cdrom_msf structure, describing a segment of music to play
182 cdrom_ti structure, describing a segment of music to play
211 cdrom_tochdr structure
215 cdrom_tochdr structure
236 cdrom_tocentry structure
240 cdrom_tocentry structure
372 cdrom_volctrl structure containing volumes for up to 4
422 cdrom_subchnl structure
[all …]
/Linux-v5.4/Documentation/userspace-api/
Dunshare.rst190 with the current task structure and releases corresponding shared
195 structure, where as unshare() operates on the current active
206 new namespace structure, the error return code will have to
209 structure, which may not exist anymore.
212 current context structure was moved into new dup_* functions. Now,
215 task structure that is being constructed. unshare() system call on
220 2) For each context structure, call the corresponding unshare()
222 structure, if the appropriate bit is set in the flags argument.
225 are new context structures then lock the current task structure,
226 associate new context structures with the current task structure,
[all …]
/Linux-v5.4/Documentation/media/uapi/dvb/
Ddvb-frontend-parameters.rst21 data, the structure size weren't enough to fit, and just extending its
34 ``dvb_frontend_parameters`` structure:
65 structure:
81 for cable QAM frontend you use the ``dvb_qam_parameters`` structure:
98 ATSC frontends are supported by the ``dvb_vsb_parameters`` structure:
113 DVB-T frontends are supported by the ``dvb_ofdm_parameters`` structure:
/Linux-v5.4/Documentation/admin-guide/kdump/
Dvmcoreinfo.rst9 information from the kernel like structure size, page size, symbol
36 data structure used to store information returned by the uname(2) system
81 Makedumpfile gets the pglist_data structure from this symbol, which is
89 The address of the mem_section array, its length, structure size, and
99 The size of a page structure. struct page is an important data structure
105 The size of a pglist_data structure. This value is used to check if the
106 pglist_data structure is valid. It is also used for checking the memory
112 The size of a zone structure. This value is used to check if the zone
113 structure has been found. It is also used for excluding free pages.
118 The size of a free_area structure. It indicates whether the free_area
[all …]
/Linux-v5.4/Documentation/filesystems/
Dfiles.txt25 table are in a separate structure - struct fdtable.
29 expansion of fdtable, a new fdtable structure is allocated
30 and files->fdtab points to the new structure. The fdtable
31 structure is freed with RCU and lock-free readers either
34 the fdtable structure -
61 4. To look up the file structure given an fd, a reader
79 file structure. This is avoided using atomic_long_inc_not_zero()
/Linux-v5.4/drivers/message/fusion/lsi/
Dmpi_history.txt106 * 05-24-00 00.10.02 Added _MSG_IOC_INIT_REPLY structure.
108 * 06-12-00 01.00.02 Added _MSG_PORT_ENABLE_REPLY structure.
109 * Added _MSG_EVENT_ACK_REPLY structure.
110 * Added _MSG_FW_DOWNLOAD_REPLY structure.
111 * Added _MSG_TOOLBOX_REPLY structure.
112 * 06-30-00 01.00.03 Added MaxLanBuckets to _PORT_FACT_REPLY structure.
113 * 07-27-00 01.00.04 Added _EVENT_DATA structure definitions for _SCSI,
116 * _MSG_EVENT_ACK_REPLY structure to match specification.
128 * Added structure offset comments.
129 * 04-09-01 01.01.07 Added structure EVENT_DATA_EVENT_CHANGE.
[all …]
/Linux-v5.4/Documentation/crypto/
Dcrypto_engine.rst12 You must put, at the start of your transform context your_tfm_ctx, the structure
24 has access to the transform structure. It is not possible to access the context
26 structure "``struct your_tfm_ctx``". The engine assumes (requires) the placement
55 Note that these functions access the crypto_async_request structure
Duserspace-if.rst103 filled struct sockaddr data structure. This data structure must be
142 initialization, the struct sockaddr data structure must be filled as
160 specified with the data structure provided by the sendmsg() system call.
163 struct cmsghdr data structure. See recv(2) and cmsg(3) for more
164 information on how the cmsghdr data structure is used together with the
165 send/recv system call family. That cmsghdr data structure holds the
196 initialization, the struct sockaddr data structure must be filled as
219 specified with the data structure provided by the sendmsg() system call.
222 struct cmsghdr data structure. See recv(2) and cmsg(3) for more
223 information on how the cmsghdr data structure is used together with the
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/clock/st/
Dst,flexgen.txt1 Binding for a type of flexgen structure found on certain
4 This structure includes:
8 Flexgen structure is a part of Clockgen[1].
14 | Flexgen structure |
/Linux-v5.4/Documentation/hid/
Dhiddev.rst94 the value that it was changed to. Note that the structure is defined
122 hiddev_devinfo structure.
138 Gets a hiddev_devinfo structure which describes the device.
179 Fills in a hiddev_report_info structure for the user. The report is
188 filled into the returned hiddev_report_info structure.
194 hiddev_field_info structure. The user must fill in report_id and
195 report_type in this structure, as above. The field_index should also
202 Returns the usage_code in a hiddev_usage_ref structure, given that
204 field have already been filled into the structure.
209 Returns the value of a usage in a hiddev_usage_ref structure. The
[all …]
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars41 a structure that contains everything
43 For structure definition see "struct
50 match byte for byte with the structure
54 **Note** the efi_variable structure
/Linux-v5.4/Documentation/driver-api/
Dmiscellaneous.rst34 are expected to embed this structure in a driver-specific structure.
35 This structure contains fields that describe a particular chip.
/Linux-v5.4/Documentation/security/
DSCTP.rst33 @ep - pointer to sctp endpoint structure.
45 @sk - Pointer to sock structure.
120 @ep - pointer to current sctp endpoint structure.
121 @sk - pointer to current sock structure.
122 @sk - pointer to new sock structure.
129 @sk - pointer to sock structure.
207 @ep - pointer to sctp endpoint structure.
266 @ep - pointer to current sctp endpoint structure.
267 @sk - pointer to current sock structure.
268 @sk - pointer to new sock structure.
[all …]
/Linux-v5.4/Documentation/devicetree/
Dof_unittest.txt19 from the unflattened device tree data structure. This interface is used by
55 Un-flattened device tree structure:
58 structure described below.
69 Figure 1, describes a generic structure of machine's un-flattened device tree
98 Figure 1: Generic structure of un-flattened device tree
136 data node is attached to the live tree above (Figure 1), the final structure is
172 Figure 3: Live device tree structure after attaching the testcase-data.
176 sibling compared to the earlier structure (Figure 2). After attaching first
/Linux-v5.4/Documentation/admin-guide/blockdev/drbd/
Ddata-structure-v9.rst2 kernel data structure for DRBD-9
5 This describes the in kernel data structure for DRBD-9. Starting with
6 Linux v3.14 we are reorganizing DRBD to use this data structure.
/Linux-v5.4/Documentation/virt/kvm/
Dmsr.txt20 structure:
54 a copy of the following structure:
69 updates of this structure is arbitrary and implementation-dependent.
70 The hypervisor may update this structure at any time it sees fit until
80 of the update of this structure. Guests can subtract this value
82 structure update.
85 time at the time this structure was last updated. Unit is
207 hold a copy of the following structure:
220 updates of this structure is arbitrary and implementation-dependent.
221 The hypervisor may update this structure at any time it sees fit until
[all …]
/Linux-v5.4/scripts/coccinelle/free/
Dkfreeaddr.cocci2 /// Free of a structure field
36 msg = "ERROR: invalid free of structure field"
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-g-crop.rst46 ``type`` field of a struct :c:type:`v4l2_crop` structure to the
48 with a pointer to this structure. The driver fills the rest of the
49 structure or returns the ``EINVAL`` error code if cropping is not supported.
53 v4l2_crop structure and call the :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctl with a pointer
54 to this structure.
Ddev-meta.rst32 :c:type:`v4l2_capability` structure returned by the :c:func:`VIDIOC_QUERYCAP`
36 :c:type:`v4l2_capability` structure. That flag means the device can read
51 :c:type:`v4l2_format` structure to ``V4L2_BUF_TYPE_META_CAPTURE`` or to
54 and applications must set the remainder of the :c:type:`v4l2_format` structure
/Linux-v5.4/Documentation/devicetree/bindings/pwm/
Dnxp,pca9685-pwm.txt13 - open-drain (bool): boolean to configure outputs with open-drain structure;
14 if omitted use totem-pole structure
/Linux-v5.4/Documentation/
Dpadata.txt14 The first step in using padata is to set up a padata_instance structure for
103 padata_priv structure::
111 This structure will almost certainly be embedded within some larger
112 structure specific to the work to be done. Most of its fields are private to
113 padata, but the structure should be zeroed at initialisation time, and the
135 function gets the padata_priv structure pointer as its lone parameter;
137 container_of() to find the enclosing structure.
150 serial() function in the padata_priv structure. That call will happen on
/Linux-v5.4/Documentation/driver-api/soundwire/
Dlocking.rst16 SoundWire Bus lock is a mutex and is part of Bus data structure
24 - Access of Stream data structure.
30 Bus data structure (sdw_bus). This lock is used to serialize the message

12345678910>>...25