public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [omap3camera] Camera bring-up on Zoom3 (OMAP3630)
Date: Wed, 17 Mar 2010 16:58:44 +0200	[thread overview]
Message-ID: <4BA0EE24.7030309@maxwell.research.nokia.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE8944541370C5@dlee02.ent.ti.com>

Aguirre, Sergio wrote:
> 
> 
>> -----Original Message-----
>> From: Sakari Ailus [mailto:sakari.ailus@maxwell.research.nokia.com]
>> Sent: Wednesday, March 17, 2010 9:16 AM
>> To: Laurent Pinchart
>> Cc: Aguirre, Sergio; linux-media@vger.kernel.org
>> Subject: Re: [omap3camera] Camera bring-up on Zoom3 (OMAP3630)
>>
>> Laurent Pinchart wrote:
>>>>>> I'm trying to get latest Sakari's tree (gitorious.org/omap3camera)
>>>>>> 'devel' branch running on my Zoom3 HW (which has an OMAP3630, and a
>>>>>> Sony IMX046 8MP sensor).
>>>>>>
>>>>>> I had first one NULL pointer dereference while the driver was
>>>>>> registering devices and creating entities, which I resolved with
>>>>>> the attached patch. (Is this patch acceptable, or maybe I am missing
>>>>>> something...)
>>>>>
>>>>> Either that, or make OMAP34XXCAM_VIDEODEVS dynamic (the value would be
>>>>> passed through platform data). The code will be removed (hopefully
>> soon)
>>>>> anyway when the legacy video nodes will disappear.
>>>>
>>>> Ok, so should I keep this patch only to myself until this code is
>> removed?
>>>
>>> I'll let Sakari answer that, but I think they can still go in in the
>> meantime.
>>
>> Is there a need for the patch? The other possible device is just left
>> unused, right?
> 
> There is need for it _if_ I don't change OMAP34XXCAM_VIDEODEVS in
> drivers/media/video/omap34xxcam.h, and if I have less devices listed
> in the platform data passed from the boardfile.
> 
> In this case, OMAP34XXCAM_VIDEODEVS is hardcoded to N900 case, which is 2,
> and I only have 1 sensor in my Zoom3.
> 
> I guess the patch is just protecting for potential pointer dereferencing, unless we get rid of current OMAP34XXCAM_VIDEODEVS hardcoded value.

What exactly does not work?

The video devices are registered dynamically based on the number of
sensors available so in this case the second video device is not even
registered.

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  reply	other threads:[~2010-03-17 14:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 14:54 [omap3camera] Camera bring-up on Zoom3 (OMAP3630) Aguirre, Sergio
2010-03-16 22:30 ` Laurent Pinchart
2010-03-17 13:52   ` Aguirre, Sergio
2010-03-17 14:14     ` Laurent Pinchart
2010-03-17 14:16       ` Sakari Ailus
2010-03-17 14:23         ` Laurent Pinchart
2010-03-17 14:23         ` Aguirre, Sergio
2010-03-17 14:58           ` Sakari Ailus [this message]
2010-03-17 15:04             ` Aguirre, Sergio
2010-03-17 20:23               ` Sakari Ailus

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=4BA0EE24.7030309@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.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