diff options
author | Leo Yan <[email protected]> | 2017-06-05 14:15:10 -0600 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2017-06-09 11:45:24 +0200 |
commit | a70fc83d3c50c5e3c69de66d4b13d8a1fbfbbe73 (patch) | |
tree | e863d0f8943851941fd1b1c06bf4bebc67bfe053 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | a3959c50b02f57df4c4e4f14f632220f1c0b1f79 (diff) |
coresight: bindings for CPU debug module
According to ARMv8 architecture reference manual (ARM DDI 0487A.k)
Chapter 'Part H: External debug', the CPU can integrate debug module
and it can support self-hosted debug and external debug. Especially
for supporting self-hosted debug, this means the program can access
the debug module from mmio region; and usually the mmio region is
integrated with coresight.
So add document for binding debug component, includes binding to APB
clock; and also need specify the CPU node which the debug module is
dedicated to specific CPU.
Suggested-by: Mike Leach <[email protected]>
Signed-off-by: Leo Yan <[email protected]>
Reviewed-by: Suzuki K Poulose <[email protected]>
Acked-by: Rob Herring <[email protected]>
Signed-off-by: Mathieu Poirier <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions