summaryrefslogtreecommitdiff
path: root/linux/drivers/media/dvb/frontends/lgdt330x.c
diff options
context:
space:
mode:
authorAndrew de Quincey <adq_dvb@lidskialf.net>2006-04-10 09:27:37 -0300
committerAndrew de Quincey <adq_dvb@lidskialf.net>2006-04-10 09:27:37 -0300
commitc3bf1b32148a59bc0a8e58c126d642236c7febc1 (patch)
treef4932978021b49311d31c87e514a0a3c42135e84 /linux/drivers/media/dvb/frontends/lgdt330x.c
parente96f69c1735c817cc19e220cb84e0f339190cf1b (diff)
downloadmediapointer-dvb-s2-c3bf1b32148a59bc0a8e58c126d642236c7febc1.tar.gz
mediapointer-dvb-s2-c3bf1b32148a59bc0a8e58c126d642236c7febc1.tar.bz2
Add sysfs device links to dvb devices
From: Andrew de Quincey <adq_dvb@lidskialf.net> Currently in /sys/class/dvb/dvbX.demuxY/ we have: dev uevent With the patch, we have (for a PCI DVB device): dev device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:03:0d.0 uevent So userspace tools can (finally) work out which physical device a DVB adapter refers to. Previously you had to kinda look through dmesg and hope that it hadn't been dumped out of the buffer. This makes debugging a lot easier if the system has been up for a long time! This is done by adding an extra 'struct device *' parameter to dvb_register_adapter(). It will work with any kind of standard linux 'device'. Additionally, if someone has an embedded system which does things differently, they can simply supply 'NULL' and the behaviour will be as before - the link will simply not appear. Signed-off-by: Andrew de Quincey <adq_dvb@lidskialf.net> Ack'd-by: Manu Abraham <manu@linuxtv.org> Acked-by: Michael Krufky <mkrufky@linuxtv.org>
Diffstat (limited to 'linux/drivers/media/dvb/frontends/lgdt330x.c')
0 files changed, 0 insertions, 0 deletions