All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Reitinger, Peter" <preitinger@carl-valentin.de>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] access SPI and DMA hardware from application ("external abort...")
Date: Fri, 15 Aug 2014 17:52:51 +0200	[thread overview]
Message-ID: <53EE2CD3.507@xenomai.org> (raw)
In-Reply-To: <e3bdea6dcdb84852972a720789331cb2@CVEX13.valentin-carl.de>

On 08/15/2014 08:47 AM, Reitinger, Peter wrote:
> Hello,
> 
> meanwhile I have solved the issue on my own. I tried to access the
> SPI1 HW with traditional mmap approach from user space and had the
> same problem until I saw that I had to start the whole SPI1 module by
> setting a specific control bit to enable its clock. Sorry for posting
> this, but I was really puzzled then. I guess it will also be possible
> to access the hw registers of the SPI with the xenomai rtdm io user
> mapping now...

It is normally recommended to implement drivers in kernel-space using
the RTDM API: this forces you to define a standard interface
(open/read/write/ioctl) between application and driver, which makes it
easy to re-use the same driver in a different application, or to
implement a driver for a differrent hardware without changing your
application.

-- 
                                                                Gilles.


  reply	other threads:[~2014-08-15 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1408010401.9958.xenomai@xenomai.org>
2014-08-15  6:47 ` [Xenomai] access SPI and DMA hardware from application ("external abort...") Reitinger, Peter
2014-08-15 15:52   ` Gilles Chanteperdrix [this message]
     [not found]     ` <8a9221baf06e4cf8b7ad859fab3af388@CVEX13.valentin-carl.de>
2014-08-19 20:34       ` 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=53EE2CD3.507@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=preitinger@carl-valentin.de \
    --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.