From: Gary Thomas <gary@mlbassoc.com>
To: linux-media@vger.kernel.org
Cc: Javier Martinez Canillas <martinez.javier@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Enrico <ebutera@users.berlios.de>
Subject: Re: [PATCH] Adding YUV input support for OMAP3ISP driver
Date: Sat, 04 Feb 2012 04:48:13 -0700 [thread overview]
Message-ID: <4F2D1AFD.1070808@mlbassoc.com> (raw)
In-Reply-To: <4F26D3A4.6010907@mlbassoc.com>
On 2012-01-30 10:30, Gary Thomas wrote:
> On 2012-01-20 05:19, Laurent Pinchart wrote:
>> Hi Enrico,
>>
>> On Thursday 19 January 2012 15:17:57 Enrico wrote:
>>> On Thu, Jan 19, 2012 at 2:52 PM, Gary Thomas<gary@mlbassoc.com> wrote:
>>>> On 2012-01-19 06:35, Gary Thomas wrote:
>>>>> My camera init code is attached. In the previous kernel, the I2C bus was
>>>>> probed implicitly when I initialized the OMAP3ISP. I thought I
>>>>> remembered some discussion about how that worked (maybe changing), so
>>>>> this is probably
>>>>> where the problem starts.
>>>>>
>>>>> If you have an example, I can check my setup against it.
>>>>
>>>> Note: I reworked how the sensor+I2C was initialized to be
>>>> omap3_init_camera(&cobra3530p73_isp_platform_data);
>>>>
>>>> omap_register_i2c_bus(cobra3530p73_isp_platform_data.subdevs->subdevs[0]
>>>> .i2c_adapter_id, 400,
>>>>
>>>> cobra3530p73_isp_platform_data.subdevs->subdevs[0].board_info, 1);
>>>>
>>>> The TVP5150 is now found, but 'media-ctl -p' still dies :-(
>>>
>>> Have a look at [1] (the linux_3.2.bb file to see the list of
>>> patches,inside linux-3.2 directory for the actual patches), it's based
>>> on mainline kernel 3.2 and the bt656 patches i submitted months ago,
>>> it should be easy to adapt it for you board.
>>>
>>> <rant>
>>> Really, there are patches for all these problems since months (from
>>> me, Javier, TI), but because no maintainer cared (apart from Laurent)
>>> they were never reviewed/applied and there is always someone who comes
>>> back with all the usual problems (additional yuv format, bt656 mode,
>>> tvp5150 that doesn't work...).
>>> </rant>
>>
>> I totally understand your feeling.
>>
>> I'd like to get YUV support integrated in the OMAP3 ISP driver. However, I
>> have no YUV image source hardware, so I can only review the patches but not
>> test them.
>>
>> If someone can rebase the existing patches on top of
>> http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
>> omap3isp-yuv and test them, then I'll review the result.
>>
>
> The attached patches produce a working setup against Laurent's tree above.
> That said, I don't recall exactly where which changes came from (I'm old
> school and not very git savvy, sorry). I've CC'd all the folks I think
> provided at least part of these changes. Perhaps we can all work together
> to come up with a proper set of patches which can be pushed upstream
> for this, once and for all?
>
> Thanks
>
Ping! Is no one but me interested in getting these changes into
the mainline?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-02-04 11:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EBE38CF866F2F94F95FA9A8CB3EF2284069CAE@singex1.aptina.com>
2012-01-17 15:33 ` [PATCH] Adding YUV input support for OMAP3ISP driver Laurent Pinchart
2012-01-19 12:41 ` Gary Thomas
2012-01-19 12:50 ` Laurent Pinchart
2012-01-19 13:13 ` Gary Thomas
2012-01-19 13:28 ` Laurent Pinchart
2012-01-19 13:35 ` Gary Thomas
2012-01-19 13:52 ` Gary Thomas
2012-01-19 14:17 ` Enrico
2012-01-20 12:19 ` Laurent Pinchart
2012-01-30 17:30 ` Gary Thomas
2012-02-04 11:48 ` Gary Thomas [this message]
2012-02-04 15:26 ` Enrico
2012-03-08 15:04 ` Enrico
2012-01-19 14:11 ` Javier Martinez Canillas
2012-01-19 14:36 ` Gary Thomas
2012-01-19 16:12 ` Javier Martinez Canillas
2012-01-19 17:08 ` Gary Thomas
2012-01-19 17:22 ` Gary Thomas
2012-01-19 17:39 ` Gary Thomas
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=4F2D1AFD.1070808@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ebutera@users.berlios.de \
--cc=linux-media@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=sakari.ailus@iki.fi \
/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.