From: jon-hunter@ti•com (Jon Hunter)
To: linux-arm-kernel@lists•infradead.org
Subject: Coresight bus and drivers from CodeAurora
Date: Wed, 12 Dec 2012 15:50:44 -0600 [thread overview]
Message-ID: <50C8FC34.3010505@ti.com> (raw)
In-Reply-To: <CACRpkdYYhAyLXJL6ns5mfFQOethihabfPpPuqz9Unq_SCJqLig@mail.gmail.com>
On 12/12/2012 02:00 AM, Linus Walleij wrote:
> On Tue, Dec 11, 2012 at 10:39 PM, Pratik Patel <pratikp@codeaurora•org> wrote:
>
>> Thanks for the quick evaluation. I will be working on cleaning up
>> the drivers for upstream submission in the coming weeks.
>
> This is exactly what I like to hear :-)
>
> Can you preserver the CC line from this mail on your subsequent
> posts so the involved experts can follow the discussions?
>
> It seems like keeping this new framework in drivers/ and actually refactoring
> the old stuff in arch/arm/kernel/etm.c etc is the way forward, but doing that
> may require some patch to support the old style of things. As the older code
> may be stale maybe just depend on !CONFIG_OC_ETM is a way forward.
I have also been working to migrate the coresight cross-trigger
interface (CTI) helpers from Ming Lei to a driver [1]. In the current
implementation I have opted to make the CTI driver an AMBA device (like
the existing ETM and ETB drivers). Therefore, I am curious if the plan
is to migrate these other coresight devices to AMBA versus adding this
new coresight bus?
It would be good to align on a plan here for coresight devices in general.
Cheers
Jon
[1] https://github.com/jonhunter/linux/commits/dev-cti
next prev parent reply other threads:[~2012-12-12 21:50 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
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 [this message]
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=50C8FC34.3010505@ti.com \
--to=jon-hunter@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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