From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Aurele Traynard <aurele.traynard@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] reading/writing registers
Date: Tue, 03 May 2011 19:36:57 +0200 [thread overview]
Message-ID: <4DC03D39.2040305@domain.hid> (raw)
In-Reply-To: <BANLkTikzGAMXZ--TaxmxXZDsoYJSesC26g@domain.hid>
On 05/03/2011 02:07 PM, Aurele Traynard wrote:
> hello,
>
> I am writing a little test. I put all my RT things in a module : one ISR and
> one RT task.
> in init_module I call :
>
> drv->data.regs = ioremap(0x04000000, 64*1024*1024);
> drv->data.gpio = ioremap(0x40E00000, 64*1024*1024);
> this is to acces registers
>
> rthal_irq_request(8, my_rt_isr, NULL, &(drv->data));
> rthal_irq_enable(8);
> for the ISR
>
> in my interrupt routine I use : writel(1, data->gpio + 0x48); for hardware
> interrupt acknowledge
>
> but when my interrupt routine is called linux is freezing so i think that I
> am never going out of the ISR (I am 99.9% sure).
> I am not sure but I think that It is due to the hardware interrupt
> aknoledge...
>
> my question is :
> can I call "writel(1, data->gpio + 0x48);" in my ISR?
> is it good or not?
> is there an other way to access registers?
>
> thanks for your answers.
>
> PS firstly I was calling : "GEDR0 = 0x1;" but in RT task this macro doesn't
> work
Why is that? What are the symptoms?
Other than that, have a look at:
http://www.xenomai.org/index.php/Request_for_information
--
Gilles.
next prev parent reply other threads:[~2011-05-03 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 12:07 [Xenomai-help] reading/writing registers Aurele Traynard
2011-05-03 17:36 ` Gilles Chanteperdrix [this message]
2011-05-04 7:11 ` Aurele Traynard
2011-05-04 7:23 ` Gilles Chanteperdrix
2011-05-04 8:59 ` Aurele Traynard
2011-05-04 9:25 ` 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=4DC03D39.2040305@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=aurele.traynard@domain.hid \
--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.