- 31 Jan, 2017 36 commits
-
-
Michael Tretter authored
If the CODA driver is configured to produce NV12 output and the VDOA is available, the VDOA can be used to transform the custom macroblock tiled format to a raster-ordered format for scanout. In this case, set the output format of the CODA to the custom macroblock tiled format, disable the rotator, and use the VDOA to write to the v4l2 buffer. The VDOA is synchronized with the CODA to always un-tile the frame that the CODA finished in the previous run. Signed-off-by:
Michael Tretter <m.tretter@pengutronix.de> Signed-off-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@s-opensource.com>
-
Michael Tretter authored
display_idx refers to the frame that will be returned in the next round. The currently processed frame is ctx->display_idx and errors should be reported for this frame. Signed-off-by:
Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by:
-
Philipp Zabel authored
In order to make the VDOA work correctly, the CODA must produce frames in tiled format. Print this information in the debug output. Also print the color format in fourcc instead of the numeric value. Signed-off-by:
-
Philipp Zabel authored
Correctly store the rectangle of valid video data in the destination q_data before rounding up to macroblock size. This fixes the output of VIDIOC_G_SELECTION for the capture side compose rectangle. Signed-off-by:
-
Mauro Carvalho Chehab authored
As warned by checkpatch: WARNING: struct of_device_id should normally be const #318: FILE: drivers/media/platform/coda/imx-vdoa.c:318: +static struct of_device_id vdoa_dt_ids[] = { So, constify structs. Signed-off-by: -
Philipp Zabel authored
The i.MX6 Video Data Order Adapter's (VDOA) sole purpose is to convert from a custom macroblock tiled format produced by the CODA960 decoder into linear formats that can be used for scanout. Signed-off-by:
Philipp Zabel <philipp.zabel@gmail.com> Signed-off-by:
-
Philipp Zabel authored
Add a DT binding documentation for the Video Data Order Adapter (VDOA) of the Freescale i.MX6 SoC. Also, add the compatible property and correct clock to the device tree to match the documentation. Signed-off-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Markus Elfring authored
Use space characters at some source code places according to the Linux coding style convention. Signed-off-by:
Markus Elfring <elfring@users.sourceforge.net> Signed-off-by:
-
Markus Elfring authored
A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle software. Signed-off-by:
-
Kevin Hilman authored
Add basic support for initialization via DT Signed-off-by:
Kevin Hilman <khilman@baylibre.com> Signed-off-by:
-
Kevin Hilman authored
Acked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Kevin Hilman authored
Video capture subdevs may be over I2C and may sleep during xfer, so we cannot do IRQ-disabled locking when calling the subdev. The IRQ-disabled locking is meant to protect the DMA queue list throughout the rest of the driver, so update the locking in [start|stop]_streaming to protect just this list, and update the irqlock comment to reflect what it actually protects. Suggested-by:
-
Kevin Hilman authored
Remove hard-coded I2C adapter in favor of getting the ID from platform_data. Signed-off-by:
Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by:
-
Kevin Hilman authored
Fix problems with automatic module loading by adding MODULE_ALIAS. Also fix various load-time errors cause by incorrect or not present platform_data. Acked-by:
-
Randy Dunlap authored
Fix dm1105 build error when CONFIG_I2C_ALGOBIT=m and CONFIG_DVB_DM1105=y. drivers/built-in.o: In function `dm1105_probe': dm1105.c:(.text+0x2836e7): undefined reference to `i2c_bit_add_bus' Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Reported-by:
kbuild test robot <fengguang.wu@intel.com> Cc: Javier Martinez Canillas <javier@osg.samsung.com> Cc: stable@vger.kernel.org # applies to 4.0 (maybe even 3.x) Signed-off-by:
-
Andrzej Hajda authored
Bool values should be negated using logical operators. Using bitwise operators results in unexpected and possibly incorrect results. Reported-by:
David Binderman <dcb314@hotmail.com> Signed-off-by:
Andrzej Hajda <a.hajda@samsung.com> Signed-off-by:
-
Pavel Machek authored
Mark me and Sakari as maintainers for Nokia N900 camera pieces. Signed-off-by:
Pavel Machek <pavel@ucw.cz> Signed-off-by:
-
Markus Elfring authored
A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle software. Signed-off-by:
-
Shyam Saini authored
When some other buffer is immediately copied into allocated region. Replace calls to kmalloc followed by a memcpy with a direct call to kmemdup. Signed-off-by:
Shyam Saini <mayhs11saini@gmail.com> Signed-off-by:
-
Santosh Kumar Singh authored
Fix to avoid possible exit file handle in error paths. Signed-off-by:
Santosh Kumar Singh <kumar.san1093@gmail.com> Signed-off-by:
-
Santosh Kumar Singh authored
Fix to avoid possible exit file handle in error paths. Signed-off-by:
-
Santosh Kumar Singh authored
Fix to avoid possible memory leak and exit file handle in error paths. Signed-off-by:
-
Santosh Kumar Singh authored
Fix to avoid possible memory leak and exit file handle in error paths. Signed-off-by:
-
Santosh Kumar Singh authored
Fix to avoid possible memory leak and exit file handle in error paths. Signed-off-by:
-
Kees Cook authored
Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. These were identified during allyesconfig builds of x86, arm, and arm64, with most initializer fixes extracted from grsecurity. Signed-off-by:
Kees Cook <keescook@chromium.org> Signed-off-by:
-
Kees Cook authored
Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. These were identified during allyesconfig builds of x86, arm, and arm64, with most initializer fixes extracted from grsecurity. Signed-off-by:
-
Sudip Mukherjee authored
If dvb_attach() fails then we were just printing an error message and exiting but the memory allocated to state was not released. Signed-off-by:
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk> Signed-off-by:
-
Sean Young authored
tx-only RC devices do not have a receive buffer. Signed-off-by:
Sean Young <sean@mess.org> Signed-off-by:
-
Sean Young authored
LIRC_SET_REC_TIMEOUT can fail if the value returned by LIRC_GET_MIN_TIMEOUT is set due to rounding errors. Signed-off-by:
-
Sean Young authored
The current message has some wanted spaces on it: rc_core: Loaded IR protocol module ir-jvc-decoder, but protocol jvc still not available Merge it into a single line. Signed-off-by:
-
Sean Young authored
An RC device which is transmit-only shouldn't have the LIRC_CAN_REC_MODE2 feature. Signed-off-by:
-
Martin Blumenstingl authored
The GeekBox ships with a 12 button remote control which seems to use the NEC protocol. The button keycodes were captured with the "ir-keytable" tool (ir-keytable -p $PROTOCOL -t; human_button_pusher). Signed-off-by:
Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by:
-
Sean Wang authored
This patch adds documentation for devicetree bindings for consumer Mediatek IR controller. Signed-off-by:
Sean Wang <sean.wang@mediatek.com> Acked-by:
-
Sean Wang authored
Most IR drivers uses the same label to identify the scancode/key table they used by multiple bindings and lack explanation well. So move the shared property into a common place and give better explanation. Signed-off-by:
-
Sean Wang authored
This patch adds driver for IR controller on MT7623 SoC. and should also work on similar Mediatek SoC. Currently testing successfully on NEC and SONY remote controller only but it should work on others (lirc, rc-5 and rc-6). Signed-off-by:
-
Sean Young authored
As reported by kernel build test: In file included from arch/arm/mach-omap2/pdata-quirks.c:15:0: >> arch/arm/mach-omap2/pdata-quirks.c:536:49: error: 'rx51_lirc_data' undeclared here (not in a function) OF_DEV_AUXDATA("nokia,n900-ir", 0, "n900-ir", &rx51_lirc_data), ^ include/linux/of_platform.h:52:21: note: in definition of macro 'OF_DEV_AUXDATA' .platform_data = _pdata } ^~~~~~ Since "a92def1b [media] ir-rx51: port to rc-core" the build fails on some arm configurations. Reported-by:
-
- 30 Jan, 2017 4 commits
-
-
Scott Matheina authored
Fixed checkpatch check blank line before closing brace '}' Signed-off-by:
Scott Matheina <scott@matheina.com> Signed-off-by:
-
Scott Matheina authored
Fixed Checkpatch check "Alignment should match open parenthesis" Signed-off-by:
-
Baruch Siach authored
Simplifies return value logic of adv7170_set_fmt(). Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Baruch Siach authored
The loop over the ov2659_formats[] array just a few lines above verifies that mf->code matches the selected array entry. Signed-off-by:
-
