From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Steven Scholz" <steven.scholz@imc-berlin.de>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Using ioctl from with the kernel ???
Date: Tue, 12 Nov 2002 16:07:21 +0100 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJCEACCLAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <3DD114B7.EFA6E6CE@imc-berlin.de>
Hello Steven,
Your right IOCTL is not applicable for this. You can simply call the driver
functions directly. If these functions are called different from different
context(s) (like your driver and the IOCTL function) you have to add some
protection mechanism. (The code is not reentrant right?) You may try
spin_lock() for this job (linux/spinlock.h). If you are calling the
functions from interrupt contect too some extra protection is required...
Regards, Stephan
> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Steven
> Scholz
> Sent: Dienstag, 12. November 2002 15:48
> To: LinuxPPC
> Subject: Using ioctl from with the kernel ???
>
>
>
> Hi there,
>
> I use a device driver (/dev/status_led from DENX) to manipulate
> some frontpanel
> LEDs from user space via some ioctls.
>
> Now I'd like to access them from the kernel space. How can I do
> that? AFAIK I
> can't use fopen and ioctl...
>
> Thanks,
>
> Steven
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-12 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 14:48 Using ioctl from with the kernel ??? Steven Scholz
2002-11-12 15:07 ` Stephan Linke [this message]
2002-11-12 15:11 ` Steven Scholz
2002-11-12 15:36 ` R: " Stefano Coluccini
2002-11-12 15:57 ` Stephan Linke
2002-11-12 16:05 ` Steven Scholz
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=FCEAKDJJAPHPLJFINDAJCEACCLAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).