All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Terje Frøysa" <Terje.Froysa@sintef.no>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] WARNING: at arch/arm/kernel/ipipe.c:157 ipipe_set_irq_affinity+0x47/0x70()
Date: Mon, 1 Dec 2014 12:16:10 +0100	[thread overview]
Message-ID: <20141201111610.GC23220@hermes> (raw)
In-Reply-To: <314E5ECDAA86314791309FA670550F89C9C50321@SINTEFEXMBX05.sintef.no>

On Mon, Dec 01, 2014 at 11:06:58AM +0000, Terje Frøysa wrote:
> Thanks Gilles,
> 
> The Debian/Xenomai was solely chosen as a start-up scenario since I found a good recipe on the net.
> I am heading for Yocto and LFS (Linux From Scratch) for future embedded systems.
> 
> By the way.. When compiling kernel for Xenomai, I am advised to
> turn off CPU Frequency scaling "as it is known to cause trouble".

Yes, for two reasons: 

- because Xenomai timing system is counting on a fixed tsc (and
hardware timer) frequency. In the case of beaglebone, the tsc is
based on the gptimer, so if the gptimer frequency does not change
when changing the processor OPP, this is probably not an issue 

- because the execution time of real-time tasks change, this remains
an issue.


> When enabled I could inspect and set the CPU clock frequency by
> the "cpufreq-info" and "cpufreq-set". These tools are no longer
> available and I don't find any settings in the menuconfig.

These are part of the cpufreq-utils package.

> 
> What is the default BBB CPU frequency when frequency scaling is turned off?

All bets are off. This depends on the kernel implementation. On
OMAP3 (which is closed to BBB, normally), last time I checked (and
that was a long time ago), the kernel does not touch whatever PLL
settings U-boot did, with regard to cpu frequency.

If the kernel provides an access to the PLL settings in /proc, you
can check the various PLL frequencies and look-up in the processor
reference manual to what OPP this corresponds.

-- 
					    Gilles.


  reply	other threads:[~2014-12-01 11:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  5:54 [Xenomai] WARNING: at arch/arm/kernel/ipipe.c:157 ipipe_set_irq_affinity+0x47/0x70() Terje Frøysa
2014-12-01  7:34 ` Gilles Chanteperdrix
2014-12-01  8:26   ` Terje Frøysa
2014-12-01  8:50     ` Gilles Chanteperdrix
2014-12-01 11:06       ` Terje Frøysa
2014-12-01 11:16         ` Gilles Chanteperdrix [this message]
2014-12-01 11:35         ` Hidde Verstoep
2014-12-01 11:39           ` Terje Frøysa
2014-12-01 18:54           ` Gilles Chanteperdrix
2014-12-01 15:19 ` Lennart Sorensen
2014-12-01 15:30   ` Gilles Chanteperdrix
2014-12-01 23:35     ` Lennart Sorensen
2014-12-01 23:37       ` Gilles Chanteperdrix
2014-12-01 23:50         ` Lennart Sorensen
2014-12-01 23:55           ` Gilles Chanteperdrix
2014-12-01 23:57             ` Lennart Sorensen
2014-12-01 15:43   ` Terje Frøysa

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=20141201111610.GC23220@hermes \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Terje.Froysa@sintef.no \
    --cc=xenomai@xenomai.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.