linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of ARM FIQ?
Date: Tue, 1 Oct 2013 10:26:30 +0100	[thread overview]
Message-ID: <20131001092623.GA2640@localhost.localdomain> (raw)
In-Reply-To: <F5184659D418E34EA12B1903EE5EF5FD8538E865F6@seldmbx02.corpusers.net>

On Mon, Sep 30, 2013 at 08:48:15PM +0200, Bird, Tim wrote:
> I'm working through some proposals for contract work for the Consumer
> Electronics Workgroup, and one of them involves use of ARM FIQ
> as a debug activator.  I have heard a rumor that FIQ mode is not being
> included in some modern ARM CPUs.
> 
> Is there any truth to this?  Can someone give me a pointer to information
> about this?

All CPUs implement FIQ, except for the M-class CPUS in v7 onwards (which
don't have an MMU, and thus could only run ucLinux).


As to whether you can use FIQ, "it depends":

Since the introduction of the Security Extensions in v6Z / v7,
FIQ can be repurposed as a private interrupt for the Secure World, so
if there is resident Secure World software, it may be impossible for
Linux to use FIQ.

Whether this does or doesn't apply depends on the SoC, and on how
it has been integrated and set up.  Consumer device SoCs, especially
anything coming to you via a mobile provider, will likely have this
restriction.  Dev boards may be a bit more relaxed.


John Stultz has been working on the FIQ debugger for Android and may
have some ideas.

I believe that the Virtualisation extensions allow virtual FIQs to be
delivered to the guest, so that KVM could send fake FIQs to guests even
if the KVM host cannot itself use FIQ.  I'm a bit hazy on this though,
and haven't played with it.

Cheers
---Dave

  parent reply	other threads:[~2013-10-01  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 18:48 Status of ARM FIQ? Bird, Tim
2013-09-30 20:46 ` Florian Fainelli
2013-10-01  7:07 ` Uwe Kleine-König
2013-10-01  9:26 ` Dave Martin [this message]
2013-10-01 16:04   ` Bird, Tim
2013-10-01 16:21     ` John Stultz

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=20131001092623.GA2640@localhost.localdomain \
    --to=dave.martin@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).