summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2016-02-22 09:22:38 -0800
committerTony Lindgren <tony@atomide.com>2016-02-22 09:22:38 -0800
commitd9d806b90260fbcd9bd1d43db492bfcbc19f014a (patch)
tree80393451efc7ae029db349d50a39abd89d6bc0a8 /tools/perf/scripts/python/event_analyzing_sample.py
parentbaa10e0dd2090d7db3a9ab47978ab95cc65b76f1 (diff)
ARM: OMAP2+: Fix out of range register access with syscon_config.max_register
If syscon_config.max_register is initialized like it should be, we have omap_ctrl_read/write() fail with out of range register access at least for omap3. We have omap3.dtsi setting up a regmap range for scm_conf, but we now have omap_ctrl_read/write() also attempt to use the regmap. However, omap_ctrl_read/write() is also used for other register ranges in the system control module (SCM). Let's fix the issue by just removing the regmap_read/write() usage for control module as suggested by Tero Kristo <t-kristo@ti.com>. Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions