https://wiki.linaro.org/WorklingGroups/Kernel/Coresight/traceDecodingWithDS5
[2].https://github.com/hwangcc23/ptm2human
New in this patchset:
. Rebased on v3.18-rc3
. Added support for hip04-d01 board
Mathieu Poirier (4):
coresight: documentation for coresight framework and drivers
core
From: Mathieu Poirier
Documentation containing an explanation on what the framework
provides and the drivers working with it. A minimal example
on how to use the functionality is also provided.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 299
From: Mathieu Poirier
Documentation containing an explanation on what the framework
provides and the drivers working with it. A minimal example
on how to use the functionality is also provided.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 299
].https://wiki.linaro.org/WorklingGroups/Kernel/Coresight/traceDecodingWithDS5
[2].https://github.com/hwangcc23/ptm2human
New in this patchset:
. Rebased on v3.18-rc1
. Added coresight entry to MAINTAINERS file
. Typo fixes to documentation
. Re-arranged configuration of link and sinks in Kconfig and
From: Mathieu Poirier
Coresight is an umbrella of technologies allowing for the debugging of ARM
based SoCs. It includes solutions for JTAG and HW assisted tracing. This
patchset is concerned with the latter.
Coresight components are cathegorised as source, link and sinks and are
(usually) dis
From: Mathieu Poirier
Coresight is an umbrella of technologies allowing for the debugging of ARM
based SoCs. It includes solutions for JTAG and HW assisted tracing. This
patchset is concerned with the latter.
Coresight components are cathegorised as source, link and sinks and are
(usually) dis
From: Mathieu Poirier
Coresight is an umbrella of technologies allowing for the debugging of ARM
based SoCs. It includes solutions for JTAG and HW assisted tracing. This
patchset is concerned with the latter.
Coresight components are cathegorised as source, link and sinks and are
(usually) dis
From: Mathieu Poirier
This patchset concentrates on enabling HW assisted tracing on ARM
SoCs. This first wave centers on the basic tracing functionnality,
enabling components such ETM/PTM, funnel, replicator, TMC, TPIU and
ETB. Subsequent submissions will enable more intricate IP blocks such
as
From: Mathieu Poirier
This patchset concentrates on enabling HW assisted tracing on ARM
SoCs. This first wave centers on the basic tracing functionnality,
enabling components such ETM/PTM, funnel, replicator, TMC, TPIU and
ETB. Subsequent submissions will enable more intricate IP blocks such
as
Mathieu,
On Thu, 7 Aug 2014 12:21:36 -0600, mathieu.poir...@linaro.org wrote:
> arch/arm/Kconfig.debug | 36 +-
> arch/arm/boot/dts/omap3-beagle-xm.dts | 28 +
> arch/arm/boot/dts/omap3-beagle.dts | 28 +
> arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts | 199
Hi Mathieu.
Maybe I just missed it, but ...
>
> As part of this patchset you will find:
>
> . The return of non-configurable replicators. Since they don't
> show up on the AMBA bus we need to use the platform device model.
> . It is now possible to configure and use multiple sinks simultaneou
From: Mathieu Poirier
As part of this patchset you will find:
. The return of non-configurable replicators. Since they don't
show up on the AMBA bus we need to use the platform device model.
. It is now possible to configure and use multiple sinks simultaneously.
. The coresigh config entries
> This set is addressing comments received after the May 30th
> submission[1]. More specifically:
>
> .All drivers have been converted to use the AMBA bus
> interface.
> .Debugfs entries are now created with a macro.
> .A header file was created for the ETM driver to allow
> for the reuse of con
From: Mathieu Poirier
This set is addressing comments received after the May 30th
submission[1]. More specifically:
.All drivers have been converted to use the AMBA bus
interface.
.Debugfs entries are now created with a macro.
.A header file was created for the ETM driver to allow
for the reu
From: Mathieu Poirier
This RFC is rescucitating the work submitted by Pratik Patel in
2012 [1].
This set is addressing comments gathered from the initial RFC
and enhance the framework in a few areas. More specifically:
. Sysfs entries have been moved to debugfs.
. The removal of the "bus" c
On Wed, Jan 16, 2013 at 12:14:59AM +, Pratik Patel wrote:
> On Mon, Jan 07, 2013 at 11:58:36AM +, Will Deacon wrote:
> > On Thu, Jan 03, 2013 at 06:06:43PM +, Pratik Patel wrote:
> > > Whats the advantage in using debugfs here?
> >
> > The main things I like about debugfs are (a) it's
On Mon, Jan 07, 2013 at 11:58:36AM +, Will Deacon wrote:
> On Thu, Jan 03, 2013 at 06:06:43PM +, Pratik Patel wrote:
> > On Sun, Dec 23, 2012 at 11:32:39AM +, Will Deacon wrote:
> > > On Fri, Dec 21, 2012 at 10:18:28PM +, Pratik Patel wrote:
> > > > What user interface do you plan t
On Thu, Jan 03, 2013 at 06:06:43PM +, Pratik Patel wrote:
> On Sun, Dec 23, 2012 at 11:32:39AM +, Will Deacon wrote:
> > On Fri, Dec 21, 2012 at 10:18:28PM +, Pratik Patel wrote:
> > > What user interface do you plan to provide for the CTI? Maybe
> > > something consistent with other Co
On Wed, Jan 02, 2013 at 02:00:21PM -0600, Jon Hunter wrote:
>
> The code is largely based upon the existing cti helpers, which just had
> a cti_map_trigger() function. The use-case you described is not
> supported by the current helpers and so also not supported in my initial
> implementation (alt
On Sun, Dec 23, 2012 at 11:32:39AM +, Will Deacon wrote:
> On Fri, Dec 21, 2012 at 10:18:28PM +, Pratik Patel wrote:
> > What user interface do you plan to provide for the CTI? Maybe
> > something consistent with other CoreSight components in sysfs to
> > allow users to enable, disable, map
On 12/21/2012 04:18 PM, Pratik Patel wrote:
> On Thu, Dec 20, 2012 at 04:54:38PM -0600, Jon Hunter wrote:
>>
>> On 12/20/2012 01:51 PM, Pratik Patel wrote:
>>> On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
On 12/19/2012 03:24 PM, Pratik Patel wrote:
[snip]
>>
On Fri, Dec 21, 2012 at 10:18:28PM +, Pratik Patel wrote:
> What user interface do you plan to provide for the CTI? Maybe
> something consistent with other CoreSight components in sysfs to
> allow users to enable, disable, map and unmap ???
>
> Please let me know your thoughts.
Rather than ha
On Thu, Dec 20, 2012 at 04:54:38PM -0600, Jon Hunter wrote:
>
> On 12/20/2012 01:51 PM, Pratik Patel wrote:
> > On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
> >>
> >> On 12/19/2012 03:24 PM, Pratik Patel wrote:
> >>
> >> [snip]
> >>
> >>> Currently we use the CoreSight virtual bus t
On Thu, Dec 20, 2012 at 11:40:11PM +, Russell King - ARM Linux wrote:
> On Thu, Dec 20, 2012 at 04:54:38PM -0600, Jon Hunter wrote:
> > On 12/20/2012 01:51 PM, Pratik Patel wrote:
> > > Ok, so are you referring to making CoreSight devices register
> > > with AMBA bus instead of platform bus kee
On Thu, Dec 20, 2012 at 09:16:15PM +0100, Jean Pihet wrote:
> Hi Pratik,
>
> On Thu, Dec 20, 2012 at 8:51 PM, Pratik Patel wrote:
> > On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
> >>
> >> On 12/19/2012 03:24 PM, Pratik Patel wrote:
> >>
> >> [snip]
> >>
> >> > Currently we use the
On Thu, Dec 20, 2012 at 04:54:38PM -0600, Jon Hunter wrote:
> On 12/20/2012 01:51 PM, Pratik Patel wrote:
> > Ok, so are you referring to making CoreSight devices register
> > with AMBA bus instead of platform bus keeping everything else
> > intact?
>
> Yes exactly. However, please note I am not s
On 12/20/2012 01:51 PM, Pratik Patel wrote:
> On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
>>
>> On 12/19/2012 03:24 PM, Pratik Patel wrote:
>>
>> [snip]
>>
>>> Currently we use the CoreSight virtual bus to conveniently list
>>> sysfs configuration attributes for all the registered
Hi Pratik,
On Thu, Dec 20, 2012 at 8:51 PM, Pratik Patel wrote:
> On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
>>
>> On 12/19/2012 03:24 PM, Pratik Patel wrote:
>>
>> [snip]
>>
>> > Currently we use the CoreSight virtual bus to conveniently list
>> > sysfs configuration attributes
On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote:
>
> On 12/19/2012 03:24 PM, Pratik Patel wrote:
>
> [snip]
>
> > Currently we use the CoreSight virtual bus to conveniently list
> > sysfs configuration attributes for all the registered CoreSight
> > devices.
> >
> > For eg:
> > /sys/
On 12/19/2012 03:24 PM, Pratik Patel wrote:
[snip]
> Currently we use the CoreSight virtual bus to conveniently list
> sysfs configuration attributes for all the registered CoreSight
> devices.
>
> For eg:
> /sys/bus/coresight/devices/coresight-etm0/
> /sys/bus/coresight/devices/coresight-etm1/
On Wed, Dec 19, 2012 at 11:03:58AM -0600, Jon Hunter wrote:
>
> On 12/19/2012 05:23 AM, Will Deacon wrote:
> > Hi Pratik,
> >
> > On Tue, Dec 18, 2012 at 07:19:17PM +, prat...@codeaurora.org wrote:
> >> This RFC is aimed at introducing CoreSight framework as well as
> >> individual CoreSight
On Wed, Dec 19, 2012 at 11:23:14AM +, Will Deacon wrote:
> Hi Pratik,
>
> On Tue, Dec 18, 2012 at 07:19:17PM +, prat...@codeaurora.org wrote:
> > This RFC is aimed at introducing CoreSight framework as well as
> > individual CoreSight trace component drivers adhering to ARM
> > CoreSight s
32 matches
Mail list logo
