lkml.org 
[lkml]   [2015]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH v0 01/11] stm class: Introduce an abstraction for System Trace Module devices
Date
Mathieu Poirier <mathieu.poirier@linaro.org> writes:

> I forgot to mention in my previous email... I think the hierarchy of
> our respective tracing module along with the generic-stm probably
> needs a review.
>
> Currently we have drivers/coresight, drivers/intel_th and drivers/stm.
>
> To me it doesn't scale - what happens when other architectures come
> out with their own hw tracing technologies?
>
> I suggest we move everything under drivers/hwtracing and as such have:
>
> drivers/hwtracing
> drivers/hwtracing/intel_ht
> drivers/hwtracing/coresight
> drivers/hwtracing/stm
>
> That way other architectures can add drivers for their own hw tracing
> technology without further polluting the drivers/ directory and
> concentrating everything in the same area. What's your view on that?

I wanted to suggest something similar, actually, if you don't mind
moving drivers/coresight, then let's do it.

Regards,
--
Alex


\
 
 \ /
  Last update: 2015-03-19 15:41    [W:0.100 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site