Re: [PATCH 6/9] [media] ir-rx51: fix clock API related build issues

2013-03-05 Thread Timo Kokkonen
On 03.05 2013 17:09:53, Tony Lindgren wrote: > * Mauro Carvalho Chehab [130305 16:28]: > > Em Tue, 5 Mar 2013 23:16:46 +0100 > > Arnd Bergmann escreveu: > > > > > OMAP1 no longer provides its own clock interfaces since patch > > > a135eaae52 "ARM: OMAP: remove plat/clock.h". This is great, but

Re: [PATCH 6/9] [media] ir-rx51: fix clock API related build issues

2013-03-05 Thread Tony Lindgren
* Mauro Carvalho Chehab [130305 16:28]: > Em Tue, 5 Mar 2013 23:16:46 +0100 > Arnd Bergmann escreveu: > > > OMAP1 no longer provides its own clock interfaces since patch > > a135eaae52 "ARM: OMAP: remove plat/clock.h". This is great, but > > we now have to convert the ir-rx51 driver to use the

Re: [PATCH 6/9] [media] ir-rx51: fix clock API related build issues

2013-03-05 Thread Mauro Carvalho Chehab
Em Tue, 5 Mar 2013 23:16:46 +0100 Arnd Bergmann escreveu: > OMAP1 no longer provides its own clock interfaces since patch > a135eaae52 "ARM: OMAP: remove plat/clock.h". This is great, but > we now have to convert the ir-rx51 driver to use the generic > interface from linux/clk.h. > > The driver

[PATCH] dvb-apps/scan: distinguish transponders with different polarisations

2013-03-05 Thread Adam Sampson
Hi, I've just gone to listen to a DVB-S radio station from Eutelsat 28A, and was a bit surprised when "scan" either didn't find it, or found it with the wrong polarisation. With -vvv, the cause was reasonably easy to see: | $ echo 'S 12607000 V 2750 2/3' >transponders | $ scan -l universal -x

[PATCH 0/9] fixes for ARM build regressions in 3.9-rc1

2013-03-05 Thread Arnd Bergmann
This is the result of my my build tests on 3.9-rc1, mostly bugs that I had not caught before the merge window, or where the fix for some reason has not yet made it in. I hope the subsystem maintainers can take care of applying these, for the arch/arm/mach-* patches I can either apply them directly

[PATCH 6/9] [media] ir-rx51: fix clock API related build issues

2013-03-05 Thread Arnd Bergmann
OMAP1 no longer provides its own clock interfaces since patch a135eaae52 "ARM: OMAP: remove plat/clock.h". This is great, but we now have to convert the ir-rx51 driver to use the generic interface from linux/clk.h. The driver also uses the omap_dm_timer_get_fclk() function, which is not exported f

[PATCH] dvb_demux: Transport stream continuity check fix

2013-03-05 Thread John Smith
This patch avoids incrementing continuity counter demux->cnt_storage[pid] for TS packets without payload in accordance with ISO /IEC 13818-1. Signed-off-by: John Smith diff --git a/drivers/media/dvb-core/dvb_demux.c b/drivers/media/dvb-core/dvb_demux.c index d319717..70a89c8 100644 --- a/drivers

Re: HAUPPAUGE HVR-930C analog tv feasible ??

2013-03-05 Thread jandegr1
Citeren Daniel Glöckner : Hi, On Fri, Mar 01, 2013 at 09:28:54PM +0100, jande...@dommel.be wrote: Citeren Mauro Carvalho Chehab : >nor I succeeded >to get any avf4910b datasheet or development kit. and now that Trident went bankrupt chances are slim that one of us ever will. Any other sugg

cron job: media_tree daily build: ERRORS

2013-03-05 Thread Hans Verkuil
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: Tue Mar 5 19:00:23 CET 2013 git branch: test git hash: 5ce60d790a246c4c32043ac9b142615466479728 gcc versio

[PATCH] lmedm04: Remove redundant NULL check before kfree

2013-03-05 Thread Syam Sidhardhan
kfree on NULL pointer is a no-op. Signed-off-by: Syam Sidhardhan --- drivers/media/usb/dvb-usb-v2/lmedm04.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/media/usb/dvb-usb-v2/lmedm04.c b/drivers/media/usb/dvb-usb-v2/lmedm04.c index 96804be..b3fd0ff 100644 ---

Re: [PATCH v2] media: i.MX27 camera: fix picture source width

2013-03-05 Thread Guennadi Liakhovetski
(Javier's opinion requested) I'm no expert in i.MX27 hardware, would be great to have an ack from someone, intensively working in this area. Javier, what do you think? Is this really correct always for channel 1, or should this calculation depend on the pixel format? Thanks Guennadi On Sat, 1

Re: [PATCH 0/3] em28xx: add support for two buses on em2874 and upper

2013-03-05 Thread Devin Heitmueller
2013/3/5 Mauro Carvalho Chehab : > The em2874 chips and upper have 2 buses. On all known devices, bus 0 is > currently used only by eeprom, and bus 1 for the rest. Add support to > register both buses. Did you add a mutex to ensure that both buses cannot be used at the same time? Because using th

Re: [GIT PULL FOR v3.9] cx231xx: v4l2 compliance and big-endian fixes.

2013-03-05 Thread Hans Verkuil
On Tue 5 March 2013 16:19:52 Mauro Carvalho Chehab wrote: > Em Fri, 15 Feb 2013 09:46:59 +0100 > Hans Verkuil escreveu: > > > This patch series cleans up the cx231xx driver based on v4l2-compliance > > reports. > > > > It is identical to the RFCv2 patch series I posted a week ago: > > > > http:

Re: [GIT PULL FOR v3.9] cx231xx: v4l2 compliance and big-endian fixes.

2013-03-05 Thread Mauro Carvalho Chehab
Em Fri, 15 Feb 2013 09:46:59 +0100 Hans Verkuil escreveu: > This patch series cleans up the cx231xx driver based on v4l2-compliance > reports. > > It is identical to the RFCv2 patch series I posted a week ago: > > http://www.mail-archive.com/linux-media@vger.kernel.org/msg58508.html > > I have

Re: [REVIEW PATCH V4 12/12] [media] marvell-ccic: add 3 frame buffers support in DMA_CONTIG mode

2013-03-05 Thread Guennadi Liakhovetski
On Thu, 7 Feb 2013, Albert Wang wrote: > This patch adds support of 3 frame buffers in DMA-contiguous mode. > > In current DMA_CONTIG mode, only 2 frame buffers can be supported. > Actually, Marvell CCIC can support 2 or 3 frame buffers. > > Currently 3 frame buffers mode will be used by default

Re: [REVIEW PATCH V4 11/12] [media] marvell-ccic: add dma burst support for marvell-ccic driver

2013-03-05 Thread Guennadi Liakhovetski
Not much _I_ could help here with, FWIW: On Thu, 7 Feb 2013, Albert Wang wrote: > This patch adds the dma burst size config support for marvell-ccic. > Developer can set the dma burst size in specified board driver. > > Signed-off-by: Albert Wang > Signed-off-by: Libin Yang > Acked-by: Jonatha

Re: [REVIEW PATCH V4 10/12] [media] marvell-ccic: add soc_camera support for marvell-ccic driver

2013-03-05 Thread Guennadi Liakhovetski
Ok, can we test existing systems, have they been tested? It is hard to review this, as you might imagine. At least I don't think I can in any reasonably way verify by just looking at this whether it's breaking anything... I think, people, really using / developing this driver for other platform

[ANNOUNCE] Changes at the master repository (media-tree.git)

2013-03-05 Thread Mauro Carvalho Chehab
I did today one change at the master driver development repository. In the past, we used to have per-kernel release branches. The rationale is that we were doing rebases on each new version, when we migrated from hg to git. Well, we don't do such rebases anymore; instead, when a new version comes

Re: [PATCH 1/1] [media] davinci_vpfe: Use module_platform_driver macro

2013-03-05 Thread Prabhakar Lad
Hi Sachin, Thanks for the patch! On Tue, Mar 5, 2013 at 5:22 PM, Sachin Kamat wrote: > module_platform_driver() eliminates the boilerplate and simplifies > the code. > > Signed-off-by: Sachin Kamat Acked-by: Lad, Prabhakar Regards, --Prabhakar Lad > --- > .../staging/media/davinci_vpfe/vpf

[PATCH 1/1] [media] davinci_vpfe: Use module_platform_driver macro

2013-03-05 Thread Sachin Kamat
module_platform_driver() eliminates the boilerplate and simplifies the code. Signed-off-by: Sachin Kamat --- .../staging/media/davinci_vpfe/vpfe_mc_capture.c | 20 +--- 1 files changed, 1 insertions(+), 19 deletions(-) diff --git a/drivers/staging/media/davinci_vpfe/vpfe_mc_

[PATCH 1/3] em28xx: Prepare to support 2 different I2C buses

2013-03-05 Thread Mauro Carvalho Chehab
Newer em28xx devices have 2 buses. Change the logic to allow using both buses. This patch was generated by this small script: for i in drivers/media/usb/em28xx/*.c; do sed 's,->i2c_adap,->i2c_adap[dev->def_i2c_bus],g;s,->i2c_client,->i2c_client[dev->def_i2c_bus],' done Of course, em28xx

[PATCH 0/3] em28xx: add support for two buses on em2874 and upper

2013-03-05 Thread Mauro Carvalho Chehab
The em2874 chips and upper have 2 buses. On all known devices, bus 0 is currently used only by eeprom, and bus 1 for the rest. Add support to register both buses. Tested with 2 devices: HVR-950C (em2883 - 1 bus) and Terratec Cinergy HTC (em2884 - 2 buses): 1) HVR-950C (1 bus only) [ 7476.154903]

[PATCH 3/3] em28xx: add support for registering multiple i2c buses

2013-03-05 Thread Mauro Carvalho Chehab
Register both buses 0 and 1 via I2C API. For now, bus 0 is used only by eeprom on all known devices. Later patches will be needed if this changes in the future. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/em28xx/em28xx-cards.c | 29 +++--- drivers/media/usb/em28xx/em28xx-i2c.c

[PATCH 2/3] em28xx: Add a separate config dir for secondary bus

2013-03-05 Thread Mauro Carvalho Chehab
Prepare to register a separate bus for the second bus. For now, just add a new field. A latter patch will add the bits to make it work. This patch was generated by this script: perl -e 'while (<>) { if (s/EM2874_I2C_SECONDARY_BUS_SELECT.*\n//) { printf "\t\t.def_i2c_bus = 1,\n"; $found

Re: [RFC PATCH] Adding additional flags when allocating buffer memory

2013-03-05 Thread Marek Szyprowski
Hello, On 3/5/2013 10:59 AM, Hans Verkuil wrote: On Tue 5 March 2013 10:28:38 Marek Szyprowski wrote: > Hello, > > On 3/1/2013 7:44 PM, Hans Verkuil wrote: > > Hi all, > > > > This patch is based on an idea from Federico: > > > > http://www.mail-archive.com/davinci-linux-open-source@linux.davin

Re: [REVIEW PATCH V4 09/12] [media] marvell-ccic: use unsigned int type replace int type

2013-03-05 Thread Guennadi Liakhovetski
I'm not against this patch, but I don't see a lot of meaning in it either, apart from the .irq part - that makes the type match *request_*irq() prototypes. Apart from that... Using "int i" for a simple iterator, that doesn't go beyond INT_MAX is kinda traditional, I think. You change int frame

[PATCH] [media] dma-mapping: enable no mmu support in dma_common_mmap

2013-03-05 Thread Scott Jiang
No MMU systems also make use of this function to do mmap. Signed-off-by: Scott Jiang --- drivers/base/dma-mapping.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/drivers/base/dma-mapping.c b/drivers/base/dma-mapping.c index 0ce39a3..ae655b2 100644 --- a/drivers/base/d

Re: [RFC PATCH] Adding additional flags when allocating buffer memory

2013-03-05 Thread Federico Vaga
Hi all, > > I agree that the gfp_flags is needed. It should be there from the > > beginning, > > but there is not DMA zone on our hardware and we missed that point. Our > > fault. > > However IMHO the better place for gfp_flags is the allocator context > > structure > > instead of vb2_queue. vb2_d

Re: [REVIEW PATCH V4 08/12] [media] marvell-ccic: rename B_DMA* to avoid CamelCase warning

2013-03-05 Thread Guennadi Liakhovetski
On Thu, 7 Feb 2013, Albert Wang wrote: > This patch renames the B_vmalloc/B_DMA_contig/B_DMA_sg to > B_VMALLOC/B_DMA_CONTIG/B_DMA_SG variables to avoid CamelCase warning > reported by the checkpatch.pl script. > > Signed-off-by: Albert Wang > Signed-off-by: Libin Yang Acked-by: Guennadi Liakho

Re: [REVIEW PATCH V4 01/12] [media] marvell-ccic: add MIPI support for marvell-ccic driver

2013-03-05 Thread Guennadi Liakhovetski
Oh, one more thing occurred to me after looking at your another patch: On Thu, 7 Feb 2013, Albert Wang wrote: > From: Libin Yang > > This patch adds the MIPI support for marvell-ccic. > Board driver should determine whether using MIPI or not. > > Signed-off-by: Albert Wang > Signed-off-by: Li

Re: [REVIEW PATCH V4 07/12] [media] marvell-ccic: switch to resource managed allocation and request

2013-03-05 Thread Guennadi Liakhovetski
Yet one more nitpick On Thu, 7 Feb 2013, Albert Wang wrote: > This patch switchs to resource managed allocation and request in mmp-driver. > It can remove free resource operations. > > Signed-off-by: Albert Wang > Signed-off-by: Libin Yang > Acked-by: Jonathan Corbet > --- > drivers/media/pl

Re: [REVIEW PATCH V4 05/12] [media] marvell-ccic: add new formats support for marvell-ccic driver

2013-03-05 Thread Guennadi Liakhovetski
Looks pretty good to me now, just one nitpick: On Thu, 7 Feb 2013, Albert Wang wrote: > From: Libin Yang > > This patch adds the new formats support for marvell-ccic. > > Signed-off-by: Albert Wang > Signed-off-by: Libin Yang > --- > drivers/media/platform/marvell-ccic/mcam-core.c | 189 >

Re: [RFC PATCH] Adding additional flags when allocating buffer memory

2013-03-05 Thread Hans Verkuil
On Tue 5 March 2013 10:28:38 Marek Szyprowski wrote: > Hello, > > On 3/1/2013 7:44 PM, Hans Verkuil wrote: > > Hi all, > > > > This patch is based on an idea from Federico: > > > > http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg24669.html > > > > While working on con

Re: [REVIEW PATCH V4 02/12] [media] marvell-ccic: add clock tree support for marvell-ccic driver

2013-03-05 Thread Guennadi Liakhovetski
Hi Albert On Thu, 7 Feb 2013, Albert Wang wrote: > From: Libin Yang > > This patch adds the clock tree support for marvell-ccic. > > Signed-off-by: Libin Yang > Signed-off-by: Albert Wang > Acked-by: Jonathan Corbet > --- > drivers/media/platform/marvell-ccic/mcam-core.h |4 ++ > driv

Re: [RFC PATCH] Adding additional flags when allocating buffer memory

2013-03-05 Thread Marek Szyprowski
Hello, On 3/1/2013 7:44 PM, Hans Verkuil wrote: Hi all, This patch is based on an idea from Federico: http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg24669.html While working on converting the solo6x10 driver to vb2 I realized that the same thing was needed for t

Re: [PATCH v17 2/7] video: add display_timing and videomode

2013-03-05 Thread Steffen Trumtrar
Hi! On Wed, Feb 27, 2013 at 06:13:49PM +0200, Tomi Valkeinen wrote: > On 2013-02-27 18:05, Steffen Trumtrar wrote: > > Ah, sorry. Forgot to answer this. > > > > On Wed, Feb 27, 2013 at 05:45:31PM +0200, Tomi Valkeinen wrote: > >> Ping. > >> > >> On 2013-02-18 16:09, Tomi Valkeinen wrote: > >>> Hi