All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Michael Opdenacker" <michael@free-electrons.com>,
	"Thomas Petazzoni" <thomas@free-electrons.com>,
	"Boris Brezillon" <boris@free-electrons.com>,
	"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
	xenomai@xenomai.org,
	"Antoine Ténart" <antoine@free-electrons.com>
Subject: Re: [Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel
Date: Fri, 06 Jun 2014 19:52:13 +0200	[thread overview]
Message-ID: <5391FFCD.3010505@xenomai.org> (raw)
In-Reply-To: <20140606135912.GJ5765@lukather>

On 06/06/2014 03:59 PM, Maxime Ripard wrote:
> Hi Gilles,
> 
> I've been experimenting these days with the i-pipe 3.14 kernel,
> and current xenomai master branch on the Atmel SAMA5D3 SoC.
> 
> There's a few issues there, the first one being that 
> at91_ipipe_early_init crashes because of a NULL pointer 
> dereference. This is due to the clk_get_rate call on the clock 
> returned by clk_get(NULL, "mck").
> 
> This clk_get call cannot since 3.14 because the clock code has
> been rewritten, and you can't use clkdev anymore.

Well, it works on AT91. (RM9200 and SMA9263). What you are doing with
SAMA5D3 here is actually a port to a new platform.

> 
> This is quite simple to fix, and after actually fixing it, you get
> a more interesting issue: either the timers or the interrupts don't
> work at all.
> 
> The first symptom is that it get stuck at the delay loop 
> calibration. Setting the loops per jiffy in the command line make
> the boot go further, until the switch to the ipipe_tsc clocksource.
> This actually makes me think that it's more the timers that are
> broken rather than the interrupts. Changing the timer counter block
> doesn't solve anything.
> 
> Do you have an idea of what could be going on?

See:
http://www.xenomai.org/index.php/I-pipe-core:ArmPorting


-- 
                                                                Gilles.


  parent reply	other threads:[~2014-06-06 17:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 13:59 [Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel Maxime Ripard
2014-06-06 14:00 ` Maxime Ripard
2014-06-07 14:34   ` Gilles Chanteperdrix
2014-06-10  9:10     ` Maxime Ripard
2014-06-10  9:40     ` Maxime Ripard
2014-06-10  9:48       ` Gilles Chanteperdrix
2014-06-10  9:54         ` Maxime Ripard
2014-06-10 10:01           ` Gilles Chanteperdrix
2014-06-10 10:35             ` Gilles Chanteperdrix
2014-06-11  9:25             ` Maxime Ripard
2014-06-11 18:16               ` Gilles Chanteperdrix
2014-06-11 18:55                 ` Gilles Chanteperdrix
2014-06-12  7:54                 ` Maxime Ripard
2014-06-12  8:37                   ` Gilles Chanteperdrix
2014-06-12 15:03                     ` Maxime Ripard
2014-06-12 17:57                       ` Gilles Chanteperdrix
2014-06-12 22:58                         ` Gilles Chanteperdrix
2014-06-13 19:01                       ` Gilles Chanteperdrix
2014-06-17 17:11                         ` Maxime Ripard
2014-06-23 14:05                         ` Maxime Ripard
2014-06-23 23:44                           ` Gilles Chanteperdrix
2014-06-24  6:13                             ` Gilles Chanteperdrix
2014-06-25 17:14                               ` Maxime Ripard
2014-06-25 17:13                             ` Maxime Ripard
2014-06-25 18:03                               ` Gilles Chanteperdrix
2014-06-06 17:52 ` Gilles Chanteperdrix [this message]
     [not found]   ` <20140606180357.GE5594@piout.net>
2014-06-06 18:13     ` Gilles Chanteperdrix
2014-06-10  8:19   ` Maxime Ripard
2014-06-10  8:48     ` Gilles Chanteperdrix
2014-06-08 13:29 ` Gilles Chanteperdrix

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=5391FFCD.3010505@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=antoine@free-electrons.com \
    --cc=boris@free-electrons.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=michael@free-electrons.com \
    --cc=thomas@free-electrons.com \
    --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.