linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@lvl7.com>
To: Khai Trinh <kqtrinh@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: inter-driver communication
Date: Thu, 18 Jul 2002 19:35:23 -0400	[thread overview]
Message-ID: <3D3750BB.9070503@lvl7.com> (raw)
In-Reply-To: 20020717212758.16528.qmail@web11505.mail.yahoo.com


I'm not sure if an interrupt is exactly what you want here.  If you want to
facilitate communication between drivers I think that tasklets do the job fairly
well.  All you really need to do is have the destination driver export a
tasklet_struct that the source driver can reference as an external variable.
Then if you want the source driver to signal the destination driver to do
something, all it needs to do is call schedule_tasklet on the exported structure.
Hope that helps
Neil

Khai Trinh wrote:

> Hi folks,
>
> Are there ways in the linux kernel that allows
> driver-driver communications (ie: one driver
> interrupts another driver in an embedded application)?
>
> I have a driver that handles one device. When it is
> interrupted, I would like then to interrupt the other
> driver to handle the interrupt request?
>
> Any suggestion is welcome and appreciated.
>
> Thanks,
> --Khai
>
>
>


--
/******************************************************************
*Neil Horman
*Software Engineer
*LVL7 Systems
*13000 Weston Pkwy.
*Cary, NC 27513
*(919)-865-2915
*nhorman@lvl7.com
*PGP keyID 0xB5E1020A
*http://www.keyserver.net/en
*******************************************************************/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-07-18 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 21:27 inter-driver communication Khai Trinh
2002-07-18 23:35 ` Neil Horman [this message]

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=3D3750BB.9070503@lvl7.com \
    --to=nhorman@lvl7.com \
    --cc=kqtrinh@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).