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:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1355858365-11849-1-git-send-email-pratikp@codeaurora.org>
[not found] ` <20121219112314.GA26329@mudshark.cambridge.arm.com>
2012-12-19 21:06 ` Pratik Patel
[not found] ` <50D1F37E.6000804@ti.com>
2012-12-19 21:24 ` Pratik Patel
2012-12-20 17:46 ` Jon Hunter
2012-12-20 19:51 ` Pratik Patel
2012-12-20 20:16 ` Jean Pihet
2012-12-21 22:12 ` Pratik Patel
2012-12-20 22:54 ` Jon Hunter
2012-12-20 23:40 ` Russell King - ARM Linux
2012-12-21 22:17 ` Pratik Patel
2012-12-21 22:18 ` Pratik Patel
2012-12-23 11:32 ` Will Deacon [this message]
2013-01-03 18:06 ` Pratik Patel
2013-01-07 11:58 ` Will Deacon
2013-01-16 0:14 ` Pratik Patel
2013-01-17 10:55 ` Will Deacon
2013-01-02 20:00 ` Jon Hunter
2013-01-03 19:32 ` Pratik Patel
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@arm.com \
--cc=arve@android.com \
--cc=christian.bejram@stericsson.com \
--cc=d-deao@ti.com \
--cc=david.rusling@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dsaxena@linaro.org \
--cc=john.stultz@linaro.org \
--cc=jon-hunter@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.p.persson@stericsson.com \
--cc=pratikp@codeaurora.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
Powered by JetHome