[PATCH 00/15][RFC] Android ETM driver changes

[John Stultz]

The Android kernel tree has a number of changes to the ETM driver.
Arve sent the first 9 of these to the list over a year ago and
got very little response.

I didn't want these to get lost, so I pinged Alexander about
these privately and he stated that he wasn't actively
maintaining the driver, but after skimming the entire set
acked the series and suggested I send it on to Russel for
review and possible inclusion.

So here they are. Please let me know if there are any
objections to merging these, or if further changes are
needed.


CC: Russell King <linux@xxxxxxxxxxxxxxxx>
CC: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
CC: Alexander Shishkin <alexander.shishkin@xxxxxxxxxxxxxxx>
CC: Arve HjÃnnevÃg <arve@xxxxxxxxxxx>

Arve HjÃnnevÃg (15):
  ARM: etm: Don't require clock control
  ARM: etm: Don't limit tracing to only non-secure code.
  ARM: etm: Don't try to clear the buffer full status after reading the
    buffer
  ARM: etm: Allow range selection
  ARM: etm: Configure data tracing
  ARM: etm: Add some missing locks and error checks
  ARM: etm: Return the entire trace buffer if it is empty after reset
  ARM: etm: Support multiple ETMs/PTMs.
  ARM: etm: Power down etm(s) when tracing is not enabled
  ARM: etm: Wait for etm/ptm(s) to stop before requesting PowerDown
  ARM: etm: Check arch version and disable data tracing for ptm
  ARM: etm: Add sysfs entry to enable timestamps if supported
  ARM: etm: Add sysfs entry to set context-id-size
  ARM: etm: Add sysfs entry to disable branch_output flag
  ARM: etm: Add sysfs entry to enable return stack if supported

 arch/arm/include/asm/hardware/coresight.h |   50 ++-
 arch/arm/kernel/etm.c                     |  680 +++++++++++++++++++++++------
 2 files changed, 587 insertions(+), 143 deletions(-)

-- 
1.7.3.2.146.gca209

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/