All of lore.kernel.org
 help / color / mirror / Atom feed
From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: Anyone implement Cortex A9 FIQ
Date: Mon, 18 Mar 2013 19:02:58 +0000	[thread overview]
Message-ID: <514764E2.6040101@arm.com> (raw)
In-Reply-To: <CAHrpEqSO89Lx=EGTJJ_XOFwkHqL=heoOUQCtJUzm6D7mEAbWiw@mail.gmail.com>

On 17/03/13 01:15, Frank Li wrote:
> 2013/3/15 Jonathan Austin <jonathan.austin@arm.com>:
>> Hi Frank,
>>
>>
>> On 15/03/13 07:38, Frank Li wrote:
>>>
>>> All:
>>>               Recently, we need real time work run in cortex A9.
>>>               Did anyone use FIQ on Cortex A9?
>>>
>>
>> What are you actually trying to do? There's quite a lot more complexity to
>> being able to do real-time work on an A-class processor than just using FIQ,
>> and much of that would be platform specific. For example on ARMv7A, we
>> generally can't assume that FIQ can be used by the non-secure world...
>
> There are period task run every 125us.
> Task is quick simply, just put virtual multi DMA queue to real DMA queue.
> Small memory copy and set some hardware register.
>

Whether this is feasible will really depend on what platform you're on - 
if there's a secure monitor then FIQs are out of the question anyway. 
Can you tell us more about the system?

If your average interrupt latency is low then you should just be able to 
do this with normal IRQs (have you got threaded interrupt handlers?)

What is it about the situation that leads you to believe that you *need* 
FIQ?

Jonny

  reply	other threads:[~2013-03-18 19:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  7:38 Anyone implement Cortex A9 FIQ Frank Li
2013-03-15 10:46 ` Jonathan Austin
2013-03-17  1:15   ` Frank Li
2013-03-18 19:02     ` Jonathan Austin [this message]
2013-03-19  7:49       ` Frank Li
2013-04-08 16:28         ` Dave Martin
     [not found]           ` <CAHrpEqR35v76qif0wP=1SNOThLvmzpmEHcbehSNoY7-CO0CRqQ@mail.gmail.com>
2013-04-10 11:10             ` Dave Martin

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=514764E2.6040101@arm.com \
    --to=jonathan.austin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.