public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: linux-kernel@vger.kernel.org
Subject: Re: parport - interrupt sharing possible?
Date: Mon, 12 Jul 2004 11:03:09 -0300	[thread overview]
Message-ID: <20040712140309.GA3755@logos.cnet> (raw)
In-Reply-To: <20040712035119.GA1865@dbz.icequake.net>


On Sun, Jul 11, 2004 at 10:51:19PM -0500, Ryan Underwood wrote:
> 
> Hi,
> 
> Does anyone know if the generic parport interrupt handler is okay (or not)
> for sharing interrupts?  The reason I ask is that I have a PCI parallel
> card with two ports on it.  Without a IRQ sharing capability, it is not
> possible for both of them to operate in interrupt-driven mode.  I tested
> a quick hack to enable IRQ sharing:
> http://home.icequake.net/~nemesis/parport.diff
> 
> and it seems to work okay with both ports in use.  I'm hoping someone
> more knowledgeable on the parallel port subject (Tim Waugh?) can shed
> some light on whether this is acceptable or not.  The interrupt handler
> eventually ends up in parport_ieee1284_interrupt which really doesn't do
> much besides wake up sleepers.
> 
> Thanks!
> 
> PS: Heh, the power just went out and back on as I wrote this.  Giving thanks
> for having multiple UPS units around!

Hi Ryan,

Quoting Tim Waugh:

> 2) Allows PCI parallel port to share an IRQ if possible.  In limited testing
> this seems to be ok, but maybe the interrupt handler was not written for
> sharing.  Someone else will need to ok this.
                                                                                
This seems dangerous to me.  There are some issues with IRQs in
parport, although I think they are known and there is a fix around:
http://lists.infradead.org/pipermail/linux-parport/2004-March/000048.html
                                                                                
Incidentally, I have asked if there is anyone with more time than me
who would like to maintain the paride/parport bits, but no-one has
stepped forward.  I see that Al Viro has fixed a lot of problems while
I've been busy with other things.

      reply	other threads:[~2004-07-12 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12  3:51 parport - interrupt sharing possible? Ryan Underwood
2004-07-12 14:03 ` Marcelo Tosatti [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=20040712140309.GA3755@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.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