On Fri, Jan 30, 2015 at 2:26 AM, kbuild test robot
wrote:
> drivers/media/platform/am437x/am437x-vpfe.c:2767:3-8: No need to set .owner
> here. The core will do it.
>
> Remove .owner field if calls are used which set it automatically
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner
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 Jan 30 04:00:23 CET 2015
git branch: test
git hash: a5f43c18fceb2b96ec9fddb4348f5282a71cf2b0
gcc versio
drivers/media/platform/am437x/am437x-vpfe.c:2767:3-8: No need to set .owner
here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Benoit Parrot
Signed-off-by: Fengguang Wu
---
am437x-
tree: git://linuxtv.org/media_tree.git master
head: a5f43c18fceb2b96ec9fddb4348f5282a71cf2b0
commit: 417d2e507edcb5cf15eb344f86bd3dd28737f24e [66/173] [media] media:
platform: add VPFE capture driver support for AM437X
coccinelle warnings: (new ones prefixed by >>)
>> drivers/media/platform
On Thu, Jan 29, 2015 at 5:31 PM, Russell King - ARM Linux
wrote:
> On Thu, Jan 29, 2015 at 05:18:33PM -0500, Rob Clark wrote:
>> On Thu, Jan 29, 2015 at 2:26 PM, Russell King - ARM Linux
>> wrote:
>> > Now, if we're going to do the "more clever" thing you mention above,
>> > that rather negates t
On Thu, Jan 29, 2015 at 05:18:33PM -0500, Rob Clark wrote:
> On Thu, Jan 29, 2015 at 2:26 PM, Russell King - ARM Linux
> wrote:
> > Now, if we're going to do the "more clever" thing you mention above,
> > that rather negates the point of this two-part patch set, which is to
> > provide the union o
The host was rebooted and got back online.
Without irqbalance daemon, all solo6x10 interrupts are still on CPU0.
See https://gist.github.com/krieger-od/d1686243c67fbe3e14a5
Any ideas are strongly appreciated.
--
Andrey Utkin
--
To unsubscribe from this list: send the line "unsubscribe linux-medi
On Thu, Jan 29, 2015 at 2:26 PM, Russell King - ARM Linux
wrote:
> On Thu, Jan 29, 2015 at 01:52:09PM -0500, Rob Clark wrote:
>> Quite possibly for some of these edge some of cases, some of the
>> dma-buf exporters are going to need to get more clever (ie. hand off
>> different scatterlists to dif
On Thu, 29 Jan 2015 19:48:08 +0100, Rickard Strandqvist said:
> Fix a possible null pointer dereference, there is
> otherwise a risk of a possible null pointer dereference.
>
> This was found using a static code analysis program called cppcheck
>
> Signed-off-by: Rickard Strandqvist
> ---
> drive
Hi, having another "card freeze" issue with linux-next (tag
next-20150128) on a server running 3 solo6110 cards. The freeze
happens after 3 days or so. Much better than 30 minutes, which was the
case before the recent enhancement by Krzysztof Halasa.
This is Ubuntu Trusty. There's /usr/sbin/irqbala
Hello again,
On 21.01.2015 14:29, Hans Verkuil wrote:
> On 01/21/15 14:28, Florian Echtler wrote:
>> On 20.01.2015 14:06, Laurent Pinchart wrote:
>>> That depends on the platform and whether it can DMA to vmalloc'ed memory
>>> :-)
>>> To be totally safe I think vb2-dma-sg would be better, but I'
Hi!
> > > This approach would require implementing additional mechanisms on
> > > both sides: LED Flash class core and a LED Flash class driver.
> > > In the former the sysfs attribute write permissions would have
> > > to be decided in the runtime and in the latter caching mechanism
> >
> > Writ
On Thu, 29 Jan 2015, Guennadi Liakhovetski wrote:
> Right, I see now. [OT] The problem is - this is not the first time this is
> happening - I didn't get that thread in my INBOX, only in the mailing list
> folder. I subscribe the mailing list from a different email address, than
> the one I'm C
On Thu, 29 Jan 2015, Sergei Shtylyov wrote:
> On 01/29/2015 11:19 PM, Guennadi Liakhovetski wrote:
>
> > > > > > This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
> > > > > > which is used by the ADV7612 chip.
>
> > > > > > Signed-off-by: Valentine Barshak
> > > > > >
>
> > > > > I
Em Thu, 15 Jan 2015 11:52:14 +0100
Hans de Goede escreveu:
> Hi Mauro,
>
> Note this pull-req superseeds my previous pull-req for 3.20 .
Hmm... I ended by applying the previous pull request. I was unable to see
what's new on this one. Please check if everything went fine.
Thanks!
Mauro
>
> P
On 01/29/2015 11:19 PM, Guennadi Liakhovetski wrote:
This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
which is used by the ADV7612 chip.
Signed-off-by: Valentine Barshak
I wonder why it hasn't been merged still? It's pending since 2013, and
I'm
seeing no objections to it...
Checkpatch complained about a few issues, like FSF address. Also,
multi-line comments are not following the Kernel CodingStyle.
While not too late, let's fix those issues.
Cc: John McMaster
Cc: Hans de Goede
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/usb/gspca/touptek.c
First of all, this subject puzzles me... What means WmT ??
2015-01-29 17:19 GMT+01:00 William Towle :
> ---
> drivers/media/i2c/adv7604.c | 12 ++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Again, it it passing checkpatch without signed-off-by ? And a little
description does
On Thu, 29 Jan 2015, Sergei Shtylyov wrote:
> Hello.
>
> On 01/29/2015 09:18 PM, Guennadi Liakhovetski wrote:
>
> > > > This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
> > > > which is used by the ADV7612 chip.
>
> > > > Signed-off-by: Valentine Barshak
>
> > > I wonder why it ha
2015-01-29 17:19 GMT+01:00 William Towle :
> From: Ian Molton
>
> ---
> Documentation/devicetree/bindings/media/i2c/adv7604.txt |3 +++
> drivers/media/i2c/adv7604.c |8 +++-
> 2 files changed, 10 insertions(+), 1 deletion(-)
Is this really passing through
Em Tue, 27 Jan 2015 12:36:49 +0200
Sakari Ailus escreveu:
> Hi Mauro,
>
> The recent smiapp OF support patches contained a small issue related to
> reading 64-bit numbers from the device tree, such that the compilation fails
> if CONFIG_OF is undefined.
>
> This patch provides a temporary fix t
On Thu, Jan 29, 2015 at 01:52:09PM -0500, Rob Clark wrote:
> Quite possibly for some of these edge some of cases, some of the
> dma-buf exporters are going to need to get more clever (ie. hand off
> different scatterlists to different clients). Although I think by far
> the two common cases will b
Am Donnerstag, den 29.01.2015, 16:34 +0100 schrieb Kamil Debski:
> Hi Philipp,
>
> Could you add a one sentence description for this patch?
> I know that it is really simple, but still the description is still
> necessary.
>
> Best wishes,
Will do, thanks.
regards
Philipp
--
To unsubscribe fro
On Thu, Jan 29, 2015 at 10:47 AM, Russell King - ARM Linux
wrote:
> On Thu, Jan 29, 2015 at 09:00:11PM +0530, Sumit Semwal wrote:
>> So, short answer is, it is left to the exporter to decide. The dma-buf
>> framework should not even attempt to decide or enforce any of the
>> above.
>>
>> At each d
Fix a possible null pointer dereference, there is
otherwise a risk of a possible null pointer dereference.
This was found using a static code analysis program called cppcheck
Signed-off-by: Rickard Strandqvist
---
drivers/staging/media/lirc/lirc_zilog.c |4 +---
1 file changed, 1 insertion(
On Thu, Jan 29, 2015 at 4:12 PM, Arnd Bergmann wrote:
> The davinci media drivers use videobuf2, which they enable through
> a 'select' statement. If one of these drivers is built-in, but
> the v4l2 core is a loadable modules, we end up with a link
> error:
>
> drivers/built-in.o: In function `vb2
Hello.
On 01/29/2015 09:18 PM, Guennadi Liakhovetski wrote:
This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
which is used by the ADV7612 chip.
Signed-off-by: Valentine Barshak
I wonder why it hasn't been merged still? It's pending since 2013, and I'm
seeing no objections to
Hi Sergei,
On Thu, 29 Jan 2015, Sergei Shtylyov wrote:
> Hello.
>
> On 01/29/2015 07:19 PM, William Towle wrote:
>
> > This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
> > which is used by the ADV7612 chip.
>
> > Signed-off-by: Valentine Barshak
>
>I wonder why it hasn't been mer
This patch adds tracepoints to the coda driver that can be used together
with the v4l2:v4l2_qbuf and v4l2:v4l2_dqbuf tracepoints to to follow video
frames through the mem2mem device.
For encoding with the BIT processor:
coda:coda_enc_pic_run
coda:coda_enc_pic_done
For decoding with the BI
Hello.
On 01/29/2015 07:19 PM, William Towle wrote:
This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
which is used by the ADV7612 chip.
Signed-off-by: Valentine Barshak
I wonder why it hasn't been merged still? It's pending since 2013, and I'm
seeing no objections to it...
W
On 29 January 2015 at 21:17, Russell King - ARM Linux
wrote:
> On Thu, Jan 29, 2015 at 09:00:11PM +0530, Sumit Semwal wrote:
>> So, short answer is, it is left to the exporter to decide. The dma-buf
>> framework should not even attempt to decide or enforce any of the
>> above.
>>
>> At each dma_bu
Hello.
On 01/29/2015 07:19 PM, William Towle wrote:
No signed off? Although, looking at the patch, I'm not very surprised...
---
arch/arm/boot/dts/r8a7790-lager.dts | 51 +++
1 file changed, 34 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boot/d
Hi Laurent,
I'm finally started working on this problem... but the code from the git
repository you specified don't compile:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
...
CC [M] drivers/media/i2c/tvp5150.o
drivers/media/i2c/tvp5150.c: In function ‘tvp5150_set_format’:
drivers/media/i2
Convert au0828 to use videobuf2. Tested with NTSC.
Tested video and vbi devices with xawtv, tvtime,
and vlc. Ran v4l2-compliance to ensure there are
no failures.
Video compliance test results summary:
Total: 75, Succeeded: 75, Failed: 0, Warnings: 18
Vbi compliance test results summary:
Total: 75
Add 'struct media_pad pad' member and suitable glue code, so that
soc_camera/rcar_vin can become agnostic to whether an old or new-
style driver (wrt pad API use) can sit underneath
This version has been reworked to include appropriate constant and
datatype names for kernel v3.18
---
drivers/medi
The following constitutes parts of our rcar_vin development branch
beyond the update to our hotfixes published earlier this month.
Similarly, these patches are intended to the mainline 3.18 kernel.
Further development is required, but we would like to highlight the
following issues and discuss th
This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
which is used by the ADV7612 chip.
Signed-off-by: Valentine Barshak
---
URL:http://marc.info/?l=linux-sh&m=138002993417489&q=raw
FIXMEs required:
- "From:" as per URL
- adapted for lx3.18 by William Towle -> add S-o-b **
---
drivers/me
Add 'struct media_pad pad' member and suitable glue code, so that
soc_camera/rcar_vin can become agnostic to whether an old or new-
style driver (wrt pad API use) can sit underneath
This version has been reworked to include appropriate constant and
datatype names for kernel v3.18
---
** this ver
From: Ian Molton
---
Documentation/devicetree/bindings/media/i2c/adv7604.txt |3 +++
drivers/media/i2c/adv7604.c |8 +++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/adv7604.txt
b/Documentatio
---
arch/arm/boot/dts/r8a7790-lager.dts | 51 +++
1 file changed, 34 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boot/dts/r8a7790-lager.dts
b/arch/arm/boot/dts/r8a7790-lager.dts
index be44493..c20b6cb 100644
--- a/arch/arm/boot/dts/r8a7790-lager.dts
+++
** for lx3.18.x+; from previous description **
The original adv7612-specific driver only contained formats meeting
a certain specification; allowing the adv7612 chip to permit all the
formats the adv7611 supports breaks this restriction and means that
enum_mbus_code can end up containing values th
---
Documentation/devicetree/bindings/media/i2c/adv7604.txt |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/adv7604.txt
b/Documentation/devicetree/bindings/media/i2c/adv7604.txt
index bc50da2..1ca6e5a 100644
--- a/Documentation/
---
drivers/media/i2c/adv7604.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/adv7604.c b/drivers/media/i2c/adv7604.c
index 30bbd9d..6ed9303 100644
--- a/drivers/media/i2c/adv7604.c
+++ b/drivers/media/i2c/adv7604.c
@@ -1976,7 +1976,11 @@ sta
Building the s5p-tv HDMI support when CONFIG_I2C is disabled
gives us this build error:
s5p-tv/hdmi_drv.c: In function 'hdmi_probe':
s5p-tv/hdmi_drv.c:947:2: error: implicit declaration of function
'i2c_get_adapter' [-Werror=implicit-function-declaration]
adapter = i2c_get_adapter(pdata->hdmiph
The davinci media drivers use videobuf2, which they enable through
a 'select' statement. If one of these drivers is built-in, but
the v4l2 core is a loadable modules, we end up with a link
error:
drivers/built-in.o: In function `vb2_fop_mmap':
:(.text+0x113e84): undefined reference to `video_devda
On Thu, Jan 29, 2015 at 09:00:11PM +0530, Sumit Semwal wrote:
> So, short answer is, it is left to the exporter to decide. The dma-buf
> framework should not even attempt to decide or enforce any of the
> above.
>
> At each dma_buf_attach(), there's a callback to the exporter, where
> the exporter
Hi Philipp,
Could you add a one sentence description for this patch?
I know that it is really simple, but still the description is still
necessary.
Best wishes,
--
Kamil Debski
Samsung R&D Institute Poland
> -Original Message-
> From: Philipp Zabel [mailto:p.za...@pengutronix.de]
> Sen
Hi Russell!
On 29 January 2015 at 20:09, Russell King - ARM Linux
wrote:
> On Tue, Jan 27, 2015 at 01:55:54PM +0530, Sumit Semwal wrote:
>> +/*
>> + * recalc_constraints - recalculates constraints for all attached devices;
>> + * useful for detach() recalculation, and for dma_buf_recalc_constrai
On Tue, Jan 27, 2015 at 01:55:54PM +0530, Sumit Semwal wrote:
> +/*
> + * recalc_constraints - recalculates constraints for all attached devices;
> + * useful for detach() recalculation, and for dma_buf_recalc_constraints()
> + * helper.
> + * Returns recalculated constraints in recalc_cons, or
Op 27-01-15 om 09:25 schreef Sumit Semwal:
> Add some helpers to share the constraints of devices while attaching
> to the dmabuf buffer.
>
> At each attach, the constraints are calculated based on the following:
> - max_segment_size, max_segment_count, segment_boundary_mask from
>device_dma_pa
Thank you for your comments, James. I'm sure it's not a hw fault because mine
works in Windows perfectly, and both tuners used independently also worked in
Linux.
BREl 29/1/2015 2:34, James Harper escribió:
>
> >
> > Hi, James.
> >
> > After searching for somebody posting some issues simila
On 01/29/15 12:51, Raimonds Cicans wrote:
> On 29.01.2015 09:33, Hans Verkuil wrote:
>> On 01/11/2015 10:33 AM, Raimonds Cicans wrote:
>>> I contacted you because I am hit by regression caused by your commit:
>>> 453afdd "[media] cx23885: convert to vb2"
>>>
>>>
>>> My system:
>>> AMD Athlon(tm) II
On 29.01.2015 09:33, Hans Verkuil wrote:
On 01/11/2015 10:33 AM, Raimonds Cicans wrote:
I contacted you because I am hit by regression caused by your commit:
453afdd "[media] cx23885: convert to vb2"
My system:
AMD Athlon(tm) II X2 240e Processor on Asus M5A97 LE R2.0 motherboard
TBS6981 card
On Wed, 2015-01-28 at 16:14 -0700, Shuah Khan wrote:
> On 01/23/2015 12:41 PM, Shuah Khan wrote:
> > Convert au0828 to use videobuf2. Tested with NTSC.
> > Tested video and vbi devices with xawtv, tvtime,
> > and vlc. Ran v4l2-compliance to ensure there are
> > no failures.
> >
> > Video complian
On 01/29/15 12:13, Davidlohr Bueso wrote:
> On Wed, 2015-01-28 at 16:14 -0700, Shuah Khan wrote:
>> On 01/23/2015 12:41 PM, Shuah Khan wrote:
>>> Convert au0828 to use videobuf2. Tested with NTSC.
>>> Tested video and vbi devices with xawtv, tvtime,
>>> and vlc. Ran v4l2-compliance to ensure ther
Keep the colorspace and encoding names consistent with what is
used elsewhere (primarily the utilities in v4l-utils.git).
Signed-off-by: Hans Verkuil
---
drivers/media/platform/vivid/vivid-ctrls.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/vivi
On Thu, 2015-01-29 at 12:15 +0100, Hans Verkuil wrote:
> You can't split this up, it's one of those changes that is all or
> nothing.
Fair enough. With changes that large, it should be mentioned, though.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body
On Mon, Jan 26, 2015 at 7:27 AM, Nicholas Mc Guire wrote:
> As the if and else branch body are identical the condition has no effect and
> can be dropped.
>
> Signed-off-by: Nicholas Mc Guire
Acked-by: Lad, Prabhakar
Regards,
--Prabhakar Lad
> ---
>
> As the if and the else branch of the inne
On Wed, Jan 28, 2015 at 9:17 PM, Arnd Bergmann wrote:
> This driver can only be built when VIDEO_V4L2_SUBDEV_API
> and VIDEO_DAVINCI_VPBE_DISPLAY are also provided by the
> kernel.
>
> drivers/staging/media/davinci_vpfe/dm365_isif.c: In function
> '__isif_get_format':
> drivers/staging/media/davi
59 matches
Mail list logo
