Re: [PATCH] coresight: Handle build path error

2016-06-02 Thread Mathieu Poirier
On 1 June 2016 at 12:04, Suzuki K Poulose wrote: > On 06/05/16 15:43, Mathieu Poirier wrote: >> >> On 6 May 2016 at 08:35, Suzuki K Poulose wrote: >>> >>> Enabling a component via sysfs (echo 1 > enable_source), would >>> trigger building a path from the enabled sources to the sink. >>> If there

Re: [PATCH] coresight: Handle build path error

2016-06-01 Thread Suzuki K Poulose
On 06/05/16 15:43, Mathieu Poirier wrote: On 6 May 2016 at 08:35, Suzuki K Poulose wrote: Enabling a component via sysfs (echo 1 > enable_source), would trigger building a path from the enabled sources to the sink. If there is an error in the process (e.g, sink not enabled or the device (CPU co

Re: [PATCH] coresight: Handle build path error

2016-05-06 Thread Mathieu Poirier
On 6 May 2016 at 08:35, Suzuki K Poulose wrote: > Enabling a component via sysfs (echo 1 > enable_source), would > trigger building a path from the enabled sources to the sink. > If there is an error in the process (e.g, sink not enabled or > the device (CPU corresponding to ETM) is not online), w

Re: [PATCH] coresight: Handle build path error

2016-05-06 Thread Suzuki K Poulose
On 06/05/16 15:26, Mathieu Poirier wrote: On 4 May 2016 at 04:41, Suzuki K Poulose wrote: Enabling a component via sysfs (echo 1 > enable_source), would trigger building a path from the enabled sources to the sink. If there is an error in the process (e.g, sink not enabled or the device (CPU co

Re: [PATCH] coresight: Handle build path error

2016-05-06 Thread Mathieu Poirier
On 4 May 2016 at 04:41, Suzuki K Poulose wrote: > Enabling a component via sysfs (echo 1 > enable_source), would > trigger building a path from the enabled sources to the sink. > If there is an error in the process (e.g, sink not enabled or > the device (CPU corresponding to ETM) is not online), w