summaryrefslogtreecommitdiffstats
path: root/sound/Makefile
diff options
context:
space:
mode:
authorJames Courtier-Dutton <James@superbug.co.uk>2005-09-03 12:05:47 +0200
committerJaroslav Kysela <perex@suse.cz>2005-09-12 10:41:07 +0200
commit025cd2f6b1624f536d4df564add3d13ea5022f53 (patch)
tree45086e3e3b82b37b43c2e1189c7c8b99947b43f0 /sound/Makefile
parenta5022b0dc6e45254437b75289e773876bb43e262 (diff)
downloadblackbird-op-linux-025cd2f6b1624f536d4df564add3d13ea5022f53.tar.gz
blackbird-op-linux-025cd2f6b1624f536d4df564add3d13ea5022f53.zip
[ALSA] snd-ca0106, snd-emu10k1: Add symlink in the sys tree.
CA0106 driver,EMU10K1/EMU10K2 driver A thread appeared on the LKML. This patch implements the fix. Question: in sysfs, /sys/bus/*/drivers lists the driver names, with their exported .name (eg. '.name = 'EMU10K1_Audigy'' in the module code, from now on 'driver name'). In /sys/modules, the kernel modules are listed with their module name, eg. snd_emu10k1. However, it seems to me that in sysfs, there is no way in particular to tell, which module has which .name. That is, that snd_emu10k1 is EMU10K1_Audigy and vice versa. I wonder whether it wouldn't be possible to add a symlink to the particular module from the driver, and/or from the module to the driver, so the list of devices handled by the module and the module name would be accessible. This way, I would know which driver name corresponds to which module name and vice versa. Answer: For PCI drivers, just add the line: .owner = THIS_MODULE, to their struct pci_driver definition and you will get the symlink created for you. Signed-off-by: James Courtier-Dutton <James@superbug.co.uk>
Diffstat (limited to 'sound/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud