linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 03 May 2010 16:17:42 +0200	[thread overview]
Message-ID: <4BDEDB06.9090909@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005031556570.4231@axis700.grange>

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.

Le 5/3/2010 4:03 PM, Guennadi Liakhovetski a écrit :
> On Mon, 3 May 2010, Sedji Gaouaou wrote:
>
>> Hi,
>>
>> I will try to write a soc driver(it seems easier ;)).
>>
>> Are the mx?_camera.c a good starting point?
>
> In principle - yes. But think about one pretty important distinction -
> what videobuf implementation is your driver going to use? Are you going to
> support scatter-gather or only contiguous buffers? If SG - the only such
> example in the mainline is pxa_camera.c. If contiguous - feel free to use
> any one of the rest. Further, mx3_camera uses the dmaengine API, others
> don't. Hope, this will simplify your choice a bit;)
>
> Thanks
> Guennadi
>
>> Regards,
>> Sedji
>>
>> Le 4/29/2010 6:35 PM, Guennadi Liakhovetski a écrit :
>>> Hi Sedji
>>>
>>> On Thu, 29 Apr 2010, Sedji Gaouaou wrote:
>>>
>>>> Hi,
>>>>
>>>> I need to re-work my driver so I could commit it to the community.
>>>> Is there a git tree that I can use?
>>>
>>> Nice to hear that! As far as soc-camera is concerned, the present APIs are
>>> pretty stable. Just use the Linus' git tree, or, if you like, you can use
>>> the v4l-dvb git tree at git://linuxtv.org/v4l-dvb.git. In fact, you don't
>>> have to use the soc-camera API these days, you can just write a complete
>>> v4l2-device driver, using the v4l2-subdev API to interface to video
>>> clients (sensors, decoders, etc.) However, you can still write your driver
>>> as an soc-camera host driver, which would make your task a bit easier at
>>> the cost of some reduced flexibility, it's up to you to decide.
>>>
>>> Thanks
>>> 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

  reply	other threads:[~2010-05-03 14:17 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 [this message]
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

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=4BDEDB06.9090909@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).