Hi Ivaylo,
On Fri, Jan 20, 2017 at 09:59:13AM +0200, Ivaylo Dimitrov wrote:
> Hi,
>
> On 19.01.2017 23:49, Sakari Ailus wrote:
> >Hi Pavel,
> >
> >On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> >>From: Sakari Ailus
> >>
> >>In the vast majority of cases the
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> This is a set of three media entity subdevice drivers for the i.MX
> Image Converter. The i.MX IC module contains three independent
> "tasks":
>
> - Pre-processing Encode task: video frames are routed directly from
> the CSI and can be scaled,
Hi Steve, Philipp,
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> In version 3:
>
> Changes suggested by Rob Herring :
>
> - prepended FIM node properties with vendor prefix "fsl,".
>
> - make mipi csi-2 receiver compatible string SoC specific:
>
From: Philipp Zabel
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
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: Michael Tretter
Acked-by: Philipp Zabel
---
From: Philipp Zabel
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
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> From: Philipp Zabel
>
> Signed-off-by: Philipp Zabel
> ---
> Documentation/media/uapi/mediactl/media-types.rst | 22 ++
> include/uapi/linux/media.h| 6
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
The VDOA is able to transform the NV12 custom macroblock tiled format of
the CODA to YUYV format. If and only if the VDOA is available, the
driver can also provide YUYV support.
While the driver is configured to produce YUYV output, the CODA must be
configured to produce NV12 macroblock tiled
From: Philipp Zabel
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: Philipp Zabel
From: Philipp Zabel
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: Philipp Zabel
Hello,
This is v4 of a patch series that adds support for the Video Data Order
Adapter (VDOA) that can be found on Freescale i.MX6. It converts the
macroblock tiled format produced by the CODA 960 video decoder to a
raster-ordered format for scanout.
Changes since v3:
- Patch 2/7: Add my
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> From: Philipp Zabel
>
> This driver can handle SoC internal and external video bus multiplexers,
> controlled either by register bit fields or by a GPIO. The subdevice
> passes through frame interval and mbus configuration
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> This is the camera interface driver that provides the v4l2
> user interface. Frames can be received from various sources:
>
> - directly from SMFC for capturing unconverted images directly from
> camera sensors.
>
> - from the IC pre-process
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> This driver is based on ov5640_mipi.c from Freescale imx_3.10.17_1.0.0_beta
> branch, modified heavily to bring forward to latest interfaces and code
> cleanup.
>
> Signed-off-by: Steve Longerbeam
> ---
>
On 01/20/2017 07:40 PM, Steve Longerbeam wrote:
> Hi Hans, Philipp,
>
>
> On 01/20/2017 08:31 AM, Philipp Zabel wrote:
>> Hi Hans,
>>
>> On Fri, 2017-01-20 at 14:52 +0100, Hans Verkuil wrote:
>>> Hi Steve, Philipp,
>>>
>>> On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
In version 3:
Hi Sean,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.10-rc4 next-20170120]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Sean-Young/IR-fixes-for-v4-11
Hi there,
Apologies if no-one wants to hear about this. But there was a patch
submitted in 3.17 for geniatech t220 / august dvb-t210 v1. And it
seems to have stopped working for some reason. (yet the patch code is
still there. I reached out to the birthplace / author of the patch,
but
Hi Sean,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.10-rc4 next-20170120]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Sean-Young/IR-fixes-for-v4-11/20170121
From: Sudip Mukherjee
Modify lirc_parallel driver to use the new parallel port device model.
Signed-off-by: Sudip Mukherjee
---
Resending after more than one year.
Prevoius patch is at
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: Sat Jan 21 05:00:16 CET 2017
media-tree git hash:40eca140c404505c09773d1c6685d818cb55ab1a
media_build
This patch add simple allocator for CMA regions
Signed-off-by: Benjamin Gaignard
---
drivers/simpleallocator/Kconfig| 7 +
drivers/simpleallocator/Makefile | 1 +
drivers/simpleallocator/simple-allocator-cma.c | 187
This is the core of simple allocator module.
It aim to offert one common ioctl to allocate specific memory.
Signed-off-by: Benjamin Gaignard
---
Documentation/simple-allocator.txt | 81 +++
drivers/Kconfig | 2
The goal of this RFC is to understand if a common ioctl for specific memory
regions allocations is needed/welcome.
Obviously it will not replace allocation done in linux kernel frameworks like
v4l2, drm/kms or others, but offer an alternative when you don't want/need to
use them for buffer
Hi Hans,
On Fri, 2017-01-20 at 15:54 +0100, Hans Verkuil wrote:
> Looks good to me.
>
> Philipp, just let me know if this is ready for merging, or you can make a pull
> request for Mauro yourself if you prefer.
Yes, with the recent fixes I think this is ready for merging.
If you don't mind
Looks good to me.
Philipp, just let me know if this is ready for merging, or you can make a pull
request for Mauro yourself if you prefer.
Regards,
Hans
On 01/20/2017 03:00 PM, Michael Tretter wrote:
> Hello,
>
> This is v4 of a patch series that adds support for the Video Data Order
On 01/12/2017 09:35 AM, Hans Verkuil wrote:
> Second attempt, this time with the [ANN] prefix in the hope more people will
> reply...
>
>
> Mauro is on vacation until the 21st, so he asked me to see who will go to the
> ELC
> in Portland in February.
>
> If there are enough core developers
Hello Marek,
On 01/20/2017 05:08 AM, Marek Szyprowski wrote:
[snip]
>>
>> This seems to be caused by some needed clocks to access the power domains
>> to be gated, since I don't get these erros when passing clk_ignore_unused
>> as parameter in the kernel command line.
>
> I think that those
An RC device which is transmit-only shouldn't have the
LIRC_CAN_REC_MODE2 feature.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc/ir-lirc-codec.c
tx-only RC devices do not have a receive buffer.
Signed-off-by: Sean Young
---
drivers/media/rc/lirc_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index 7f5d109..18b4dae 100644
---
rc_core: Loaded IR protocol module ir-jvc-decoder, but
protocol jvc still not available
Signed-off-by: Sean Young
---
drivers/media/rc/rc-main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/media/rc/rc-main.c
Testing of lirc uncovered some issue with tx-only devices, and some
other minor issues.
Sean Young (4):
[media] lirc: fix transmit-only read features
[media] rc: remove excessive spaces from error message
[media] lirc: LIRC_GET_MIN_TIMEOUT should be in range
[media] lirc: fix null
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
---
drivers/media/rc/ir-lirc-codec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/ir-lirc-codec.c
Hi Hans,
On Fri, 2017-01-20 at 14:52 +0100, Hans Verkuil wrote:
> Hi Steve, Philipp,
>
> On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
> > In version 3:
> >
> > Changes suggested by Rob Herring :
> >
> > - prepended FIM node properties with vendor prefix "fsl,".
> >
> >
Hi Hans, Philipp,
On 01/20/2017 08:31 AM, Philipp Zabel wrote:
Hi Hans,
On Fri, 2017-01-20 at 14:52 +0100, Hans Verkuil wrote:
Hi Steve, Philipp,
On 01/07/2017 03:11 AM, Steve Longerbeam wrote:
In version 3:
Changes suggested by Rob Herring :
- prepended FIM node
Hi Javier,
On 2017-01-19 15:56, Javier Martinez Canillas wrote:
Thanks a lot for your feedback.
On 01/19/2017 11:17 AM, Marek Szyprowski wrote:
On 2017-01-18 01:30, Javier Martinez Canillas wrote:
Commit 15f90ab57acc ("[media] exynos-gsc: Make driver functional when
CONFIG_PM is unset")
Hello Marek,
On 01/20/2017 05:37 AM, Marek Szyprowski wrote:
[snip]
>> I'll post a proper patch for the exynos5800.dtsi, to override the
>> clocks in the gsc_pd device node.
>>
>> I also see that the two power domains that fail to be disabled msc_pd
>> (power-domain@10044120) and isp_pd
Hello,
On 01/20/2017 07:06 AM, Javier Martinez Canillas wrote:
> Hello Marek,
>
> On 01/20/2017 05:37 AM, Marek Szyprowski wrote:
>
> [snip]
>>
>> Please send this patch instead of adding more clocks to the power domains.
>> This way we will avoid adding more dependencies to userspace (DT ABI).
Hi Javier,
On 2017-01-19 18:51, Javier Martinez Canillas wrote:
On 01/19/2017 11:56 AM, Javier Martinez Canillas wrote:
On 01/19/2017 11:17 AM, Marek Szyprowski wrote:
[snip]
Also when removing the exynos_gsc driver, I get the same error:
# rmmod s5p_mfc
[ 106.405972] s5p-mfc
Hello Marek,
On 01/20/2017 05:08 AM, Marek Szyprowski wrote:
> Hi Javier,
>
[snip]
>> Ok, I misunderstood the relationship between runtime PM and the power domains
>> then. I thought the power domains were only powered on when the runtime PM
>> framework resumed an associated device (i.e:
Hello,
On 01/19/2017 07:36 PM, Javier Martinez Canillas wrote:
> Commit 15f90ab57acc ("[media] exynos-gsc: Make driver functional when
> CONFIG_PM is unset") removed the implicit dependency that the driver
> had with CONFIG_PM, since it relied on the config option to be enabled.
>
> In order to
Hi,
On 19.01.2017 23:49, Sakari Ailus wrote:
Hi Pavel,
On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
From: Sakari Ailus
In the vast majority of cases the bus type is known to the driver(s)
since a receiver or transmitter can only support a single one.
42 matches
Mail list logo