On 30 June 2014 04:53, Dirk Behme <[email protected]> wrote: > On 27.06.2014 20:04, [email protected] wrote: >> >> From: Pratik Patel <[email protected]> >> >> 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 <[email protected]> >> Signed-off-by: Panchaxari Prasannamurthy >> <[email protected]> >> Signed-off-by: Mathieu Poirier <[email protected]> >> --- >> .../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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
