From: Manu Abraham <abraham.manu@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pci probe
Date: Wed, 13 Jun 2007 11:39:57 +0400 [thread overview]
Message-ID: <466F9F4D.7060003@gmail.com> (raw)
In-Reply-To: <20070529222735.GK4644@kroah.com>
Hi,
Sorry for my late reply.
Greg KH wrote:
>>> - your driver will not work on any pci-hotplug type system (that
>>> includes expresscard and pccard and lots of high-end servers.
>> This doesn't matter
>
> Are you sure? PCI Hotplug is showing up in more places that people
> realize...
The PCI bridges that we have for the mentioned use, does not support
Hotplugging at all and hence doesn't matter for those devices mentioned.
>>> - your driver will not be notified if the system is being
>>> suspended or resumed or wanting to drop into a low power
>>> state.
>>> - another driver can bind to your device without you ever
>>> knowing it.
>> These also sound bad.
>>
>>> So in short, use pci_probe and just handle the fact that you need to be
>>> called for two PCI devices and bind to both of them. It shouldn't be
>>> that hard...
>> Thanks for the explanation.
>>
>> Do you mean to have two PCIID tables ? But then that does mean 2 modules
>> don't you ? (i thought probe would be called once per module) Or you
>> mean to say use PCI_ANY_ID in the table to match multiple devices and
>> then allow probe to return a list of devices ?
>
>
> No, you can specify multiple devices in the same device id table, and
> your driver will get called for all of the matching devices. You just
> need to "bind" them together in your driver to be able to handle
> everything properly. It shouldn't be that tough.
>
Will take a go at it.
I was using PCI_ANY_ID for the device id, so that should return all the
devices.
Thanks,
Manu
prev parent reply other threads:[~2007-06-13 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 19:03 pci probe Manu Abraham
2007-05-15 13:15 ` Manu Abraham
2007-05-16 7:18 ` Greg KH
2007-05-16 12:29 ` Manu Abraham
2007-05-29 22:27 ` Greg KH
2007-06-07 20:00 ` Markus Rechberger
2007-06-13 7:39 ` Manu Abraham [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=466F9F4D.7060003@gmail.com \
--to=abraham.manu@gmail.com \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.