On Wed, 23 Jan 2019 at 05:12, Sai Prakash Ranjan
<saiprakash.ranjan@xxxxxxxxxxxxxx> wrote:
That depends on whether the ETMs have been modified at all, something
Suzuki has asked to be clarified. If ETMs have been modified then we
need to understand how they differ from the driver's implementation.
If the implementations are the same:
@@ -1079,6 +1079,10 @@ static const struct amba_id etm4_ids[] = {
ETM4x_AMBA_ID(0x000bb95a), /* Cortex-A72 */
ETM4x_AMBA_ID(0x000bb959), /* Cortex-A73 */
ETM4x_AMBA_ID(0x000bb9da), /* Cortex-A35 */
+ ETM4x_AMBA_ID(0x000f0211), /* Qualcomm Kryo */
+ ETM4x_AMBA_ID(0x000f0205), /* Qualcomm Kryo */
What version of the Kryo CPU? And the above will need to be in a
separate patch with the modifications to address the problem you
mentionned below.
+ ETM4x_AMBA_ID(0x000bb803), /* Qualcomm Kryo 385
Cortex-A75 */
+ ETM4x_AMBA_ID(0x000bb802), /* Qualcomm Kryo 385
Cortex-A55 */
Please add them in chronological order.
{},
};
For msm8996, cpu debug module pid returned is same as ETM
which is causing the probe failure for cpu debug coresight module
as shown in below logs.
For this case, I tried adding these ids to cpu debug driver, but it
splits some errors (coresight-cpu-debug: probe of 3840000.etm failed
with error -16) since the ids are same. Can we override for this case
or there is something else we can do here?
That is another problem. See this patchset [1] from Mike Leach for a
description of the problem and how to fix it.
[1]. https://lkml.org/lkml/2018/12/7/784