Re: Is IIO the appropriate subsystem for a thermal camera sensor?

On 26 October 2015 08:21:07 GMT+00:00, Jean-Michel Hautbois wrote: >Hi Lucas, > >2015-10-26 8:53 GMT+01:00 Daniel Baluta : >> Hi Lucas, >> >> Adding linux-iio and linux-media, I hope you don't mind. >> >> On 10/23/2015 06:58 PM, Lucas

Re: Is IIO the appropriate subsystem for a thermal camera sensor?

Hi Lucas, 2015-10-26 8:53 GMT+01:00 Daniel Baluta : > Hi Lucas, > > Adding linux-iio and linux-media, I hope you don't mind. > > On 10/23/2015 06:58 PM, Lucas Magasweran wrote: >> >> Hi Daniel, >> >> My colleague, Roberto Cornetti, attended your IIO talk at LinuxCon >>

Re: PCIe capture driver

> No, use V4L2. What you do with the frame after it has been captured > into memory has no relevance to the API you use to capture into memory. Ran, I've built many open and closed source Linux drivers over the last 10 years - so I can speak with authority on this. Hans is absolutely correct,

Re: Is IIO the appropriate subsystem for a thermal camera sensor?

Hi Lucas, Adding linux-iio and linux-media, I hope you don't mind. On 10/23/2015 06:58 PM, Lucas Magasweran wrote: Hi Daniel, My colleague, Roberto Cornetti, attended your IIO talk at LinuxCon recently and is using the IIO subsystem for an I2C IMU. Glad to hear that :) My question is if

[PATCH 02/19] media: Introduce internal index for media entities

From: Sakari Ailus The internal index can be used internally by the framework in order to keep track of entities for a purpose or another. The internal index is constant while it's registered to a media device, but the same index may be re-used once the entity

[PATCH 09/19] v4l: exynos4-is: Use the new media_entity_graph_walk_start() interface

Signed-off-by: Sakari Ailus --- drivers/media/platform/exynos4-is/media-dev.c | 31 +-- drivers/media/platform/exynos4-is/media-dev.h | 1 + 2 files changed, 21 insertions(+), 11 deletions(-) diff --git

[PATCH 07/19] media: Use the new media_entity_graph_walk_start()

Signed-off-by: Sakari Ailus --- drivers/media/media-entity.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/drivers/media/media-entity.c b/drivers/media/media-entity.c index bf3c31f..4161dc7 100644 --- a/drivers/media/media-entity.c

[PATCH 03/19] media: Add an API to manage entity enumerations

From: Sakari Ailus This is useful in e.g. knowing whether certain operations have already been performed for an entity. The users include the framework itself (for graph walking) and a number of drivers. Signed-off-by: Sakari Ailus

[PATCH 11/19] v4l: vsp1: Use the new media_entity_graph_walk_start() interface

Signed-off-by: Sakari Ailus --- drivers/media/platform/vsp1/vsp1_video.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/media/platform/vsp1/vsp1_video.c b/drivers/media/platform/vsp1/vsp1_video.c index f741582..ce10d86 100644 ---

[PATCH 19/19] media: Rename MEDIA_ENTITY_ENUM_MAX_ID as MEDIA_ENTITY_ENUM_STACK_ALLOC

The purpose of the macro has changed, rename it accordingly. It is not and should no longer be used in drivers directly, but only for the purpose for defining how many bits can be allocated from the stack for entity enumerations. Signed-off-by: Sakari Ailus ---

[PATCH 10/19] v4l: xilinx: Use the new media_entity_graph_walk_start() interface

Signed-off-by: Sakari Ailus --- drivers/media/platform/xilinx/xilinx-dma.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/media/platform/xilinx/xilinx-dma.c b/drivers/media/platform/xilinx/xilinx-dma.c index bc244a0..0a19824 100644 ---

[PATCH 00/19] Unrestricted media entity ID range support

Hi, This is an update to my previous RFC patchset here: In addition to the problems the patchset previously resolved and features it implemented: - unrestricted media entity ID support and - API to manage entity enumerations this

[PATCH 15/19] v4l: vsp1: Use media entity enumeration API

From: Sakari Ailus Signed-off-by: Sakari Ailus --- drivers/media/platform/vsp1/vsp1_video.c | 45 ++-- 1 file changed, 31 insertions(+), 14 deletions(-) diff --git

[PATCH 12/19] media: Use entity enums in graph walk

This will also mean that the necessary graph related data structures will be allocated dynamically, removing the need for maximum ID checks. Signed-off-by: Sakari Ailus --- drivers/media/media-entity.c | 16 ++-- include/media/media-entity.h | 2 +- 2

[PATCH 17/19] staging: v4l: omap4iss: Use media entity enum API

From: Sakari Ailus Signed-off-by: Sakari Ailus --- drivers/staging/media/omap4iss/iss.c | 15 +++ drivers/staging/media/omap4iss/iss.h | 4 ++-- drivers/staging/media/omap4iss/iss_video.c | 13 +++--

[PATCH 14/19] v4l: omap3isp: Use media entity enumeration API

From: Sakari Ailus Signed-off-by: Sakari Ailus --- drivers/media/platform/omap3isp/isp.c | 21 + drivers/media/platform/omap3isp/isp.h | 5 +++-- drivers/media/platform/omap3isp/ispccdc.c | 2 +-

[PATCH 05/19] media: Move media graph state for streamon/off to the pipeline

The struct media_entity_graph was allocated in the stack, limiting the number of entities that could be reasonably allocated. Instead, move the struct to struct media_pipeline which is typically allocated using kmalloc() instead. The intent is to keep the enumeration around for later use for the

[PATCH 08/19] v4l: omap3isp: Use the new media_entity_graph_walk_start() interface

Signed-off-by: Sakari Ailus --- drivers/media/platform/omap3isp/isp.c | 63 ++ drivers/media/platform/omap3isp/isp.h | 4 +- drivers/media/platform/omap3isp/ispvideo.c | 19 - drivers/media/platform/omap3isp/ispvideo.h

[PATCH 18/19] staging: v4l: omap4iss: Use the new media_entity_graph_walk_start() interface

Signed-off-by: Sakari Ailus --- drivers/staging/media/omap4iss/iss.c | 59 +++--- drivers/staging/media/omap4iss/iss.h | 4 +- drivers/staging/media/omap4iss/iss_video.c | 36 ++

[PATCH 16/19] staging: omap4iss: Fix sub-device power management code

The same bug was present in the omap4iss driver as was in the omap3isp driver. The code got copied to the omap4iss driver while broken. Fix the omap4iss driver as well. Signed-off-by: Sakari Ailus --- drivers/staging/media/omap4iss/iss.c | 4 ++-- 1 file changed, 2

[PATCH 06/19] media: Amend media graph walk API by init and cleanup functions

Add media_entity_graph_walk_init() and media_entity_graph_walk_cleanup() functions in order to dynamically allocate memory for the graph. This is not done in media_entity_graph_walk_start() as there are situations where e.g. correct error handling, that itself may not fail, requires successful

[PATCH 04/19] media: Move struct media_entity_graph definition up

It will be needed in struct media_pipeline shortly. Signed-off-by: Sakari Ailus --- include/media/media-entity.h | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/include/media/media-entity.h b/include/media/media-entity.h

[PATCH 01/19] media: Enforce single entity->pipe in a pipeline

If a different entity->pipe in a pipeline was encountered, a warning was issued but the execution continued as if nothing had happened. Return an error instead right there. Signed-off-by: Sakari Ailus --- drivers/media/media-entity.c | 7 ++- 1 file changed, 6

PVR-250 Composite 3 unavailable [Re: ivtv driver]

On October 26, 2015 7:13:52 PM EDT, Warren Sturm wrote: >Hi Andy. > >I don't know whether this was intended but the pvr250 lost the >composite 3 input when going from kernel version 4.1.10 to 4.2.3. > >This is on a Fedora 22 x86_64 system. > > >Thanks for any insight.

[PATCH 13/19] media: Keep using the same graph walk object for a given pipeline

Initialise a given graph walk object once, and then keep using it whilst the same pipeline is running. Once the pipeline is stopped, release the graph walk object. Signed-off-by: Sakari Ailus --- drivers/media/media-entity.c | 17 +++--

Re: PCIe capture driver

On 10/27/2015 02:04, Ran Shalit wrote: > On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >>> No, use V4L2. What you do with the frame after it has been captured >>> into memory has no relevance to the API you use to capture into memory. >> >> Ran, I've built many open

Re: [PATCH 0/8] add missing of_node_put

From: Julia Lawall Date: Sun, 25 Oct 2015 14:56:59 +0100 > The various for_each device_node iterators performs an of_node_get on each > iteration, so a break out of the loop requires an of_node_put. > > The complete semantic patch that fixes this problem is >

cron job: media_tree daily build: OK

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 Oct 27 04:00:15 CET 2015 git branch: test git hash: 79f5b6ae960d380c829fb67d5dadcd1d025d2775 gcc

[RFC] Snapshot Mode and Interrupt Trigger

Hi, I was searching in the list if there is some RFC to implement some kind of snapshot mode in the API. I found a conversation [1] but it turned to flash capabilities. The thing is, there are sensors with hardware trigger modes (a.k.a. snapshot modes) but there is not any standard form to deal

Re: PCIe capture driver

>> Hans is absolutely correct, don't make the mistake of going >> proprietary with your API. Take advantage of the massive amount of > Thank you very much for these valuable comments. > If I may ask one more on this issue: > Is there an example in linux tree, for a pci device which is used both >

Re: PCIe capture driver

On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >> No, use V4L2. What you do with the frame after it has been captured >> into memory has no relevance to the API you use to capture into memory. > > Ran, I've built many open and closed source Linux drivers over the > last

Re: PCIe capture driver

Hi Ran, 2015-10-26 18:04 GMT+01:00 Ran Shalit : > On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >>> No, use V4L2. What you do with the frame after it has been captured >>> into memory has no relevance to the API you use to capture into memory. >>