public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
	Cliff Brake <cbrake@bec-systems.com>
Subject: Re: how fast can you run a hrtimer?
Date: Tue, 22 Aug 2017 18:15:54 +0530	[thread overview]
Message-ID: <20170822124554.GA5898@afzalpc> (raw)
In-Reply-To: <CAOd_LFx5Bn6HtnzD59Hn6feY=ZS3Re+GXHcRU2x2J54cuJDagw@mail.gmail.com>

Hi

> On Fri, Aug 18, 2017 at 8:35 AM, Cliff Brake <cliff.brake@gmail.com> wrote:

> > I have an application where we need to tweak a PWM setting every 10uS.
> > My impression is this is beyond the capabilities of linux+rt, but want
> > to verify I'm not missing anything before we add an external
> > microcontroller to handle this.
> >
> > I've run some experiments on a i.MX6UL with v4.1+rt, and observe
> > delays of ~50us when toggling a GPIO in a Linux driver using a
> > hrtimer.

On Fri, Aug 18, 2017 at 10:34:19AM -0400, Cliff Brake wrote:
> After a suggestion of using a NMI and a bit of research, it seems
> something like the following article is the probably a reasonable
> approach:
> 
> http://free-electrons.com/blog/fiq-handlers-in-the-arm-linux-kernel/

If a PWM IP is present on the chip, won't updating the PWM compare
registers within 10us (PWM @100KHz) achieve the required ?, toggling
delay & jitter shouldn't be a worry here, right ? (assuming PWM
compare registers can be updated every 10us using hrtimers)

afzal

  parent reply	other threads:[~2017-08-22 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 12:35 how fast can you run a hrtimer? Cliff Brake
2017-08-18 14:34 ` Cliff Brake
2017-08-18 14:52   ` Julia Cartwright
2017-08-22 12:45   ` afzal mohammed [this message]
2017-08-22 13:13     ` Cliff Brake

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=20170822124554.GA5898@afzalpc \
    --to=afzal.mohd.ma@gmail.com \
    --cc=cbrake@bec-systems.com \
    --cc=cliff.brake@gmail.com \
    --cc=linux-rt-users@vger.kernel.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