Searched refs:payloads (Results 1 – 17 of 17) sorted by relevance
122 struct i2c_payload *payloads; member
240 list_for_each_entry(pos, &mst_state->payloads, next) { in dm_helpers_construct_old_payload()612 msgs[i].flags = cmd->payloads[i].write ? 0 : I2C_M_RD; in dm_helpers_submit_i2c()613 msgs[i].addr = cmd->payloads[i].address; in dm_helpers_submit_i2c()614 msgs[i].len = cmd->payloads[i].length; in dm_helpers_submit_i2c()615 msgs[i].buf = cmd->payloads[i].data; in dm_helpers_submit_i2c()
8232 cmd.payloads = kcalloc(num, sizeof(struct i2c_payload), GFP_KERNEL); in amdgpu_dm_i2c_xfer()8234 if (!cmd.payloads) in amdgpu_dm_i2c_xfer()8242 cmd.payloads[i].write = !(msgs[i].flags & I2C_M_RD); in amdgpu_dm_i2c_xfer()8243 cmd.payloads[i].address = msgs[i].addr; in amdgpu_dm_i2c_xfer()8244 cmd.payloads[i].length = msgs[i].len; in amdgpu_dm_i2c_xfer()8245 cmd.payloads[i].data = msgs[i].buf; in amdgpu_dm_i2c_xfer()8254 kfree(cmd.payloads); in amdgpu_dm_i2c_xfer()
180 parsing pass over the message and sort out the payloads into buckets indexed182 payloads. We then pass over them once more validating each payload183 in numeric payload type order. This makes SA payloads come naturally first.194 number of payloads instead, like 10 or so.316 entire payloads in readable form via field_dump_payload.
4 Does the spec limit the count of SA payloads in a message? Where if so?
32 Running EFI payloads with U-Boot:
176 i2c_command.payloads = i2c_payloads; in hdmi_14_process_transaction()
21 // contains other kinds of dnstap payloads, although currently only one type67 // metadata. Applications generating "Message" payloads should follow
54 u_int8_t payloads[0]; member236 payload = ih->payloads; in ike_print()
482 struct i2c_payload *payload = cmd->payloads + index_of_payload; in dce_i2c_submit_command_sw()
593 struct i2c_payload *payload = cmd->payloads + index_of_payload; in dce_i2c_submit_command_hw()
21 // contains other kinds of dnstap payloads, although currently only one type116 // metadata. Applications generating "Message" payloads should follow
46 Running EFI payloads with U-Boot:
192 ** Strict checks for CTAP2 compliance on received CBOR payloads.
35 Running EFI payloads with U-Boot:
99 as markers for user-defined Event Data payloads. Metadata records have 16
649 for UTF-16 payloads containing CDATA sections.