diff options
| author | Kiwoong Kim <[email protected]> | 2016-09-09 08:22:22 +0900 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2016-09-21 16:28:57 -0400 |
| commit | 8794ee0c1d4ce35b8b8e4e8cdc80bba6e42206eb (patch) | |
| tree | 7e727ec4d825789f4d15d824bbdd83051804645a /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 07d0e9a847401ffd2f09bd450d41644cd090e81d (diff) | |
scsi: ufs: Get a TM service response from the correct offset
When any UFS host controller receives a TM(Task Management) response
from a UFS device, UFS driver has been recognize like receiving a
message of "Task Management Function Complete"(00h) in all cases, so
far. That means there is no pending task for a tag of the TM request
sent before in the UFS device. That's because the byte offset 6 in TM
response which has been used to get a TM service response so far
represents just whether or not a TM transmission passes.
Regarding UFS spec, the correct byte offset to get TM service response
is 15, not 6.
I tested that UFS driver responds properly for the TM response from a
UFS device with an reference board with exynos8890, as follow: No
pending task -> Task Management Function Complete (00h) Pending task ->
Task Management Function Succeeded (08h)
[mkp: applied by hand]
Signed-off-by: Kiwoong Kim <[email protected]>
Signed-off-by: HeonGwang Chu <[email protected]>
Tested-by: : Kiwoong Kim <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions