From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hamad Kadmany <hkadmany@codeaurora.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [dvb] Problem registering demux0 device
Date: Wed, 07 Dec 2011 09:49:56 -0200 [thread overview]
Message-ID: <4EDF52E4.9090606@redhat.com> (raw)
In-Reply-To: <000001ccb4d3$aab157f0$001407d0$@org>
On 07-12-2011 09:30, Hamad Kadmany wrote:
> Hi,
>
> I'm implementing new adapter for DVB, I built a module to register the
> adapter and demux/net devices. From the kernel log I see all actions are
> performed fine and dvb_register_device (called by dvb_dmxdev_init) is called
> successfully for net0/demux0/dvr0, however, demux0/dvr0 devices do not show
> up, "ls /sys/class/dvb" shows only dvb0.net0 (and nothing appears under
> /dev/dvb/ anyhow).
>
> What could cause not having demux0/dvr0 registered? Note that net0 shows up
> fine.
It is hard to tell the exact problem without looking into the driver. Are you
handling the error codes returned by the register functions?
You can follow what's happening inside your driver by enabling tracepoints.
Here is one of the scripts I used when I need to know what functions are
called:
#!/bin/bash
cd /sys/kernel/debug/tracing
echo disabling trace
echo 0 > tracing_enabled
echo getting funcs
FUNC="`cat /sys/kernel/debug/tracing/available_filter_functions|grep -i drx`"
echo setting functions
echo $FUNC>set_ftrace_filter
echo set trace type
echo function_graph > current_tracer
echo enabling trace
echo 1 > tracing_enabled
(the above enables tracing only for functions with "drx" in the name - you'll
need to tailor it for your specific needs)
Of course, after finishing the device creation, you should disable the trace and
get its results with:
#!/bin/bash
cd /sys/kernel/debug/tracing
echo 0 > tracing_enabled
less trace
I suggest you to compare the trace for a device that is known to create all dvb
nodes with your driver. This may give you a good hint about what is missing on
your driver.
Regards,
Mauro
next prev parent reply other threads:[~2011-12-07 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 8:05 Support for multiple section feeds with same PIDs Hamad Kadmany
2011-12-01 6:23 ` Hamad Kadmany
2011-12-01 11:48 ` Mauro Carvalho Chehab
2011-12-01 13:36 ` Andreas Oberritter
2011-12-01 13:55 ` Hamad Kadmany
2011-12-01 13:57 ` Andreas Oberritter
2011-12-01 14:22 ` Hamad Kadmany
2011-12-01 14:30 ` Andreas Oberritter
2011-12-01 15:57 ` Hamad Kadmany
2011-12-01 16:30 ` Andreas Oberritter
2011-12-07 11:30 ` [dvb] Problem registering demux0 device Hamad Kadmany
2011-12-07 11:49 ` Mauro Carvalho Chehab [this message]
2011-12-07 13:27 ` Hamad Kadmany
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=4EDF52E4.9090606@redhat.com \
--to=mchehab@redhat.com \
--cc=hkadmany@codeaurora.org \
--cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox