From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Coresight bus and drivers from CodeAurora
Date: Mon, 10 Dec 2012 18:18:40 +0000 [thread overview]
Message-ID: <20121210181840.GI12030@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CACRpkdYeFw3YqYqgNAKUv1U4edyzzUa9x6xBSoBU4BbBoc6q5Q@mail.gmail.com>
Hi Linus,
On Mon, Dec 10, 2012 at 12:40:20PM +0000, Linus Walleij wrote:
> recently my colleague Magnus (@ST-Ericsson) found this bus and
> implementations for the ARM Coresight and drivers for the ARM Coresight
> blocks ETB, ETM, Funnel, Replicator, STM, TMC and TPIU. The
> code is here:
> https://www.codeaurora.org/gitweb/quic/le/?p=kernel/msm.git;a=tree;f=drivers/coresight;h=f0221ea9a55c1e8bcd63f36ec28abb6d5406e63d;hb=refs/heads/msm-3.4
>
> What is your intention with this? Do you have any intention to mainline?
>
> We can see it has references to Qualcomm in the device tree strings even
> though they are ARM Coresight HW blocks, for example, so some changes
> are likely necessary, and such bindings should pass the devicetree-discuss
> list.
>
> Will: what is ARM Ltd. position on these blocks and their drivers? Any plans
> from your side?
>
>From what I understand, ARM has looked at the idea of self-hosted tracing
using Coresight but we couldn't find a compelling use-case and, as such,
don't currently have any plans in this area.
That's not to say it's been written off if somebody has good use for it.
What exactly is your use-case and why is there yet another driver on the
cards? I have some personal opinions about what we should/shouldn't do in
this space, but that can come later.
> The design is nice, but maybe this is one of the few cases where the
> drivers should actually live under arch/arm/common/* or similar.
Well, if the code is useful on arm64 then a directory outside of arch/ could
be beneficial.
Cheers,
Will
next prev parent reply other threads:[~2012-12-10 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 12:40 Coresight bus and drivers from CodeAurora Linus Walleij
2012-12-10 18:18 ` Will Deacon [this message]
2012-12-10 19:52 ` Paul Walmsley
2012-12-11 21:39 ` Pratik Patel
2012-12-12 8:00 ` Linus Walleij
2012-12-12 21:50 ` Jon Hunter
2012-12-13 7:46 ` Pratik Patel
2012-12-13 10:49 ` Will Deacon
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=20121210181840.GI12030@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).