From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: ATMEL camera interface
Date: Wed, 26 May 2010 15:04:31 +0200 [thread overview]
Message-ID: <4BFD1C5F.5060403@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005031836140.4231@axis700.grange>
Hi,
So I have decided to go with the v4l2-subdev API.
I have taken the omapxxcam and vivi.c as exemple, but I have some
questions...
I still don't understand how to register a v4l2 device. I tried to copy
the method from vivi.c using v4l2_device_register but it is not working?
If I just use video_regiter_device, then it is trying to use the default
ioctl and open/close functions from v4l2(v4l2_open) instead of the one I
hae in my driver...
What am I doing wrong?
BR,
Sedji
Le 5/3/2010 6:40 PM, Guennadi Liakhovetski a écrit :
> On Mon, 3 May 2010, Sedji Gaouaou wrote:
>
>> Well sorry to bother you again but I am looking at the mx1_camera.c file, and
>> I wonder where are implemented the queue and dqueue functions?
>>
>> The atmel IP is using linked list for the buffers, and previously I was
>> managing it in the queue and dqueue functions.
>> I am not sure where I should take care of it now?
>
> qbuf and dqbuf are implemented by soc-camera in soc_camera_qbuf() and
> soc_camera_dqbuf() respectively, drivers only implement methods from
> struct videobuf_queue_ops, e.g., a .buf_queue method, which for mx1_camera
> is implemented by mx1_videobuf_queue().
>
> Thanks
> Guennadi
>
>>
>>
>> Regards,
>> Sedji
>>
>> Le 5/3/2010 4:26 PM, Guennadi Liakhovetski a écrit :
>>> On Mon, 3 May 2010, Sedji Gaouaou wrote:
>>>
>>>> Well I need contiguous memory, so I guess I will have a look at
>>>> mx1_camera.c?
>>>> Is there another example?
>>>>
>>>> What do you mean by videobuf implementation? As I said I just need a
>>>> contiguous memory.
>>>
>>> I mean, whether you're gping to use videobuf-dma-contig.c or
>>> videobuf-dma-sg.c, respectively, whether you'll be calling
>>> videobuf_queue_dma_contig_init() or videobuf_queue_sg_init() in your
>>> driver.
>>>
>>> Regards
>>> Guennadi
>>> ---
>>> Guennadi Liakhovetski, Ph.D.
>>> Freelance Open-Source Software Developer
>>> http://www.open-technology.de/
>>>
>>
>>
>
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-05-26 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 15:49 ATMEL camera interface Sedji Gaouaou
2010-04-29 16:35 ` Guennadi Liakhovetski
2010-05-03 13:46 ` Sedji Gaouaou
2010-05-03 14:03 ` Guennadi Liakhovetski
2010-05-03 14:17 ` Sedji Gaouaou
2010-05-03 14:26 ` Guennadi Liakhovetski
2010-05-03 15:39 ` Sedji Gaouaou
2010-05-03 16:40 ` Guennadi Liakhovetski
2010-05-26 13:04 ` Sedji Gaouaou [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=4BFD1C5F.5060403@atmel.com \
--to=sedji.gaouaou@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).