All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alexey Galakhov <agalakhov@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Ipipe hangs on ARM MINI2440 after switching clocksource
Date: Wed, 27 Apr 2011 20:10:32 +0200	[thread overview]
Message-ID: <4DB85C18.5020802@domain.hid> (raw)
In-Reply-To: <BANLkTikmzwturTQNB20eiaOkEYdhEnBmyw@domain.hid>

Alexey Galakhov wrote:
>> There was a bug some time ago, which was fixed for TIMER3, see commit:
>>
>> http://git.xenomai.org/?p=ipipe-gch.git;a=commit;h=ebf2fac4298e25509ba47942b9fad408dcefce1e
>>
> 
> Oh, I know about this bug. That's the first thing I checked. I found that it
> is already fixed in my case. However, it is still unclear for me where the
> correct MUXes for timer4 and timer3 are initialized, seems to be kind of
> magic. I didn't checked TCFGs against the datasheet, going to do it now. I
> also think about making the free-running timer selectable from config since
> some machines may have something wired to timer3's PWM.
> 
> I forgot to say, it works with patched kernel if CONFIG_IPIPE=no. Timers are
> the same in both cases. I don't quite understand, however, how the
> non-working free-running timer may affect the system in that case.
> Interrupts from timer4 are still generated, so the system may boot with
> ipipe off even with broken free-running timer without any obvious problems,
> am I right?

I have absolutely no idea. Fabian Godehart sent the patch, saying that
it fixed an issue, I merged it. That is all.


-- 
                                                                Gilles.


  parent reply	other threads:[~2011-04-27 18:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 13:05 [Adeos-main] Ipipe hangs on ARM MINI2440 after switching clocksource Alexey Galakhov
2011-04-27 15:56 ` Gilles Chanteperdrix
2011-04-27 17:49   ` Alexey Galakhov
2011-04-27 17:55     ` Gilles Chanteperdrix
2011-04-27 18:10     ` Gilles Chanteperdrix [this message]
2011-04-28 11:12   ` Alexey Galakhov
2011-04-28 11:16     ` Gilles Chanteperdrix
2011-04-28 11:24       ` Alexey Galakhov
2011-04-28 11:27         ` Gilles Chanteperdrix
2011-04-28 13:37       ` Alexey Galakhov
2011-04-28 13:47         ` Gilles Chanteperdrix
2011-04-28 16:12       ` Alexey Galakhov
2011-04-28 17:05         ` Gilles Chanteperdrix
2011-04-28 18:43           ` Alexey Galakhov
2011-04-28 19:01             ` Gilles Chanteperdrix
2011-04-28 19:28               ` Alexey Galakhov
2011-04-28 19:32                 ` Gilles Chanteperdrix
2011-04-28 19:47                   ` Alexey Galakhov
2011-04-29  6:44                     ` Gilles Chanteperdrix
2011-04-29  6:49                       ` Gilles Chanteperdrix
2011-04-29 11:08                   ` Alexey Galakhov
2011-04-29 11:32                     ` Gilles Chanteperdrix
2011-04-29 12:08                       ` Alexey Galakhov
2011-04-29 12:14                         ` Gilles Chanteperdrix
2011-04-29 13:09                           ` Alexey Galakhov
2011-04-30  9:55                       ` Gilles Chanteperdrix
2011-04-30 17:33                         ` Alexey Galakhov
2011-04-30 17:39                           ` Alexey Galakhov
2011-04-30 18:41                             ` Alexey Galakhov
2011-04-30 20:14                           ` Gilles Chanteperdrix
2011-04-30 20:28                             ` Alexey Galakhov
2011-04-30 22:01                               ` Gilles Chanteperdrix
2011-04-30 22:36                               ` Gilles Chanteperdrix
2011-05-01 14:23                                 ` Alexey Galakhov
2011-05-01 14:34                                   ` Gilles Chanteperdrix
2011-04-28 18:46           ` Alexey Galakhov
2011-04-28 20:33       ` 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=4DB85C18.5020802@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=agalakhov@domain.hid \
    /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.