LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth.org>
To: Linuxppc-embedded@ozlabs.org
Subject: Re: USB IRQ Handling in IBMSTBx25xx
Date: Sat, 8 Oct 2005 15:26:36 -0700	[thread overview]
Message-ID: <20051008222636.GA816@xyzzy.farnsworth.org> (raw)
In-Reply-To: <8e78982e0510080306n48d9c8b2p858f22bed588f6b9@mail.gmail.com>

On Sat, Oct 08, 2005 at 10:06:36AM +0000, Vijesh VH wrote:
> Has any one worked on Interrupt handling in PPC 405 for STBx25xx. I am
> working in interfacing USB devices for STB. The Device Driver is getting
> stuck or runs unconditional in calling ISR. I Identified that that the
> spin_unlock_irqrestore function call in the kernel does it. So i am unable
> to go ahead and could not find what to do further. If any one is aware or
> worked on this kind of problem plz help me.

On which kernel?

It works for me in linux-2.6.13.

-Dale

      reply	other threads:[~2005-10-08 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08 10:06 USB IRQ Handling in IBMSTBx25xx Vijesh VH
2005-10-08 22:26 ` Dale Farnsworth [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=20051008222636.GA816@xyzzy.farnsworth.org \
    --to=dale@farnsworth.org \
    --cc=Linuxppc-embedded@ozlabs.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