From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Poirier Subject: Re: [PATCH 1/2] coresight: replicator: Add Qualcomm CoreSight Replicator driver Date: Thu, 30 Apr 2015 07:07:42 -0600 Message-ID: References: <1430310000-10867-1-git-send-email-ivan.ivanov@linaro.org> <1430310000-10867-2-git-send-email-ivan.ivanov@linaro.org> <1430378466.2400.8.camel@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1430378466.2400.8.camel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Ivan T. Ivanov" Cc: Kumar Gala , Pratik Patel , Catalin Marinas , Will Deacon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org On 30 April 2015 at 01:21, Ivan T. Ivanov wrote: > > On Wed, 2015-04-29 at 10:28 -0600, Mathieu Poirier wrote: >> On 29 April 2015 at 06:19, Ivan T. Ivanov ivanov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote: > > > >> > - "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. amba_id work well for devices within the same family and compatible up to a certain point. When revisions change backward compatibility is usually not kept and it becomes a nightmare to maintain. > >> > * 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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html