[PATCH 1/9 v2] coresight: add CoreSight core layer framework

[Mathieu Poirier]

On 30 June 2014 04:53, Dirk Behme <dirk.behme at de.bosch.com> wrote:
> On 27.06.2014 20:04, mathieu.poirier at linaro.org wrote:
>>
>> From: Pratik Patel <pratikp at codeaurora.org>
>>
>> CoreSight components are compliant with the ARM CoreSight
>> architecture specification and can be connected in various
>> topologies to suite a particular SoCs tracing needs. These trace
>> components can generally be classified as sources, links and
>> sinks. Trace data produced by one or more sources flows through
>> the intermediate links connecting the source to the currently
>> selected sink.
>>
>> CoreSight framework provides an interface for the CoreSight trace
>> drivers to register themselves with. It's intended to build up a
>> topological view of the CoreSight components and configure the
>> right series of components on user input via debugfs.
>>
>> For eg., when enabling a source, framework builds up a path
>> consisting of all the components connecting the source to the
>> currently selected sink and enables all of them.
>>
>> Framework also supports switching between available sinks and
>> also provides status information to user space applications
>> through the debugfs interface.
>>
>> Signed-off-by: Pratik Patel <pratikp at codeaurora.org>
>> Signed-off-by: Panchaxari Prasannamurthy
>> <panchaxari.prasannamurthy at linaro.org>
>> Signed-off-by: Mathieu Poirier <mathieu.poirier at linaro.org>
>> ---
>>   .../devicetree/bindings/arm/coresight.txt          | 141 +++++
>>   drivers/Kconfig                                    |   2 +
>
>
> I wonder if
>
> arch/arm/Kconfig.debug
>
> wouldn't be better place for this?

With the other kernel hacking options - right, that is probably best.

>
> Best regards
>
> Dirk