Hi All:
I've been playing with the mt9p031 for some time now. Last weekend
I got the raw 12 bit data dump I've been wanting for some time. As of
now the module I'm using only works if it is included in the kernel. I
cannot obtain functionality or enumeration on the i2c bus if I insert
it as a m
Omar Ramirez Luna writes:
> Use runtime PM functionality interfaced with hwmod enable/idle
> functions, to replace direct clock operations, reset and sysconfig
> handling.
>
> Tidspbridge uses a macro removed with this patch, for now the value
> is hardcoded to avoid breaking compilation.
>
> Sig
Omar Ramirez Luna writes:
> Add mmu hwmod data for ipu and dsp.
>
> Signed-off-by: Omar Ramirez Luna
[...]
> +static struct omap_hwmod omap44xx_ipu_mmu_hwmod = {
> + .name = "ipu_mmu",
> + .class = &omap44xx_mmu_hwmod_class,
> + .mpu_irqs = omap44xx_ipu_mmu
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date:Fri Nov 4 19:00:22 CET 2011
git hash:31cea59efb3a4210c063f31c061ebcaff833f583
gcc version: i686-linux-gcc (GCC
Commit:
6497e3cb61ca555969a35ab68b477db34ee2
[media] tvp5150: Add video format registers configuration values
Added constants for each video standard supported by TVP5150, so this patch
get rid of the magic numbers.
Signed-off-by: Javier Martinez Canillas
---
drivers/media/video/tvp5150.c |
Hi Laurent,
On 11/04/2011 11:43 AM, Laurent Pinchart wrote:
> On Wednesday 02 November 2011 17:15:57 Sylwester Nawrocki wrote:
...
>> diff --git a/drivers/media/video/v4l2-subdev.c
>> b/drivers/media/video/v4l2-subdev.c index 179e20e..4fe1e7a 100644
>> --- a/drivers/media/video/v4l2-subdev.c
>> ++
On 11/04/2011 02:07 PM, Jonghun Han wrote:
Hi,
Hi Mr. Han,
I'm not sure the meaning of variables in v4l2_pix_format and v4l2_plane.
Especially bytesperline, sizeimage, length and bytesused.
v4l2_pix_format.width = width
v4l2_pix_format.height = height
The fields width
On Friday 04 November 2011 14:28:48 Marek Szyprowski wrote:
> Hello,
>
> On Friday, November 04, 2011 2:08 PM Jonghun Han wrote:
> > I'm not sure the meaning of variables in v4l2_pix_format and v4l2_plane.
> > Especially bytesperline, sizeimage, length and bytesused.
> >
> > v4l2_pix_format.width
Minimum vertical pixel size alignment for input and output DMA and
the scaler depend on color format, rotation, the IP instance and revision.
Make vertical pixel size of format and crop better fit for each SoC
revision and the IP instance by adding min_vsize_align attribute to
the FIMC variant dat
When a sensor with MIPI-CSI interface is attached through platform
data definition and the MIPI-CSI receiver is not selected in kernel
configuration s5p-fimc driver probe() will now succeed, issuing only
a warning. It was done this way to allow the driver to work even if
system configuration is not
With 16-bit RGB565 colour format pixels are stored by the device in memory
in the following order:
| b3 | b2 | b1 | b0 |
~+-+-+-+-+
| R5 G6 B5 | R5 G6 B5 |
This corresponds to V4L2_PIX_FMT_RGB565 fourcc, not V4L2_PIX_FMT_RGB565X.
This change is required to avoid t
The "s5p-fimc-md" platform device platform_data is used to pass
attached camera sensor data. Not allowing device probe() to succeed
when it's null prevents using FIMC as a mem-to-mem device only.
Fix this by removing the platform_data check against null and
registering sensors only if platform_data
After i2c_unregister_device() has been called the client object can already
be freed and thus using the client pointer may lead to dereferencing freed
memory. Avoid this by saving the adapter pointer for further use before
i2c_unregister_device() call.
Signed-off-by: Sylwester Nawrocki
Signed-off
Make sure the subdev pointer is cleared when the subdev object
has been freed.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/s5p-fimc/fi
When requested more than 2 buffers the buffer dequeue order was wrong
due to erroneous updating FIMC registers in every interrupt handler
call. This also fixes regression of resetting the output DMA buffer
pointer at wrong time, when some buffers are already queued in hardware.
The hardware is rese
ST_LPM bit must not be initially set, so the first resume helper
call properly quiesce the device's operation.
Also fimc_runtime_suspend() at device remove is unneeded and
leads to unbalanced clock disable so remove it.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/
The following is a bunch of bug fixes/improvements for s5p-fimc driver.
Sylwester Nawrocki (8):
s5p-fimc: Fix wrong pointer dereference when unregistering sensors
s5p-fimc: Fix error in the capture subdev deinitialization
s5p-fimc: Fix initialization for proper system suspend support
s5p-
Hello,
On Friday, November 04, 2011 2:08 PM Jonghun Han wrote:
> I'm not sure the meaning of variables in v4l2_pix_format and v4l2_plane.
> Especially bytesperline, sizeimage, length and bytesused.
>
> v4l2_pix_format.width = width
> v4l2_pix_format.height= height
> v4l2_
Mauro,
Could you still try PULL some rather small Anysee changes for 3.2 I have
requested two weeks ago?
http://patchwork.linuxtv.org/patch/8182/
Those are Common Interface support and new board layout for Anysee E7 T2C.
Antti
On 11/04/2011 02:18 PM, Mauro Carvalho Chehab wrote:
Hi Linus,
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
v4l_for_linus
For:
- move cx25821 out of staging;
(acked by Greg KH)
- move the remaining media staging drivers to drivers/staging/media;
(acked by Greg KH)
Hi,
I'm not sure the meaning of variables in v4l2_pix_format and v4l2_plane.
Especially bytesperline, sizeimage, length and bytesused.
v4l2_pix_format.width = width
v4l2_pix_format.height = height
v4l2_pix_format.bytesperline= bytesperline [in bytes]
v4l2_pix_format.sizeim
GET_RES request support is mandatory for extension units, but some
cameras still choke on it (one example is the Logitech QuickCam PTZ that
returns a single byte for the PTZ relative control instead of four).
Signed-off-by: Laurent Pinchart
---
drivers/media/video/uvc/uvc_ctrl.c | 17 +
The camera requires the PROBE_MINMAX quirk. Add a corresponding entry in
the device IDs list.
Signed-off-by: Laurent Pinchart
---
drivers/media/video/uvc/uvc_driver.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/uvc/uvc_driver.c
b/drivers/
Inside of skipping the payload completely, which would make the
resulting image corrupted anyway, store the payload normally and mark
the buffer as erroneous. If the no_drop module parameter is set to 1 the
buffer will then be passed to userspace, and tt will then be up to the
application to decide
The macros are defined in both drivers/media/video/uvc/uvc_video.c and
include/linux/usb/video.h. Remove definitions from the former.
Signed-off-by: Laurent Pinchart
---
drivers/media/video/uvc/uvc_video.c | 10 --
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/drivers
The function is not used outside of its compilation unit. Make it
static.
Signed-off-by: Laurent Pinchart
---
drivers/media/video/uvc/uvc_video.c |4 ++--
drivers/media/video/uvc/uvcvideo.h |2 --
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/media/video/uvc/uvc
Turn streaming off (by selecting alternate setting 0) and disable the
video buffers queue in the uvc_video_enable() error path.
Signed-off-by: Laurent Pinchart
---
drivers/media/video/uvc/uvc_video.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/media/v
Hi everybody,
Here are miscellaneous fixes that were sleeping in dark corners of my git
trees. They're pretty straightforward, and I intend to push them to v3.3.
The patches are based on top of the videobuf2 conversion patches that I've
previously posted to the list. As I haven't received any com
Hi Chris,
On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote:
> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my
> beagleboard-xm.
>
> I'm interested in the media controller framework, which I believe is
> in this kernel.
Yes it is.
> I expected there to be a /dev/me
Hi Hans,
On Friday 04 November 2011 11:58:26 Hans Verkuil wrote:
> On Friday 04 November 2011 11:41:28 Laurent Pinchart wrote:
> > On Wednesday 02 November 2011 17:33:16 javier Martin wrote:
> > > On 2 November 2011 17:12, Devin Heitmueller wrote:
> > > > I've actually got a very similar issue and
On Friday 04 November 2011 11:41:28 Laurent Pinchart wrote:
> Hi Javier,
>
> On Wednesday 02 November 2011 17:33:16 javier Martin wrote:
> > On 2 November 2011 17:12, Devin Heitmueller wrote:
> > > I've actually got a very similar issue and have been looking into it
> > > (an em28xx device on OMAP
Em 04-11-2011 08:27, Hans Verkuil escreveu:
> On Friday 04 November 2011 11:19:37 Mauro Carvalho Chehab wrote:
>> Em 04-11-2011 08:13, Mauro Carvalho Chehab escreveu:
>>> Em 04-11-2011 07:39, Hans Verkuil escreveu:
Mauro,
This fixes two compilation problems when using the media_build
Hi Sylwester,
Thanks for the patch.
On Wednesday 02 November 2011 17:15:57 Sylwester Nawrocki wrote:
> The VIDIOC_LOG_STATUS ioctl allows to dump current status of a driver
> to the kernel log. Currently this ioctl is only available at video
> device nodes and the subdevs rely on the host driver
Hi Javier,
On Wednesday 02 November 2011 17:33:16 javier Martin wrote:
> On 2 November 2011 17:12, Devin Heitmueller wrote:
> > I've actually got a very similar issue and have been looking into it
> > (an em28xx device on OMAP requiring contiguous physical memory for the
> > hardware H.264 encoder
Hello,
On Tuesday, October 18, 2011 3:43 PM Mel Gorman wrote:
> On Thu, Oct 06, 2011 at 03:54:46PM +0200, Marek Szyprowski wrote:
> > The Contiguous Memory Allocator is a set of helper functions for DMA
> > mapping framework that improves allocations of contiguous memory chunks.
> >
> > CMA grabs
Hi Gary,
On Tuesday 01 November 2011 19:52:49 Gary Thomas wrote:
> I'm trying to use the MT9P031 digital sensor with the Media Controller
> Framework. media-ctl tells me that the sensor is set to capture using
> SGRBG12 2592x1944
>
> Questions:
> * What pixel format in ffmpeg does this correspo
On Friday 04 November 2011 11:19:37 Mauro Carvalho Chehab wrote:
> Em 04-11-2011 08:13, Mauro Carvalho Chehab escreveu:
> > Em 04-11-2011 07:39, Hans Verkuil escreveu:
> >> Mauro,
> >>
> >> This fixes two compilation problems when using the media_build system.
> >>
> >> Both gspca and the solo dr
Em 04-11-2011 08:13, Mauro Carvalho Chehab escreveu:
> Em 04-11-2011 07:39, Hans Verkuil escreveu:
>> Mauro,
>>
>> This fixes two compilation problems when using the media_build system.
>>
>> Both gspca and the solo driver have a header with the same name, and that
>> clashes when using media_build
Em 04-11-2011 07:39, Hans Verkuil escreveu:
> Mauro,
>
> This fixes two compilation problems when using the media_build system.
>
> Both gspca and the solo driver have a header with the same name, and that
> clashes when using media_build.
This the kind of patch that doesn't make much sense upst
Hi Alain,
On Thursday 03 November 2011 10:16:25 Alain VOLMAT wrote:
> Hi
>
> Last week we started the discussion about having a MediaController
> aware LinuxDVB demux and I would like to proceed on this discussion.
> Then, the discussion rapidly moved to having the requirement for
> dynamic pads
Mauro,
This fixes two compilation problems when using the media_build system.
Both gspca and the solo driver have a header with the same name, and that
clashes when using media_build.
And the solo driver uses an incorrect Makefile construct, which (somewhat
mysteriously) skips the compilation of
Em 04-11-2011 05:09, Marek Szyprowski escreveu:
> Hello Mauro,
>
> On Thursday, November 03, 2011 7:26 PM Mauro Carvalho Chehab wrote:
>
>> Em 06-10-2011 11:57, Marek Szyprowski escreveu:
>>> Hello Mauro,
>>>
>>> The following changes since commit 2f4cf2c3a971c4d5154def8ef9ce4811d702852d:
>>>
>>>
Hi Thomas,
On 10/15/2011 11:38 PM, Thomas Jarosch wrote:
> Detected by "cppcheck".
>
> This time with "Signed-off-by" line.
>
> Signed-off-by: Thomas Jarosch
Acked-by: Sylwester Nawrocki
> ---
> drivers/media/video/m5mols/m5mols_core.c |2 +-
> 1 files changed, 1 insertions(+), 1 deleti
Hi,
VIDIOC_ENUMINPUT may set the flag V4L2_IN_ST_NO_SYNC in the status
field. The flag is described in the documentation under "Digital Video"
as "No synchronization lock"
(http://hverkuil.home.xs4all.nl/spec/media.html#vidioc-enuminput). What
kind of sync lock does it refer to? Horizontal syn
Hello Mauro,
I've collected various pending patches from Samsung and updated our git
tree. Almost all of the patches are quite important fixes to various
videobuf2 corner cases, so I hope they will find their way into v3.2.
The following changes since commit 31cea59efb3a4210c063f31c061ebcaff833f5
Hello Mauro,
On Thursday, November 03, 2011 7:26 PM Mauro Carvalho Chehab wrote:
> Em 06-10-2011 11:57, Marek Szyprowski escreveu:
> > Hello Mauro,
> >
> > The following changes since commit 2f4cf2c3a971c4d5154def8ef9ce4811d702852d:
> >
> > [media] dib9000: release a lock on error (2011-09-30 1
46 matches
Mail list logo