From: "chaithrika" <chaithrika@ti.com>
To: "'Hans Verkuil'" <hverkuil@xs4all.nl>
Cc: <linux-media@vger.kernel.org>
Subject: RE: vpif_display.c bug
Date: Mon, 10 Aug 2009 18:21:01 +0530 [thread overview]
Message-ID: <024e01ca19b9$36c64c90$a452e5b0$@com> (raw)
In-Reply-To: <200908100807.23455.hverkuil@xs4all.nl>
On Mon, Aug 10, 2009 at 11:37:23, Hans Verkuil wrote:
> Hi Chaithrika,
>
> This code in vpif_display.c is not correct:
>
> for (i = 0; i < subdev_count; i++) {
> vpif_obj.sd[i] = v4l2_i2c_new_probed_subdev(&vpif_obj.v4l2_dev,
> i2c_adap, subdevdata[i].name,
> subdevdata[i].name,
> &subdevdata[i].addr);
> if (!vpif_obj.sd[i]) {
> vpif_err("Error registering v4l2 subdevice\n");
> goto probe_subdev_out;
> }
>
> if (vpif_obj.sd[i])
> vpif_obj.sd[i]->grp_id = 1 << i;
> }
>
> This: '&subdevdata[i].addr' should be: I2C_ADDRS(subdevdata[i].addr).
>
> The list of probe addresses must be terminated by I2C_CLIENT_END (= -1) and
> that isn't the case here.
>
> An alternative solution is to use v4l2_i2c_new_subdev, but then no probing
> will take place. But I think that you don't want probing at all since this
> address information comes from the platform data, so one can assume that
> that data is correct.
>
> Even better is to copy the implementation from vpfe_capture.c and to use
> v4l2_i2c_new_subdev_board().
>
Hans,
Thank you for the suggestions.
I will look into this and submit a patch to correct this bug.
Regards,
Chaithrika
> Regards,
>
> Hans
>
> --
> Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
>
next prev parent reply other threads:[~2009-08-10 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 6:07 vpif_display.c bug Hans Verkuil
2009-08-10 12:51 ` chaithrika [this message]
2009-08-10 15:09 ` Karicheri, Muralidharan
2009-08-11 9:51 ` chaithrika
2009-08-10 15:07 ` Karicheri, Muralidharan
2009-08-11 6:35 ` Hans Verkuil
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='024e01ca19b9$36c64c90$a452e5b0$@com' \
--to=chaithrika@ti.com \
--cc=hverkuil@xs4all.nl \
--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