summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorSujit Reddy Thumma <sthumma@codeaurora.org>2014-12-09 12:55:38 +0200
committerSubhash Jadavani <subhashj@codeaurora.org>2016-05-31 15:25:58 -0700
commit3332d5a9e4fe04b14c3008d432a031c22a38bd2c (patch)
tree3168753ba17039b51be7ebeb8da87b94d6992af2 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent90102c17f9caaaf8ad8ec241df0a434aa3d8c643 (diff)
mmc: core: Fix clock frequency transitions during invalid states
eMMC and SD card specifications restrict the usage of a class of commands while commands in other class are in progress. For example, during erase operations the SD/eMMC spec. allows only CMD35, CMD36, CMD38. If clock scaling is enabled and decide to scale up the clocks it may be possible that CMD19/21 tuning commands are sent in between erase commands, which is illegal as per specification. Fix such illegal transactions to the card and also make clock scaling statistics accountable only for read/write commands instead of time consuming commands, like CMD38 erase, where transactions are independent of bus frequency. Change-Id: Iffba175787837e7f95bde8970f19d0f0f9d7d67d Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org> [merez@codeaurora.org: fix conflicts as mmc_update_clk_scaling is missing on 3.14] Signed-off-by: Maya Erez <merez@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions