From: ivan.ivanov@linaro.org (Ivan T. Ivanov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] coresight-etm3x: Add Qualcomm PFT v1.1 peripheral ID
Date: Thu, 21 May 2015 18:24:25 +0300 [thread overview]
Message-ID: <1432221865.29174.29.camel@linaro.org> (raw)
In-Reply-To: <CANLsYky+hsVBR3Zh4yejL3EMA3sOX5Y+2GPp_KXrmDJ8xLAsUA@mail.gmail.com>
On Thu, 2015-05-21 at 08:10 -0600, Mathieu Poirier wrote:
> On 20 May 2015 at 09:02, Ivan T. Ivanov ivanov at linaro.org> wrote:
> > Add Qualcomm's PFT v1.1 peripheral ID to supported devices.
> > This device could be found at least in MSM8974 and APQ8064
> > chipsets.
> >
> > Signed-off-by: Ivan T. Ivanov ivanov at linaro.org>
> > ---
> > drivers/hwtracing/coresight/coresight-etm3x.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/hwtracing/coresight/coresight-etm3x.c
> > b/drivers/hwtracing/coresight/coresight-etm3x.c
> > index 018a00f..e13520f 100644
> > --- a/drivers/hwtracing/coresight/coresight-etm3x.c
> > +++ b/drivers/hwtracing/coresight/coresight-etm3x.c
> > @@ -1912,6 +1912,11 @@ static struct amba_id etm_ids[] = {
> > .mask = 0x0003ffff,
> > .data = "PTM 1.1",
> > },
> > + { /* PFT 1.1 Qualcomm */
> > + .id = 0x0003006f,
> > + .mask = 0x0003ffff,
> > + .data = "PFT 1.1",
> > + },
> > { 0, 0},
> > };
>
> I'm essentially good with that. On the flip side "PFT" is the format
> of the output generated by the tracer. What is important to identify
> is the type of tracer fitted to the SoC, either "ETM" or "PTM".
I was unable to find PTM 1.1 in the ARM documentation and PFT
v1.1 is supported only by PTM, if understand it correctly.
Regards,
Ivan
next prev parent reply other threads:[~2015-05-21 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 15:02 [PATCH] coresight-etm3x: Add Qualcomm PFT v1.1 peripheral ID Ivan T. Ivanov
2015-05-21 14:10 ` Mathieu Poirier
2015-05-21 15:24 ` Ivan T. Ivanov [this message]
2015-05-22 13:57 ` Mathieu Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1432221865.29174.29.camel@linaro.org \
--to=ivan.ivanov@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).