[PATCH] [media] mtk-mdp: Fix g_/s_selection capture/compose logic

From: Daniel Kurtz Experiments show that the: (1) mtk-mdp uses the _MPLANE form of CAPTURE/OUTPUT (2) CAPTURE types use CROP targets, and OUTPUT types use COMPOSE targets Signed-off-by: Daniel Kurtz Signed-off-by: Minghsiu Tsai

cron job: media_tree daily build: WARNINGS

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: Thu Apr 13 05:00:14 CEST 2017 media-tree git hash:4aed35ca73f6d9cfd5f7089ba5d04f5fb8623080 media_build

[PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular

The Makefile / Kconfig currently controlling compilation of this code is: clock/Makefile:obj-$(CONFIG_INTEL_ATOMISP) += vlv2_plat_clock.o atomisp/Kconfig:menuconfig INTEL_ATOMISP atomisp/Kconfig:bool "Enable support to Intel MIPI camera drivers" ...meaning that it currently is not

[PATCH 40/40] media: imx: set and propagate empty field, colorimetry params

This patch adds a call to imx_media_fill_empty_mbus_fields() in the *_try_fmt() functions at the sink pads, to set empty field order and colorimetry parameters. If the field order is set to ANY, choose the currently set field order at the sink pad. If the colorspace is set to DEFAULT, choose the

Re: [PATCH] [media] imx: csi: retain current field order and colorimetry setting as default

On 04/06/2017 08:25 AM, Philipp Zabel wrote: On Thu, 2017-04-06 at 16:10 +0100, Russell King - ARM Linux wrote: On Thu, Apr 06, 2017 at 05:01:52PM +0200, Philipp Zabel wrote: On Thu, 2017-04-06 at 15:05 +0100, Russell King - ARM Linux wrote: On Thu, Apr 06, 2017 at 03:55:29PM +0200, Philipp

[PATCH] [media] mceusb: TX -EPIPE (urb status = -32) lockup fix

Bug: Once IR blasting or mceusb device commands fail with mce_async_callback() TX -EPIPE error, all subsequent TX to device then fail with the same error. ... [ 249.986174] mceusb 1-1.2:1.0: requesting 38000 HZ carrier [ 249.986210] mceusb 1-1.2:1.0: send request called (size=0x4) [

et8ek8 camera on Nokia N900: trying to understand what is going on with modes

Hi! 5Mpix mode does not work on N900, which is something I'd like to understand. et8ek8_mode contains huge tables of register settings and parameter values, but it seems that they are not really independend. To test that theory, I started with checking values against each other. This is the

[PATCH v2 2/5] media: rc: meson-ir: make use of the bitfield macros

Make use of the bitfield macros thus partially hiding the complexity of dealing with bitfields. The patch also includes a minor fix to REG0_RATE_MASK, so far it was set to bit 0..10, but according to the spec it's bit 0..11. Signed-off-by: Heiner Kallweit Reviewed-by: Neil

[PATCH v2 4/5] media: rc: meson-ir: use readl_relaxed in the interrupt handler

We don't need the memory barriers here and an interrupt handler should be as fast as possible. Therefore switch to readl_relaxed. Signed-off-by: Heiner Kallweit Reviewed-by: Neil Armstrong --- v2: - added R-b --- drivers/media/rc/meson-ir.c | 7

[PATCH v2 3/5] media: rc: meson-ir: switch to managed rc device allocation / registration

Switch to the managed versions of rc_allocate_device/rc_register_device, thus simplifying the code. Signed-off-by: Heiner Kallweit Reviewed-by: Neil Armstrong --- v2: - added R-b --- drivers/media/rc/meson-ir.c | 18 -- 1 file

[PATCH v2 1/5] media: rc: meson-ir: remove irq from struct meson_ir

The irq number is used in the probe function only, therefore just use a local variable. Signed-off-by: Heiner Kallweit --- v2: - no changes --- drivers/media/rc/meson-ir.c | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git

[PATCH v2 5/5] media: rc: meson-ir: change irq name to to of node name

Switch the interrupt description to the default which is the of node name. This is more in line with the interrupt descriptions in other meson drivers. Signed-off-by: Heiner Kallweit --- v2: - no changes --- drivers/media/rc/meson-ir.c | 2 +- 1 file changed, 1

[PATCH v2 0/5] media: rc: meson-ir: series with smaller improvements

This series includes smaller improvements for the meson-ir driver. Tested on a Odroid C2. v2: - minor change to patch 2 - added Reviewed-by to patch 2, 3, 4 Heiner Kallweit (5): media: rc: meson-ir: remove irq from struct meson_ir media: rc: meson-ir: make use of the bitfield macros media:

Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware

Am Wed, 29 Mar 2017 18:43:00 +0200 schrieb Daniel Scheller : > From: Daniel Scheller > > Third iteration of the DD CineCTv6/FlexCT support patches with mostly > all things cleaned up that popped up so far. Obsoletes V1 and V2 > series. > > These

[PATCH 14/14] atomisp: remove UDS kernel code

UDS is another layer which actually boils down to some trivial assignments so remove it so inline the code. Signed-off-by: Alan Cox --- .../ia_css_isp_params.c| 12 --- .../ia_css_isp_params.c| 12 ---

[PATCH 13/14] atomisp: remove xnr3_0_5 and xnr3_0_11

These are not used in the driver so can go away. Signed-off-by: Alan Cox --- .../staging/media/atomisp/pci/atomisp2/Makefile|4 - .../kernels/xnr/xnr3_0_11/ia_css_xnr3_0_11.host.c | 155 .../kernels/xnr/xnr3_0_11/ia_css_xnr3_0_11.host.h |

[PATCH 12/14] atomisp: remove fixedbds kernel code

This is a whole pile of code that wraps a single assignment. Remove it and put the assignment in the caller. Once we have the kernels sorted we should revisit these and remove all the pointless 1 item structs that go with it. Signed-off-by: Alan Cox ---

[PATCH 11/14] atomisp: remove satm kernel

This isn't used so it can go in the bitbucket. Signed-off-by: Alan Cox --- .../staging/media/atomisp/pci/atomisp2/Makefile|1 - .../css2400/isp/kernels/satm/ia_css_satm.host.c| 27 --- .../css2400/isp/kernels/satm/ia_css_satm.host.h| 29

[PATCH 09/14] atomisp: remove sh_css_malloc indirections where we can

Where we know the buffer size is reasonably constrained we can just use kmalloc, and where it will be large vmalloc. This still leaves a pile in the middle. Signed-off-by: Alan Cox --- .../media/atomisp/pci/atomisp2/css2400/sh_css.c| 92 ++--

[PATCH 06/14] atomisp: remove most of the uses of atomisp_kernel_malloc

They can be replaced by kmalloc. There are a few that do need to pick kmalloc or vmalloc. Those we leave for the moment. Signed-off-by: Alan Cox --- .../atomisp/pci/atomisp2/atomisp_compat_css20.c|4 -- .../media/atomisp/pci/atomisp2/hmm/hmm_bo.c| 34

[PATCH 10/14] atomisp: remove contiguous handling

The base hmm MMU code doesn't support contiguous allocations (they BUG), so remove support from them from the higher levels of the heirarchy. We still need to unwind all these layers but it turns out that some of the init order stuff is rather sensitive and the simple cleanup breaks everything

[PATCH 08/14] atomisp: remove indirection from sh_css_malloc

We have one hard coded set of behaviour so unpick the indirection and function pointers. This isn't the whole story. A lot of the callers are known sizes and use cases so we can switch them directly to kmalloc later on. Signed-off-by: Alan Cox ---

[PATCH 07/14] atomisp: unwrap the _ex malloc/free functions

We are not using these for debugging or debug logging so remove the defines, trim and rename the functions. Signed-off-by: Alan Cox --- .../media/atomisp/pci/atomisp2/css2400/sh_css.c| 15 +++ .../atomisp/pci/atomisp2/css2400/sh_css_internal.h | 17

[PATCH 05/14] staging: atomisp: move mipi_info assignment to next line in __get_asd_from_port()

From: Daeseok Youn The line which is initializing mipi_info variable is too long to read. It would be placed in next line. Signed-off-by: Daeseok Youn Signed-off-by: Alan Cox ---

[PATCH 03/14] staging: atomisp: remove enable_isp_irq function and add disable_isp_irq

From: Daeseok Youn Enable/Disable ISP irq is switched with "enable" parameter of enable_isp_irq(). It would be better splited to two such as enable_isp_irq()/disable_isp_irq(). But the enable_isp_irq() is no use in atomisp_cmd.c file. So remove the enable_isp_irq()

[PATCH 04/14] staging: atomisp: replace ">asd[i]" with "asd" in __get_asd_from_port()

From: Daeseok Youn The address of isp->asd[i] is already assigned to local "asd" variable. ">asd[i]" would be replaced with just "asd". Signed-off-by: Daeseok Youn Signed-off-by: Alan Cox ---

[PATCH 02/14] staging/atomisp: fix spelling mistake: "falied" -> "failed"

From: Colin Ian King trivial fix to spelling mistake in dev_err error message Signed-off-by: Colin Ian King Signed-off-by: Alan Cox --- .../media/atomisp/pci/atomisp2/hmm/hmm_bo_dev.c|2 +- 1 file changed, 1

[PATCH 01/14] staging: atomisp: use local variable to reduce number of references

From: Daeseok Youn Define new local variable to reduce the number of reference. The new local variable is added to save the addess of dfs and used in atomisp_freq_scaling() function. Signed-off-by: Daeseok Youn Signed-off-by: Alan Cox

Re: please help with uninstall

Hi, On 2017-04-12 08:00 AM, Milan Čížek wrote: How to remove your product from my kernel? I tried make rmmod rminstall but this message stills in my syslog. Sorry for question, I'm linux newbie. [ 15.753993] WARNING: You are using an experimental version of the media stack.

Re: Looking for device driver advice

On 04/12/2017 04:29 PM, Patrick Doyle wrote: > Thank you again Hans. > > On Wed, Apr 12, 2017 at 9:58 AM, Hans Verkuil wrote: >> On 04/12/2017 03:13 PM, Patrick Doyle wrote: >>> The SAMA5 has a downsampler built into its LCD engine. Suppose I >>> wanted to treat that

Re: Looking for device driver advice

Thank you again Hans. On Wed, Apr 12, 2017 at 9:58 AM, Hans Verkuil wrote: > On 04/12/2017 03:13 PM, Patrick Doyle wrote: >> The SAMA5 has a downsampler built into its LCD engine. Suppose I >> wanted to treat that downsampler as an independent device and pass >> image

[PATCH] [media] xc5000: fix spelling mistake: "calibration"

From: Colin Ian King Trivial fix to spelling mistake on calibration, make Self lowercase and re-join multiple lined printk since checkpatch allows this coding style. Signed-off-by: Colin Ian King --- drivers/media/tuners/xc5000.c | 3 +-- 1

Re: [RFC PATCH 3/3] encoder-tpd12s015: keep the ls_oe_gpio on while the phys_addr is valid

On 04/12/2017 03:21 PM, Tomi Valkeinen wrote: > On 12/04/17 16:03, Hans Verkuil wrote: > >> I noticed while experimenting with this that tpd_disconnect() in >> drivers/gpu/drm/omapdrm/displays/encoder-tpd12s015.c isn't called when >> I disconnect the HDMI cable. Is that a bug somewhere? >> >> I

Re: Looking for device driver advice

On 04/12/2017 03:13 PM, Patrick Doyle wrote: > Thank you Hans, > I can modify (or work with Atmel/Microchip to have modified) the > atmel-isc driver, so I that's not an issue. > > With your feedback, I now have a target implementation to which I can aim. > > For now, I'll be happy when I can get

Re: [RFC PATCH 3/3] encoder-tpd12s015: keep the ls_oe_gpio on while the phys_addr is valid

On 12/04/17 16:03, Hans Verkuil wrote: > I noticed while experimenting with this that tpd_disconnect() in > drivers/gpu/drm/omapdrm/displays/encoder-tpd12s015.c isn't called when > I disconnect the HDMI cable. Is that a bug somewhere? > > I would expect that tpd_connect and tpd_disconnect are

Re: Looking for device driver advice

Thank you Hans, I can modify (or work with Atmel/Microchip to have modified) the atmel-isc driver, so I that's not an issue. With your feedback, I now have a target implementation to which I can aim. For now, I'll be happy when I can get any image at all through my pipeline... wish me luck! :-)

Re: [RFC PATCH 3/3] encoder-tpd12s015: keep the ls_oe_gpio on while the phys_addr is valid

On 04/12/2017 03:03 PM, Hans Verkuil wrote: > Hi Tomi, > > On 04/10/2017 01:59 PM, Tomi Valkeinen wrote: >> On 08/04/17 13:11, Hans Verkuil wrote: >> >>> So, this is a bit of a blast from the past since the omap4 CEC development >>> has been on hold for almost a year. But I am about to resume my

Re: [RFC PATCH 3/3] encoder-tpd12s015: keep the ls_oe_gpio on while the phys_addr is valid

Hi Tomi, On 04/10/2017 01:59 PM, Tomi Valkeinen wrote: > On 08/04/17 13:11, Hans Verkuil wrote: > >> So, this is a bit of a blast from the past since the omap4 CEC development >> has been on hold for almost a year. But I am about to resume my work on this >> now that the CEC framework was

[GIT PULL FOR v4.12] Add vimc virtual test driver

Finally merge this for 4.12. Regards, Hans The following changes since commit 4aed35ca73f6d9cfd5f7089ba5d04f5fb8623080: [media] v4l2-tpg: don't clamp XV601/709 to lim range (2017-04-10 14:58:06 -0300) are available in the git repository at:

Re: Looking for device driver advice

Hi Patrick, On 04/10/2017 10:13 PM, Patrick Doyle wrote: > I am looking for advice regarding the construction of a device driver > for a MIPI CSI2 imager (a Sony IMX241) that is connected to a > MIPI<->Parallel converter (Toshiba TC358748) wired into a parallel > interface on a Soc (a

[GIT PULL FOR v4.12] New ov5645 and ov5647 drivers

Add the ov5645 and ov5647 drivers. This supersedes an earlier ov5645-only pull request. Having separate pull requests for these drivers would create a Kconfig conflict, so I've combined them in one pull request. Regards, Hans The following changes since commit

please help with uninstall

How to remove your product from my kernel? I tried make rmmod rminstall but this message stills in my syslog. Sorry for question, I'm linux newbie. [   15.753993] WARNING: You are using an experimental version of the media stack.     As the driver is backported to an older kernel,

Re: [PATCH v6 17/39] platform: add video-multiplexer subdevice driver

Hi Steve, On Tue, Apr 11, 2017 at 05:50:58PM -0700, Steve Longerbeam wrote: > > > On 04/04/2017 05:47 AM, Sakari Ailus wrote: > >Hi Steve, Philipp and Pavel, > > > >On Mon, Mar 27, 2017 at 05:40:34PM -0700, Steve Longerbeam wrote: > >>From: Philipp Zabel > >> > >>This

Re: [PATCH] [media] imx: csi: retain current field order and colorimetry setting as default

On 04/06/2017 06:01 PM, Philipp Zabel wrote: > On Thu, 2017-04-06 at 17:43 +0200, Hans Verkuil wrote: >> On 04/06/2017 04:54 PM, Philipp Zabel wrote: >>> On Thu, 2017-04-06 at 16:20 +0200, Hans Verkuil wrote: On 04/06/2017 03:55 PM, Philipp Zabel wrote: > If the the field order is set to