On 3/28/2013 3:50 PM, Prabhakar Lad wrote:
Hi Laurent,
On Thu, Mar 28, 2013 at 3:40 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Prabhakar,
On Thursday 28 March 2013 15:36:11 Prabhakar Lad wrote:
On Thu, Mar 28, 2013 at 2:39 PM, Laurent Pinchart wrote:
On Thursday 28
Hi Sekhar,
On Mon, Apr 1, 2013 at 11:33 AM, Sekhar Nori nsek...@ti.com wrote:
On 3/28/2013 3:50 PM, Prabhakar Lad wrote:
Hi Laurent,
On Thu, Mar 28, 2013 at 3:40 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Prabhakar,
On Thursday 28 March 2013 15:36:11 Prabhakar Lad
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Add pm_runtime support to the TI Davinci VPIF driver.
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
Cc: Mauro Carvalho Chehab mche...@redhat.com
Cc: Hans Verkuil hans.verk...@cisco.com
Cc: Laurent Pinchart
As poll behavior described in following link, polling needs to just return if
already some buffer is in done list.
Link: http://www.spinics.net/lists/linux-media/msg34759.html
But in current vb2 and v4l2_m2m, poll function always calls poll_wait(), so it
needs to wait until next vb2_buffer_done()
The vb2_poll() does not need to wait next vb_buffer_done() if there is already
a buffer in done_list of queue, but current vb2_poll() always waits.
So done_list is checked before calling poll_wait().
Signed-off-by: Seung-Woo Kim sw0312@samsung.com
---
drivers/media/v4l2-core/videobuf2-core.c
The v4l2_m2m_poll() does not need to wait if there is already a buffer in
done_list of source and destination queues, but current v4l2_m2m_poll() always
waits. So done_list of each queue is checked before calling poll_wait().
Signed-off-by: Seung-Woo Kim sw0312@samsung.com
---
On 1 April 2013 12:06, Prabhakar lad prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Add pm_runtime support to the TI Davinci VPIF driver.
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
Cc: Mauro Carvalho Chehab mche...@redhat.com
Cc: Hans Verkuil
On Mon, Apr 1, 2013 at 12:47 PM, Rajagopal Venkat
rajagopal.ven...@linaro.org wrote:
On 1 April 2013 12:06, Prabhakar lad prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Add pm_runtime support to the TI Davinci VPIF driver.
Signed-off-by: Lad, Prabhakar
While migrating to common clock framework (CCF), found that the FIMD clocks
were pulled down by the CCF.
If CCF finds any clock(s) which has NOT been claimed by any of the
drivers, then such clock(s) are PULLed low by CCF.
By calling clk_prepare_enable() for FIMD clocks fixes the issue.
this
On 1 April 2013 14:13, Vikas Sajjan vikas.saj...@linaro.org wrote:
While migrating to common clock framework (CCF), found that the FIMD clocks
s/found/we found/
were pulled down by the CCF.
If CCF finds any clock(s) which has NOT been claimed by any of the
drivers, then such clock(s) are
On 1 April 2013 13:53, Prabhakar Lad prabhakar.cse...@gmail.com wrote:
On Mon, Apr 1, 2013 at 12:47 PM, Rajagopal Venkat
rajagopal.ven...@linaro.org wrote:
On 1 April 2013 12:06, Prabhakar lad prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Add pm_runtime
Hi Laurent,
+struct mt9m114_reg {
+ u16 reg;
+ u32 val;
+ int width;
+};
+
+enum {
+ MT9M114_QVGA,
+ MT9M114_VGA,
+ MT9M114_WVGA,
+ MT9M114_720P,
+};
This is the part I don't like. Instead of hardcoding 4 different
resolutions and using
Hey Ralph,
On 02/15/13 14:47, Ralph Metzler wrote:
Oliver Schinagl writes:
On 02/11/13 23:20, Martin Vidovic wrote:
Hi,
Is there any plan to include ddbridge driver version 0.8 in mainline
kernel
(currently it's 0.5). I really see no reason it's in the vacuum like now
Hi Hans,
On Sun March 31 2013 14:48:01 Hans de Goede wrote:
Hi,
On 03/30/2013 10:47 AM, Hans Verkuil wrote:
This patch for xawtv3 releases the buffer if it can't be displayed because
the resolution of the current format is larger than the size of the window.
This will happen if the
Hi,
On Mon, Mar 11, 2013 at 09:40:22AM +0100, Guido Günther wrote:
---
Tested with totem as well as gst-launch. Any chance this can be applied
to http://git.linuxtv.org/jarod/crystalhd.git?
Any chance this gets applied.
Cheers,
-- Guido
filters/gst/gst-plugin/configure.ac|8 +-
Hi,
On 04/01/2013 12:19 PM, Hans Verkuil wrote:
Hi Hans,
On Sun March 31 2013 14:48:01 Hans de Goede wrote:
Hi,
On 03/30/2013 10:47 AM, Hans Verkuil wrote:
This patch for xawtv3 releases the buffer if it can't be displayed because
the resolution of the current format is larger than the size
On Mon April 1 2013 16:23:51 Hans de Goede wrote:
Hi,
On 04/01/2013 12:19 PM, Hans Verkuil wrote:
Hi Hans,
On Sun March 31 2013 14:48:01 Hans de Goede wrote:
Hi,
On 03/30/2013 10:47 AM, Hans Verkuil wrote:
This patch for xawtv3 releases the buffer if it can't be displayed because
As pointed by Dan Carpenter, there are two smatch warnings on
this driver:
drivers/media/dvb-frontends/mb86a20s.c:1897 mb86a20s_set_frontend()
error: buffer overflow 'mb86a20s_subchannel' 8 = 8
drivers/media/dvb-frontends/mb86a20s.c:644 mb86a20s_layer_bitrate()
error: buffer
Using 'i' for the guard interval temporary var is a bad idea, as
'i' is generally used by anonymous indexes.
Let's rename modulation, fec and guard interval temp vars with
a meaningful name, as that makes easier to understand the code
and avoids cut-and-paste types of error.
Signed-off-by: Mauro
As reported by Dan Carpenter dan.carpen...@oracle.com:
Smatch warnings:
drivers/media/dvb-frontends/mb86a20s.c:644 mb86a20s_layer_bitrate()
error: buffer overflow 'state-estimated_rate' 3 = 3
What happens there is that estimate_rate index should be the layer
number, and not the
We're using the anonymous 'i' to indicate the layer number
on several places on the driver. That's not good, as some
cut-and-paste type of change might be doing the wrong thing.
So, call it as layer everywhere.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
As reported by Dan Carpenter dan.carpen...@oracle.com
FYI, there are new smatch warnings show up in:
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
master
head: da17d7bda957ae4697b6abc0793f74fb9b50b58f
commit:
Instead of using the magic number 3, use NUM_LAYERS macro
on all places that are related to the ISDB-T layers.
This makes the source code a little more readable.
No functional changes.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb-frontends/mb86a20s.c | 32
As reported by Dan Carpenter:
FYI, there are new smatch warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
master
head: da17d7bda957ae4697b6abc0793f74fb9b50b58f
commit: 4c3bdb5e2f5612ceb99ac17dbbe673b59a94d105 [media]
Hi John,
Thanks for the new driver! Unfortunately the driver is still
using gspca's own/deprecated control mechanism rather then
the new v4l2-control framework which all drivers now a days
use.
And we've just finished converting all the gspca sub-drivers
to using this new control framework, and
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em Wed, 06 Mar 2013 18:44:07 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 05.03.2013 16:43, schrieb Devin Heitmueller:
2013/3/5 Mauro Carvalho Chehab mche...@redhat.com:
The em2874 chips and upper have 2 buses. On all known
Am 30.03.2013 10:54, schrieb Timo Teras:
On Thu, 28 Mar 2013 12:22:52 -0300
Mauro Carvalho Chehab mche...@redhat.com wrote:
On the W7 driver, I don't get any of the above mentioned problems.
I looked at the saa7113 register init sequence, and copied that
over to linux saa7113 init, but that
On Sun, Mar 24, 2013 at 2:11 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
== Michael Krufky mkru...@linuxtv.org ==
Michael promised to review and apply them on his tree, sending me a pull
request, but this never happened. Mike, did you see any issues on those
patches?
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: Mon Apr 1 19:30:52 CEST 2013
git branch: test
git hash: 6bf7861fa2bb4be3cc70a6e9aed664ce65270027
gcc
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em Wed, 06 Mar 2013 18:44:07 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 05.03.2013 16:43, schrieb Devin Heitmueller:
2013/3/5
Am 01.04.2013 21:22, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em Wed, 06 Mar 2013 18:44:07 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am
Good catch! I don't know if this fix got merged yet or not, but it's correct.
Reviewed-by: Michael Krufky mkru...@linuxtv.org
On Tue, Mar 26, 2013 at 7:17 AM, Hans Verkuil hverk...@xs4all.nl wrote:
au8522_attach is dependent on CONFIG_DVB_AU8522_DTV, not CONFIG_DVB_AU8522.
Signed-off-by:
Em Mon, 01 Apr 2013 22:39:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 01.04.2013 21:22, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em
Em Mon, 1 Apr 2013 19:12:24 -0300
Mauro Carvalho Chehab mche...@redhat.com escreveu:
Em Mon, 01 Apr 2013 22:39:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 01.04.2013 21:22, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer
Hi all
After analyzing 15 samples (took me many days),I obtained the table
underneath.
{ 0x70, 0x0f },
{ 0x70, 0xff },
{ 0x09, 0x3a },
{ 0x50, 0xd1 }, { 0x51, 0x22 },
{ 0x39, 0x00 },
{ 0x28, 0x2a }, { 0x29, 0x00 }, { 0x2a, 0xfd }, { 0x2b, 0xc8 },
{ 0x3b, 0x21 },
Hi Guennadi,
On Friday 29 March 2013 16:13:41 Guennadi Liakhovetski wrote:
Hi Mauro
On Sun, 24 Mar 2013, Mauro Carvalho Chehab wrote:
== Guennadi Liakhovetski g.liakhovet...@gmx.de ==
I suspect that some of the above may be obsoleted:
Nov,13 2012: sh_vou: Move from
On Sun, Mar 24, 2013 at 11:41 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
This is the summary of the patches that are currently under review at
Linux Media Mailing List linux-media@vger.kernel.org.
Manu,
Yet another patch adding IR support for mantis. It seems that this is
is a long
Hi Mr. Inki Dae,
Can you please review this patch.?
On Wed, Mar 13, 2013 at 4:22 PM, Vikas Sajjan vikas.saj...@linaro.org wrote:
Replaces the platform_get_resource() for IORESOURCE_IRQ with
platform_get_resource_byname().
Both in exynos4 and exynos5, FIMD IP has 3 interrupts in the order:
On Mon, 01 Apr 2013 19:26:53 +0200
Frank Schäfer fschaefer@googlemail.com wrote:
Am 30.03.2013 10:54, schrieb Timo Teras:
On Thu, 28 Mar 2013 12:22:52 -0300
Mauro Carvalho Chehab mche...@redhat.com wrote:
On the W7 driver, I don't get any of the above mentioned problems.
I looked
39 matches
Mail list logo
