Skip to contentSkip to conversation

pci_[g|s]et_drvdata() versus ->driver_data

DISCUSSION David KOENIG 2 participants 2 messages Oct 19, 2006

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is there any reason for some drivers that I should leave references as foo->driver_data instead of pci_get_drvdata(foo)? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFN8TLmhCgVPlWJY8RAv4lAJ9VrJg+DlXt+AMvVBBbMSgl/3UqzgCgpynk cGm7n7hfEdgWZQxZ0qeXhqE=
=0KXz
-----END PGP SIGNATURE-----

#1 lore raw
Quoted 2 lines · David KOENIG

Is there any reason for some drivers that I should leave references as foo->driver_data instead of pci_get_drvdata(foo)?

When "foo" is not a struct pci_dev ?

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core