Skip to contentSkip to conversation

Watchdog: i8xx_tco remove pci_find_device

PATCH Wim Van Sebroeck 2 participants 3 messages Jul 19, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Jiri,

Just back from a small holiday, but:

Quoted 5 lines

Watchdog: i8xx_tco remove pci_find_device.

Use refcounting for pci device obtaining. Use PCI_DEVICE macro.

Why the pci_dev_put's? We aren't registering the PCI devices. See the comment above the MODULE_DEVICE_TABLE:
/*
* Data for PCI driver interface
*
* This data only exists for exporting the supported
* PCI ids via MODULE_DEVICE_TABLE. We do not actually
* register a pci_driver, because someone else might one day
* want to register another driver on the same PCI id. */

Since the I/O controller Hub has several functions we explicitely do not register the PCI device...

PS: In the -mm tree there is allready a replacement for this driver... Plan is to get this one into linus tree soon.

Greetings,
Wim.

#2 lore raw

Wim Van Sebroeck napsal(a):

Quoted 1 line

Hi Jiri,

Hi Wim.

Quoted 9 lines

Just back from a small holiday, but:

Quoted 5 lines

Watchdog: i8xx_tco remove pci_find_device.

Use refcounting for pci device obtaining. Use PCI_DEVICE macro.

Quoted 10 lines

Why the pci_dev_put's? We aren't registering the PCI devices. See the comment above the MODULE_DEVICE_TABLE:
/*
* Data for PCI driver interface
*
* This data only exists for exporting the supported
* PCI ids via MODULE_DEVICE_TABLE. We do not actually
* register a pci_driver, because someone else might one day
* want to register another driver on the same PCI id. */

Sure, but it's not registering, but telling the subsystem, we use the device, so that user can't hotunplug it since some driver uses it and reads and writes its registers. It's purpose of refcounting in pci_dev_{put,get}() (pci_dev_get is called in pci_get_device()).

Quoted 5 lines

Since the I/O controller Hub has several functions we explicitely do not register the PCI device...

PS: In the -mm tree there is allready a replacement for this driver... Plan is to get this one into linus tree soon.

This patch is against 2.6.18-rc1-mm2. (Maybe you mean there are some patches coming to -rc2-mm1?)

thanks,

Signature · 4 lines
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
#3 lore raw

Hi Jiri,

Quoted 11 lines
Quoted 10 lines

Why the pci_dev_put's? We aren't registering the PCI devices. See the comment above the MODULE_DEVICE_TABLE:
/*
* Data for PCI driver interface
*
* This data only exists for exporting the supported
* PCI ids via MODULE_DEVICE_TABLE. We do not actually
* register a pci_driver, because someone else might one day
* want to register another driver on the same PCI id. */

Quoted 4 lines

Sure, but it's not registering, but telling the subsystem, we use the device, so that user can't hotunplug it since some driver uses it and reads and writes its registers. It's purpose of refcounting in pci_dev_{put,get}() (pci_dev_get is called in pci_get_device()).

I see now; it's the:
#define for_each_pci_dev(d) while ((d = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, d)) != NULL) that does this. Need to fix that in iTCO_wdt...

Quoted 8 lines
Quoted 5 lines

Since the I/O controller Hub has several functions we explicitely do not register the PCI device...

PS: In the -mm tree there is allready a replacement for this driver... Plan is to get this one into linus tree soon.

This patch is against 2.6.18-rc1-mm2. (Maybe you mean there are some patches coming to -rc2-mm1?)

Nope. iTCO_wdt is going to replace i8xx_tco after testing.

Greetings,
Wim.