From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Pratik Patel <pratikp-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"magnus.p.persson-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org"
<magnus.p.persson-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
"david.rusling-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<david.rusling-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org"
<arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"dsaxena-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<dsaxena-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"d-deao-l0cyMroinI0@public.gmane.org"
<d-deao-l0cyMroinI0@public.gmane.org>,
"christian.bejram-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org"
<christian.bejram-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: CoreSight framework and drivers
Date: Sun, 23 Dec 2012 11:32:39 +0000 [thread overview]
Message-ID: <20121223113239.GG16237@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121221221828.GA2658-9H3kiKr51/JHGpnEYu0o6d07Fnf2crXX0E9HWUfgJXw@public.gmane.org>
On Fri, Dec 21, 2012 at 10:18:28PM +0000, Pratik Patel wrote:
> What user interface do you plan to provide for the CTI? Maybe
> something consistent with other CoreSight components in sysfs to
> allow users to enable, disable, map and unmap ???
>
> Please let me know your thoughts.
Rather than have your current approach of dev nodes + sysfs config files for
each coresight device, I think it might be better to follow something closer
to ftrace and stick per-device directories under debugfs/coresight/. Then you
can have a pipe file and some config files in the same directory for each
component. You also don't need to do any mapping operations with this (just
post-process the stream directly).
It might also be fun to play with file redirection for sources and sinks, but
that's probably a bit too invasive.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: CoreSight framework and drivers
Date: Sun, 23 Dec 2012 11:32:39 +0000 [thread overview]
Message-ID: <20121223113239.GG16237@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121221221828.GA2658@pratikp-linux.qualcomm.com>
On Fri, Dec 21, 2012 at 10:18:28PM +0000, Pratik Patel wrote:
> What user interface do you plan to provide for the CTI? Maybe
> something consistent with other CoreSight components in sysfs to
> allow users to enable, disable, map and unmap ???
>
> Please let me know your thoughts.
Rather than have your current approach of dev nodes + sysfs config files for
each coresight device, I think it might be better to follow something closer
to ftrace and stick per-device directories under debugfs/coresight/. Then you
can have a pipe file and some config files in the same directory for each
component. You also don't need to do any mapping operations with this (just
post-process the stream directly).
It might also be fun to play with file redirection for sources and sinks, but
that's probably a bit too invasive.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Pratik Patel <pratikp@codeaurora.org>
Cc: Jon Hunter <jon-hunter@ti.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"magnus.p.persson@stericsson.com"
<magnus.p.persson@stericsson.com>,
"david.rusling@linaro.org" <david.rusling@linaro.org>,
"arve@android.com" <arve@android.com>,
"dsaxena@linaro.org" <dsaxena@linaro.org>,
"john.stultz@linaro.org" <john.stultz@linaro.org>,
"d-deao@ti.com" <d-deao@ti.com>,
"christian.bejram@stericsson.com"
<christian.bejram@stericsson.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: CoreSight framework and drivers
Date: Sun, 23 Dec 2012 11:32:39 +0000 [thread overview]
Message-ID: <20121223113239.GG16237@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121221221828.GA2658@pratikp-linux.qualcomm.com>
On Fri, Dec 21, 2012 at 10:18:28PM +0000, Pratik Patel wrote:
> What user interface do you plan to provide for the CTI? Maybe
> something consistent with other CoreSight components in sysfs to
> allow users to enable, disable, map and unmap ???
>
> Please let me know your thoughts.
Rather than have your current approach of dev nodes + sysfs config files for
each coresight device, I think it might be better to follow something closer
to ftrace and stick per-device directories under debugfs/coresight/. Then you
can have a pipe file and some config files in the same directory for each
component. You also don't need to do any mapping operations with this (just
post-process the stream directly).
It might also be fun to play with file redirection for sources and sinks, but
that's probably a bit too invasive.
Will
next prev parent reply other threads:[~2012-12-23 11:32 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 19:19 CoreSight framework and drivers pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp
2012-12-18 19:19 ` [RFC 1/8] coresight: add CoreSight core layer framework pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-18 19:19 ` [RFC 2/8] coresight: add CoreSight TMC driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2013-02-21 14:20 ` Robert MARKLUND
2013-02-21 14:20 ` Robert MARKLUND
2012-12-18 19:19 ` [RFC 3/8] coresight: add CoreSight TPIU driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-18 19:19 ` [RFC 4/8] coresight: add CoreSight ETB driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-20 17:49 ` Jon Hunter
2012-12-20 17:49 ` Jon Hunter
2012-12-20 19:54 ` Pratik Patel
2012-12-20 19:54 ` Pratik Patel
2012-12-18 19:19 ` [RFC 5/8] coresight: add CoreSight Funnel driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-18 19:19 ` [RFC 6/8] coresight: add CoreSight Replicator driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-18 19:19 ` [RFC 7/8] coresight: add CoreSight STM driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-18 19:19 ` [RFC 8/8] coresight: add CoreSight ETM driver pratikp at codeaurora.org
2012-12-18 19:19 ` pratikp-sgV2jX0FEOL9JmXXK+q4OQ
2012-12-19 11:23 ` CoreSight framework and drivers Will Deacon
2012-12-19 11:23 ` Will Deacon
2012-12-19 17:03 ` Jon Hunter
2012-12-19 17:03 ` Jon Hunter
2012-12-19 21:24 ` Pratik Patel
2012-12-19 21:24 ` Pratik Patel
2012-12-20 17:46 ` Jon Hunter
2012-12-20 17:46 ` Jon Hunter
2012-12-20 17:46 ` Jon Hunter
2012-12-20 19:51 ` Pratik Patel
2012-12-20 19:51 ` Pratik Patel
2012-12-20 20:16 ` Jean Pihet
2012-12-20 20:16 ` Jean Pihet
2012-12-21 22:12 ` Pratik Patel
2012-12-21 22:12 ` Pratik Patel
2012-12-20 22:54 ` Jon Hunter
2012-12-20 22:54 ` Jon Hunter
2012-12-20 22:54 ` Jon Hunter
2012-12-20 23:40 ` Russell King - ARM Linux
2012-12-20 23:40 ` Russell King - ARM Linux
2012-12-21 22:17 ` Pratik Patel
2012-12-21 22:17 ` Pratik Patel
2012-12-21 22:18 ` Pratik Patel
2012-12-21 22:18 ` Pratik Patel
[not found] ` <20121221221828.GA2658-9H3kiKr51/JHGpnEYu0o6d07Fnf2crXX0E9HWUfgJXw@public.gmane.org>
2012-12-23 11:32 ` Will Deacon [this message]
2012-12-23 11:32 ` Will Deacon
2012-12-23 11:32 ` Will Deacon
2013-01-03 18:06 ` Pratik Patel
2013-01-03 18:06 ` Pratik Patel
[not found] ` <20130103180643.GA30277-9H3kiKr51/JHGpnEYu0o6d07Fnf2crXX0E9HWUfgJXw@public.gmane.org>
2013-01-07 11:58 ` Will Deacon
2013-01-07 11:58 ` Will Deacon
2013-01-07 11:58 ` Will Deacon
2013-01-16 0:14 ` Pratik Patel
2013-01-16 0:14 ` Pratik Patel
2013-01-17 10:55 ` Will Deacon
2013-01-17 10:55 ` Will Deacon
2013-01-02 20:00 ` Jon Hunter
2013-01-02 20:00 ` Jon Hunter
2013-01-02 20:00 ` Jon Hunter
2013-01-03 19:32 ` Pratik Patel
2013-01-03 19:32 ` Pratik Patel
2012-12-19 21:06 ` Pratik Patel
2012-12-19 21:06 ` Pratik Patel
2013-02-21 14:32 ` Robert MARKLUND
2013-02-21 14:32 ` Robert MARKLUND
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=20121223113239.GG16237@mudshark.cambridge.arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=arve-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=christian.bejram-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=d-deao-l0cyMroinI0@public.gmane.org \
--cc=david.rusling-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dsaxena-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=magnus.p.persson-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=pratikp-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.