diff options
| author | Joshua Yeong <[email protected]> | 2023-11-14 16:55:25 +0800 |
|---|---|---|
| committer | Alexandre Belloni <[email protected]> | 2023-11-16 23:37:56 +0100 |
| commit | 2aac0bf4ebc8e09941bb2a40c0ce725437d9a82c (patch) | |
| tree | de9a0af3a3e8586ee57615a4d0eb85b640b16e4f /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 4afd72876942f2ab1e97e79082464a46ab40a485 (diff) | |
i3c: Add fallback method for GETMXDS CCC
Some I3C hardware will report error when an incorrect length is received from
device. GETMXDS CCC are available in 2 formats: without turnaround time (format
1) and with turnaround time (format 2). There is no mechanics to determine which
format is supported by device. So in case sending GETMXDS CCC format 2 resulted
in a failure, try sending GETMXDS CCC format 1 instead.
Signed-off-by: Joshua Yeong <[email protected]>
Reviewed-by: Miquel Raynal <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Alexandre Belloni <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions