Hi Laurent,
[auto build test ERROR on: renesas/next]
[also build test ERROR on: v4.4-rc1 next-20151116]
url:
https://github.com/0day-ci/linux/commits/Laurent-Pinchart/VSP1-Add-support-for-lookup-tables/20151116-124808
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git n
The VSPS includes a CLU module, describe it in DT.
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7791.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/r8a7791.dtsi b/arch/arm/boot/dts/r8a7791.dtsi
index 831525dd39a6..fc2a1b10c1af 100644
--- a/arch/arm/boot/dt
The VSPS includes a CLU module, describe it in DT.
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7790.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/r8a7790.dtsi b/arch/arm/boot/dts/r8a7790.dtsi
index a0b2a79cbfbd..4e75b8df09e3 100644
--- a/arch/arm/boot/dt
The CLU processing block is a 3D lookup table that converts the input
three color component data into desired three color components using a
lookup table.
Signed-off-by: Laurent Pinchart
---
.../devicetree/bindings/media/renesas,vsp1.txt | 3 +
drivers/media/platform/vsp1/Makefile
Hello,
The VSP1 includes two lookup table modules, a 1D LUT and a 3D cubic lookup
table (CLU). This patch series fixes the LUT implementation and adds support
for the CLU.
The patches are based on top of
git://linuxtv.org/media_tree.git master
and have been tested on a Koelsch board.
L
The LUT set format handler overrides the requested format by mistake.
Fix it.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_lut.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/vsp1/vsp1_lut.c
b/drivers/media/platform/vsp1/vsp1_lut.c
index 656e
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 Nov 16 04:00:18 CET 2015
git branch: test
git hash: 79f5b6ae960d380c829fb67d5dadcd1d025d2775
gcc versio
Goede dag,
We zijn BARCLAYS LOANS COMPANY het geven van leningen per post
advertentie. Wij bieden verschillende soorten leningen (korte en lange termijn
leningen, persoonlijke leningen, leningen aan bedrijven etc.) met 2% rente. We
geven leningen aan mensen in nood niet, onge
Device Tree bindings for the Camera Adaptation Layer (CAL) driver
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/ti-cal.txt
diff --git a
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data lanes.
The driver implements the required API/ioctls to be V4L2 compli
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
This camera engine is currently found on DRA72xx family of devices.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data l
Hi,
I'm not seeing anything when I use "ir-keytable -t /dev/input/"
for my RC node in RC6 mode, although it does respond correctly in RC5
mode.
FWIW, I've realised that the 05a4:9881 IR dongle is actually
responding to all of its remote's keys. The problem is that USBHID
creates two /dev/inpu
Device Tree bindings for the Camera Adaptation Layer (CAL) driver
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/ti-cal.txt
diff --git a
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data lanes.
The driver implements the required API/ioctls to be V4L2 compli
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
This camera engine is currently found on DRA72xx family of devices.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data l
On Fri, Nov 13, 2015 at 11:46:00AM +0100, Julia Lawall wrote:
> Move constants to the right of binary operators.
>
> Generated by: scripts/coccinelle/misc/compare_const_fl.cocci
>
> CC: Junghak Sung
> Signed-off-by: Fengguang Wu
> Signed-off-by: Julia Lawall
Acked-by: Sakari Ailus
--
Saka
Hi Shuah,
On Thu, Nov 12, 2015 at 07:41:47AM -0700, Shuah Khan wrote:
> Media core drivers (dvb, v4l2, bridge driver) unregister
> their entities calling media_device_unregister_entity()
> during device removal from their unregister paths. In
> addition media_device_unregister() tries to unregiste
Em Sun, 15 Nov 2015 22:18:48 +
Chris Rankin escreveu:
> > How are you "switching back to RC5"?
>
> I use the command "ir-keytable -p rc-5" or "ir-keytable -p rc-6" to
> switch between IR protocols, which does seem to invoke the
> em2874_ir_change_protocol() function. I'm not sure that I have
> How are you "switching back to RC5"?
I use the command "ir-keytable -p rc-5" or "ir-keytable -p rc-6" to
switch between IR protocols, which does seem to invoke the
em2874_ir_change_protocol() function. I'm not sure that I have a
suitable RC6 keymap for this IR, and was expecting to have to creat
> I've dug a bit deeper and discovered that the reason the
> em28xx_info(...) lines that I'd added to em2874_polling_getkey()
> weren't appearing is because I'd loaded the wrong version of the
> em28xx-rc module! (Doh!)
Ok, good.
> The polling function *is* being called regularly, but
> em28xx_ir
This patch adds support for the DVB-T/C/T2 usb stick WinTV-soloHD from
Hauppauge.
It adds the usb ID 2040:0264 Hauppauge to the cards of the driver em28xx.
I successfully tested DVB-T/C and the IR remote control with the firmware
dvb-demod-si2168-b40-01.fw.
Signed-off-by: Arno Bauernoeppel
--
Hi,
I've dug a bit deeper and discovered that the reason the
em28xx_info(...) lines that I'd added to em2874_polling_getkey()
weren't appearing is because I'd loaded the wrong version of the
em28xx-rc module! (Doh!)
The polling function *is* being called regularly, but
em28xx_ir_handle_key() isn'
On Sun, Nov 15, 2015 at 3:49 PM, Chris Rankin wrote:
> Hi,
>
> My Hauppauge RC5 remote control finally broke, and the PCTV T2 290e's
> native RC5 remote control isn't suitable for VDR, and so I bought a
> cheap RC6 remote as a replacement. The unit I chose was the Ortek
> VRC-1100 Vista MCE Remote
Hi,
My Hauppauge RC5 remote control finally broke, and the PCTV T2 290e's
native RC5 remote control isn't suitable for VDR, and so I bought a
cheap RC6 remote as a replacement. The unit I chose was the Ortek
VRC-1100 Vista MCE Remote Control, USB ID 05a4:9881. I've been able to
switch the PCTV dev
The mxr_layer_ops structures are never modified, so declare them as const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
drivers/media/platform/s5p-tv/mixer.h |2 +-
drivers/media/platform/s5p-tv/mixer_grp_layer.c |2 +-
drivers/media/platform/s5p-tv/mixer
> I actually refer to CX23418 chip, which I don't find its datasheet (I
> saw in code that cx18 can work in YUV raw capture, so I wanted to
> verify that CX23418 can capture YUV raw format).
The cx23418 datasheets are not publicly available, although I have
them under NDA and can likely answer spe
On Sun, Nov 15, 2015 at 4:29 PM, Ran Shalit wrote:
> Hello,
>
> I was seaching for datasheet of Hauppauge PVR-150 (or other), but can't find
> it.
> Does anyone know where it can be found ?
Hi,
I actually refer to CX23418 chip, which I don't find its datasheet (I
saw in code that cx18 can work
Hi Mauro,
I've got 9 patches from Josh Wu for 4.5. Please, note, that patches 2-4
also touch vore v4l2-clock files, so, maybe you or someone else want to
look at them too.
The following changes since commit 79f5b6ae960d380c829fb67d5dadcd1d025d2775:
[media] c8sectpfe: Remove select on CONFIG_
Hello,
I was seaching for datasheet of Hauppauge PVR-150 (or other), but can't find it.
Does anyone know where it can be found ?
Best Regards,
Ran
--
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
29 matches
Mail list logo