From: "Ivan T. Ivanov" <ivan.ivanov@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Kumar Gala <galak@codeaurora.org>,
Pratik Patel <pratikp@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] coresight: replicator: Add Qualcomm CoreSight Replicator driver
Date: Thu, 30 Apr 2015 10:21:06 +0300 [thread overview]
Message-ID: <1430378466.2400.8.camel@linaro.org> (raw)
In-Reply-To: <CANLsYkwfDYjTqBUvXp2da6E=SA8F2EbH7_Mi20Sba9NpJm9Y7g@mail.gmail.com>
On Wed, 2015-04-29 at 10:28 -0600, Mathieu Poirier wrote:
> On 29 April 2015 at 06:19, Ivan T. Ivanov ivanov@linaro.org> wrote:
<snip>
> > - "arm,coresight-etm4x", "arm,primecell";
> > + - "qcom,coresight-replicator", "arm,primecell";
>
> Is there some sort of versioning information we can add like it was
> done for the "coresight-etmXY" bindings? It makes things a lot
> cleaner when a new (and possibly not backward compatible) version gets
> released.
>
>From what I can see, it is version 1. I could add it to compatible
string, but suldn't we use amba_id for this reason.
> > * reg: physical base address and length of the register
> > set(s) of the component.
> > diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig
> > index 6b331d4..165b681 100644
> > --- a/drivers/hwtracing/coresight/Kconfig
> > +++ b/drivers/hwtracing/coresight/Kconfig
> > @@ -68,4 +68,13 @@ config CORESIGHT_SOURCE_ETM4X
> > instructions that a processor is executing. This is primarily useful
> > for instruction level tracing. Depending on the implemented version
> > data tracing may also be available.
> > +
> > +config CORESIGHT_QCOM_REPLICATOR
> > + bool "Qualcomm CoreSight Replicator driver"
> > + help
> > + This enables support for CoreSight link and sink driver that are
> > + responsible for transporting and collecting the trace data
> > + respectively. Link and sinks are dynamically aggregated with a trace
> > + entity at run time to form a complete trace path.
>
> The replicator is only a link entity. It is only transporting trace
> data information rather than collecting it. Please review the
> comment.
True, sorry. copy and paste from CORESIGHT_LINKS_AND_SINKS.
> Also, can this specific version run on both V7 and V8
> architecture. If not the proper "depends" should be added.
>
Same driver/device on both architectures.
Will fix rest of the comments and will resend.
Thank you,
Ivan
next prev parent reply other threads:[~2015-04-30 7:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 12:19 [PATCH 0/2] Add initial CoreSight support for the Qualcomm 8x16 chipsets Ivan T. Ivanov
[not found] ` <1430310000-10867-1-git-send-email-ivan.ivanov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-04-29 12:19 ` [PATCH 1/2] coresight: replicator: Add Qualcomm CoreSight Replicator driver Ivan T. Ivanov
2015-04-29 16:28 ` Mathieu Poirier
2015-04-30 7:21 ` Ivan T. Ivanov [this message]
[not found] ` <1430378466.2400.8.camel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-04-30 13:07 ` Mathieu Poirier
2015-04-30 20:53 ` Paul Bolle
2015-05-07 14:46 ` Ivan T. Ivanov
2015-05-07 16:39 ` Paul Bolle
2015-04-29 12:20 ` [PATCH 2/2] arm64: dts: qcom: Add msm8916 CoreSight components Ivan T. Ivanov
2015-04-29 16:49 ` Mathieu Poirier
2015-04-30 7:22 ` Ivan T. Ivanov
2015-04-30 9:24 ` Ivan T. Ivanov
2015-04-30 13:03 ` 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=1430378466.2400.8.camel@linaro.org \
--to=ivan.ivanov@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pratikp@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
/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).