Hi folks,
Here's an update to the omap3isp DT support patchset. v1 can be found here:
http://www.spinics.net/lists/linux-media/msg87733.html>
Changes since v1:
patch 10:
- Add Kconfig dependency to MFD_SYSCON
patch 12:
- Rename "lane-polarity" property as "lane-polarities"
patch 13:
- Add
Hi folks,
Here's the first non-RFC version of the omap3isp driver DT support patchset.
It's a sub-set of patches in this RFC set:
http://www.spinics.net/lists/linux-media/msg87263.html>
What has been changed since the RFC set in these patches is roughly:
- The patches have be
Hi Hans, Laurent and others,
This small set fixes a videobuf2 issue related to returning queued buffers
back to the driver. I found it after hopefully fixing a related issue (two
later patches) in the omap3isp driver.
The patchset has been tested up to streamon, but no buffers have been
On Sat, Feb 4, 2012 at 4:26 PM, Enrico wrote:
> On Sat, Feb 4, 2012 at 12:48 PM, Gary Thomas wrote:
>> 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,
On Sat, Feb 4, 2012 at 12:48 PM, Gary Thomas wrote:
> 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 wrote:
>
> O
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 wrote:
On 2012-01-19 06:35, Gary Thomas wrote:
My camera init code is attached. In the previous kern
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 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 wh
Hi Enrico,
On Thursday 19 January 2012 15:17:57 Enrico wrote:
> On Thu, Jan 19, 2012 at 2:52 PM, Gary Thomas 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 t
astructure comes up and all of the devices are created, but I can't
access them.
From the bootup log:
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the omap3isp driver and from the sensor driver ?
No, it doesn't appear that the sensor was probed (or
re created, but I can't
access them.
From the bootup log:
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the omap3isp driver and from the sensor driver ?
No, it doesn't appear that the sensor was probed (or maybe it failed but
no messages). I'
hem to
>>>>>>>>
>>>>>>>>
>>>>>>>> http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp
>>>>>>>> - omap3isp-yuv. Could you please try them, and see if they're usable
>>>
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the omap3isp driver and from the sensor driver ?
No, it doesn't appear that the sensor was probed (or maybe it failed but
no messages). I'll check into this.
Is the omap3-isp driver compiled
On Thu, Jan 19, 2012 at 2:52 PM, Gary Thomas 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 cha
gt;>>>> - omap3isp-yuv. Could you please try them, and see if they're usable
>>>>>> with your sensor ?
>>>>>
>>>>>
>>>>> I just tried this kernel with my board. The media control
>>>>> infrastructure comes
ey're usable
with your sensor ?
I just tried this kernel with my board. The media control
infrastructure comes up and all of the devices are created, but I can't
access them.
From the bootup log:
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the
?
I just tried this kernel with my board. The media control
infrastructure comes up and all of the devices are created, but I can't
access them.
From the bootup log:
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the omap3isp driver and
; >> access them.
> >>
> >> From the bootup log:
> >> Linux media interface: v0.10
> >> Linux video capture interface: v2.00
> >
> > Any message from the omap3isp driver and from the sensor driver ?
>
> No, it doesn't appe
evices are created, but I can't access them.
From the bootup log:
Linux media interface: v0.10
Linux video capture interface: v2.00
Any message from the omap3isp driver and from the sensor driver ?
No, it doesn't appear that the sensor was probed (or maybe it failed but
no me
tructure
> comes up and all of the devices are created, but I can't access them.
>
> From the bootup log:
>Linux media interface: v0.10
>Linux video capture interface: v2.00
Any message from the omap3isp driver and from the sensor driver ?
> When I try to access the d
On 2012-01-17 08:33, Laurent Pinchart wrote:
I already had a couple of YUV support patches in my OMAP3 ISP tree at
git.kernel.org. I've rebased them on top of the lastest V4L/DVB tree and
pushed them to
http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
omap3isp-yuv. Co
manually to comment it this time, but please make sure it gets formatted
properly next time.
On Tuesday 06 December 2011 12:45:51 Abhishek Reddy Kondaveeti wrote:
> Adding YUV input support for Omap3ISp driver, so that we don't need to
> use entire pipeline while working with SOC c
Hi Sriram,
On Tuesday 09 August 2011 19:03:17 Sriram V wrote:
> Hi,
>Does the omap3isp driver implementation support rgb888 format?
No, that's not supported. The driver only support raw sensors. Support for
YUYV sensors could be implemented, but the hardware doesn't support
Hi,
Does the omap3isp driver implementation support rgb888 format?
Regards,
sriram
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Javier,
On Thursday 02 June 2011 15:52:57 javier Martin wrote:
> Hi,
> I'm trying to add VFLIP control to the mt9p031 driver (don't worry
> Guennadi, I won't send the patch yet). For that purpose I've followed
> the code in mt9v032 sensor.
> When I try to query available controls using yavta I
Hi,
I'm trying to add VFLIP control to the mt9p031 driver (don't worry
Guennadi, I won't send the patch yet). For that purpose I've followed
the code in mt9v032 sensor.
When I try to query available controls using yavta I get the following:
root@beagleboard:~# ./media-ctl -e "OMAP3 ISP CCDC output
On Tuesday 10 May 2011 00:04:09 Aguirre, Sergio wrote:
> Hi Everyone,
>
> I'll just like to know if there's someone working with the mainline
> version of the omap3isp driver.
I do :-)
> Ohad (in CC) has some omap3 iommu changes which might affect the
> omap3isp dr
Hi Everyone,
I'll just like to know if there's someone working with the mainline
version of the omap3isp driver.
Ohad (in CC) has some omap3 iommu changes which might affect the
omap3isp driver.
I have been a bit away of the omap3 driver these days, so, if there's
someone else th
27 matches
Mail list logo
