linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Nageswari S <nageswari@sanyo.co.in>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: USB - Interrupt problem
Date: Mon, 18 Nov 2002 08:11:24 -0700	[thread overview]
Message-ID: <20021118081124.B31148@home.com> (raw)
In-Reply-To: <6DF87017DA95D611AC6000606730DE9B1B51D5@BLREXSR>; from nageswari@sanyo.co.in on Mon, Nov 18, 2002 at 11:56:04AM +0530


On Mon, Nov 18, 2002 at 11:56:04AM +0530, Nageswari S wrote:
> but, there is no change in interrupts when I connect a USB device.
> cat /proc/interrupts output is
>
>
>            CPU0
>   2:     119608  405IAP UIC Edge      NE2000
>  11:          1  405IAP UIC Edge      usb-ohci
>  29:        604  405IAP UIC Edge      keyboard
> BAD:          0
>
> Also, whatever device I connect, it does not get listed in
> /proc/bus/usb/devices
> Could anybody please tell me as to where the problem is regarding the
> interrupts.
>
>
> Any help or suggestion would be very helpful....

Couple options off the top of my head:

1) Check your triggering/polarity for the ohci device.  Are you
   sure the UIC is set correctly for this device?  Is this something
   custom hanging off the ebc?

2) You have a bug in your custom ohci HCI driver which causes it
   to stall before device insertion.  Verify whatever status register
   ohci has that it is still running (I dunno, only know uhci stuffs
   here).

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

      reply	other threads:[~2002-11-18 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  6:26 USB - Interrupt problem Nageswari S
2002-11-18 15:11 ` Matt Porter [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=20021118081124.B31148@home.com \
    --to=porter@cox.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nageswari@sanyo.co.in \
    /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).