From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Xiaoguang Chen <chenxg-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Cc: "grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"robh+dt-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<robh+dt-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: CCI-400 driver ARM V8 support
Date: Mon, 4 Aug 2014 15:33:32 +0100 [thread overview]
Message-ID: <20140804143332.GF3197@leverpostej> (raw)
In-Reply-To: <4737A960563B524DA805CA602BE04B30799875DBE8-r8ILAu4/owtq65YQV0AP9hL4W9x8LtSr@public.gmane.org>
Hi,
On Mon, Aug 04, 2014 at 08:03:18AM +0100, Xiaoguang Chen wrote:
>
> Hi, Grant, Rob
> I'm checking arm cci-400 driver on mainline, and found it only
> supports ARM v7, but no ARM V8 support.
> Do you have plan to support it? or it is under development?
The arm64 port doesn't do any coherency management within the kernel
(this must be done by the firmware or bootloader), so the CCI-400 driver
would be limited to a performance monitoring role.
As far as I am aware, no one is actively working on factoring out the
32-bit dependencies such that the CCI-400 PMU code can be used on arm64.
Thanks,
Mark.
--
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
prev parent reply other threads:[~2014-08-04 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 7:03 CCI-400 driver ARM V8 support Xiaoguang Chen
[not found] ` <4737A960563B524DA805CA602BE04B30799875DBE8-r8ILAu4/owtq65YQV0AP9hL4W9x8LtSr@public.gmane.org>
2014-08-04 14:33 ` Mark Rutland [this message]
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=20140804143332.GF3197@leverpostej \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=chenxg-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robh+dt-QSEj5FYQhm4dnm+yROfE0A@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 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).