From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: jean-philippe francois <jp.francois@cynove.com>
Cc: linux-media <linux-media@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: omap3-isp : panic using previewer from V4L input
Date: Wed, 15 May 2013 03:32:43 +0200 [thread overview]
Message-ID: <1579245.NgheaxZSaI@avalon> (raw)
In-Reply-To: <CAGGh5h0eAdk+2pHcNn+xBgpvWmGgTa87_WN5GP-64Gexm-oK_Q@mail.gmail.com>
Hi Jean-Philippe,
On Tuesday 14 May 2013 11:29:39 jean-philippe francois wrote:
> Hi Laurent,
>
> I have a beagle xm board, but no sensor board. Is it possible to have
> the omap3-isp initialised ?
Yes it is. You will just need to call omap3_init_camera() in your board code
with a pointer to platform data that contain an empty list of subdevs.
Something like
static struct isp_v4l2_subdevs_group beagle_camera_subdevs[] = {
{ },
};
static struct isp_platform_data beagle_isp_platform_data = {
.subdevs = beagle_camera_subdevs,
};
static int __init beagle_camera_init(void)
{
if (!machine_is_omap3_beagle())
return 0;
omap3_init_camera(&beagle_isp_platform_data);
return 0;
}
late_initcall(beagle_camera_init);
should do (you will also need to include the appropriate headers).
> I would like to try my program on a beagle board to eliminate any
> hardware related problem.
> From the board file in mainline kernel, it seems omap3_init_camera is
> not called, do you know any kernel tree where isp is initialized for beagle
> board ?
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-05-15 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 8:59 omap3-isp : panic using previewer from V4L input jean-philippe francois
2013-05-07 11:56 ` Laurent Pinchart
2013-05-07 12:41 ` jean-philippe francois
2013-05-14 9:29 ` jean-philippe francois
2013-05-15 1:32 ` Laurent Pinchart [this message]
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=1579245.NgheaxZSaI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jp.francois@cynove.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@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