On Sat, 12 Mar 2005, Grant Grundler wrote:

> Maybe this would help narrow the search?
> 
> | Date: Tue, 6 Mar 2001 20:20:25 +0300
> | From: Ivan Kokshaysky <[EMAIL PROTECTED]>
> | To: Grant Grundler <[EMAIL PROTECTED]>
> | Cc: linux-kernel@vger.kernel.org
> ...
> | > The other part of the comment I added was:
> | > +** Disabling *all* devices is bad. Console, root, etc get
> | > +** disabled this way.
> | > 
> | > I can't debug with *all* devices disabled.
> | 
> | What is why I leave VGAs and all sorts of bridges enabled.
> | If you have some other type of console sitting on the PCI
> | bus you need this enabled as well, of course.
> ...

Very helpful, thanks.  It appears that the main problem with disabling 
PCI devices as they are discovered lies with devices that are already in 
use (before their drivers have initialized!).  Obviously this can include 
the console.  Any other examples you can point out?  Network devices 
maybe?

What do you think of the idea of setting up a list of devices that the
kernel starts to use early in the boot procedure (without the benefit
of normal drivers)?  The PCI scanning routine could check newly discovered
devices against this list and disable them only if they aren't on it.  
Possibly other buses could make use of such a list as well.

> > Maybe I'll try to put one together.  Can you give me any pointers to
> > examples showing how one prevents a generic PCI device from issuing IRQs?
> 
> call disable_irq(pci_dev->irq).
> But that may only work for line based IRQs.
> May need to do something difference for MSI/MSI-X.
> Off hand, I'm not sure.

Worse than that, it will disable the entire IRQ line, thus affecting other
devices that may be sharing it.  That's not what I want; I need a way to
prevent a generic PCI device from issuing interrupt requests without
affecting other devices sharing the same IRQ.

The idea is that when another device sharing the IRQ is initialized and 
the IRQ is enabled, we won't start getting spurious unhandled interrupt 
requests from the device whose driver isn't initialized yet.

Alan Stern



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to