From: "Erik Andrén" <erik.andren@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: About some sensor drivers in mc5602 gspca driver
Date: Sun, 09 Aug 2009 10:28:09 +0200 [thread overview]
Message-ID: <4A7E8899.7080206@gmail.com> (raw)
In-Reply-To: <4A7E86DF.1070901@gmail.com>
Erik Andrén wrote:
>
> Dongsoo, Nathaniel Kim wrote:
>> Hello,
>>
>> It has been years I've working on linux multimedia drivers, but what a
>> shame I found that there were already sensor drivers that I've already
>> implemented. Precisely speaking, soc camera devices from Samsung named
>> s5k4aa* and s5k83a* were already in Linux kernel and even seems to
>> have been there for years.
>> But a thing that I'm curious is those drivers are totally mc602 and
>> gspca oriented. So some users who are intending to use those samsung
>> camera devices but not using gspca and mc5602 H/W have to figure out
>> another way.
>> As you know, the s5k* camera devices are actually ISP devices which
>> are made in SoC device and can be used independently with any kind of
>> ITU or MIPI supporting host devices.
>> However, I see that gspca and mc5602 have their own driver structure
>> so it seems to be tough to split out the sensor drivers from them.
>> So, how should we coordinate our drivers if a new s5k* driver is
>> getting adopted in the Linux kernel? different version of s5k* drivers
>> in gspca and subdev or gspca also is able to use subdev drivers?
>> I am very willing to contribute several drivers for s5k* soc camera
>> isp devices and in the middle of researching to prepare for
>> contribution those s5k* drivers popped up.
>> Please let me know whether it is arrangeable or not.
>> Cheers,
>>
>
> Hi Nathaniel,
> The sensor sharing question pops up now and then and I'm sure that
> if you search the mailing list archive you can find several threads
> discussing this.
> IIRC the main problem is that in an usb webcam consisting of a
> sensor and an usb bridge. The sensor is often configured in a very
> specific way tied to the particular usb bridge. It is also common
> that much of the initialization is reverse engineered and that we
> may have little or no understanding what we're actually doing.
> (Often just mimicing a windows webcam driver).
> I think the conclusion reached now is that it's not worth the effort
> considering that the sensors usually don't need that much setup to
> get working. Of course this may need to be reevaluated from time to
> time. If someone could device a clever solution I would be all for
> trying to create some kind of driver sharing.
>
> In the gspca-m5602-s5k* case everything is reverse-engineered, as I
> don't possess any datasheets of the ALi m5602 nor the s5k83a,
> s5k4aa. I would be much happy if you Samsung folks would be able to
> provide with me with datasheets for the s5k* sensors.
>
> Best regards,
> Erik
>
Resending due to UTF-8 fail.
>> Nate
>>
>
next prev parent reply other threads:[~2009-08-09 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 7:57 About some sensor drivers in mc5602 gspca driver Dongsoo, Nathaniel Kim
[not found] ` <4A7E86DF.1070901@gmail.com>
2009-08-09 8:28 ` Erik Andrén [this message]
2009-08-09 11:02 ` Dongsoo, Nathaniel Kim
2009-08-09 8:44 ` Hans Verkuil
2009-08-09 11:13 ` Dongsoo, Nathaniel Kim
2009-08-09 12:29 ` 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=4A7E8899.7080206@gmail.com \
--to=erik.andren@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.