From: Hans Verkuil <hverkuil@xs4all.nl>
To: Benoit Parrot <bparrot@ti.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [Patch v5 1/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver
Date: Mon, 14 Dec 2015 15:41:54 +0100 [thread overview]
Message-ID: <566ED532.6060308@xs4all.nl> (raw)
In-Reply-To: <20151211221633.GF1517@ti.com>
On 12/11/2015 11:16 PM, Benoit Parrot wrote:
> Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote on Thu [2015-Dec-03 11:19:22 -0200]:
>>> +static int cal_enum_framesizes(struct file *file, void *fh,
>>> + struct v4l2_frmsizeenum *fsize)
>>> +{
>>> + struct cal_ctx *ctx = video_drvdata(file);
>>> + const struct cal_fmt *fmt;
>>> + struct v4l2_subdev_frame_size_enum fse;
>>> + int ret;
>>> +
>>> + ctx_dbg(2, ctx, "%s\n", __func__);
>>
>> This s a general note: do you really need tracing-like debug macros
>> all around the code?
>>
>> You could easily check if the functions are called via trace.
>
> True but that also mean to rebuild the kernel in order to
> get to it since function tracing is usually not enabled
> by default.
>
You can enable debugging by doing:
echo 2 >/sys/class/video4linux/video0/dev_debug
See also: Documentation/video4linux/v4l2-framework.txt, section "video device
debugging" for more info.
That's always available and basically does what you want.
Regards,
Hans
next prev parent reply other threads:[~2015-12-14 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 20:47 [Patch v5 0/2] media: v4l: ti-vpe: Add CAL v4l2 camera capture driver Benoit Parrot
2015-11-18 20:47 ` [Patch v5 1/2] " Benoit Parrot
2015-12-03 13:19 ` Mauro Carvalho Chehab
2015-12-11 22:16 ` Benoit Parrot
2015-12-14 14:41 ` Hans Verkuil [this message]
2015-12-15 15:52 ` Mauro Carvalho Chehab
2015-11-18 20:47 ` [Patch v5 2/2] media: v4l: ti-vpe: Document DRA72 CAL h/w module Benoit Parrot
2015-11-19 14:51 ` Rob Herring
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=566ED532.6060308@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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