Re: [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings

2016-05-26 Thread Marek Szyprowski
Hello, On 2016-05-25 19:36, Rob Herring wrote: On Wed, May 25, 2016 at 11:18:59AM -0400, Javier Martinez Canillas wrote: Hello Marek, On 05/24/2016 09:31 AM, Marek Szyprowski wrote: Use generic reserved memory bindings and mark old, custom properties as obsoleted. Signed-off-by: Marek Szypr

Re: [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings

2016-05-26 Thread Krzysztof Kozlowski
On 05/24/2016 03:31 PM, Marek Szyprowski wrote: > Use generic reserved memory bindings and mark old, custom properties > as obsoleted. > > Signed-off-by: Marek Szyprowski > --- > .../devicetree/bindings/media/s5p-mfc.txt | 39 > +- > 1 file changed, 31 insertions(+)

cron job: media_tree daily build: OK

2016-05-26 Thread Hans Verkuil
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: Fri May 27 04:00:28 CEST 2016 git branch: test git hash: bc2b80ee3490651904f121eac1c8fb7652d48253 gcc versi

Re: How should I use kernel-defined i2c structs in this driver

2016-05-26 Thread Antti Palosaari
On 05/26/2016 04:59 PM, Andrey Utkin wrote: Could anybody please give a hint - which kernel-defined i2c objects, and how many of them, I need to define and use to substitute these driver-defined functions i2c_read(), i2c_write() ? https://github.com/bluecherrydvr/linux/blob/release/tw5864/1.16/dr

Re: [PATCH v4 1/7] of: reserved_mem: add support for using more than one region for given device

2016-05-26 Thread Rob Herring
On Tue, May 24, 2016 at 8:31 AM, Marek Szyprowski wrote: > This patch allows device drivers to initialize more than one reserved > memory region assigned to given device. When driver needs to use more > than one reserved memory region, it should allocate child devices and > initialize regions by i

How should I use kernel-defined i2c structs in this driver

2016-05-26 Thread Andrey Utkin
Could anybody please give a hint - which kernel-defined i2c objects, and how many of them, I need to define and use to substitute these driver-defined functions i2c_read(), i2c_write() ? https://github.com/bluecherrydvr/linux/blob/release/tw5864/1.16/drivers/media/pci/tw5864/tw5864-config.c In a wo

Re: [v4l-utils PATCH 1/2] libmediactl: Drop length argument from media_get_entity_by_name()

2016-05-26 Thread Sakari Ailus
On Thu, May 26, 2016 at 03:07:41PM +0300, Laurent Pinchart wrote: > Hi Sakari, > > On Tuesday 24 May 2016 23:50:44 Sakari Ailus wrote: > > On Tue, May 24, 2016 at 08:09:37PM +0300, Laurent Pinchart wrote: > > ... > > > > > > + if (strcmp(entity->info.name, name) == 0) > > > > > > W

Re: [v4l-utils PATCH 1/2] libmediactl: Drop length argument from media_get_entity_by_name()

2016-05-26 Thread Laurent Pinchart
Hi Sakari, On Tuesday 24 May 2016 23:50:44 Sakari Ailus wrote: > On Tue, May 24, 2016 at 08:09:37PM +0300, Laurent Pinchart wrote: > ... > > > > + if (strcmp(entity->info.name, name) == 0) > > > > While the kernel API guarantees that entity->info.name will be NULL- > > terminated, wouldn

Re: [PATCH v2 2/2] media: Add a driver for the ov5645 camera sensor.

2016-05-26 Thread Todor Tomov
Hi Hans, Thanks for the review. On 05/23/2016 01:36 PM, Hans Verkuil wrote: > Hi Todor, > > Thanks for the patch series! I got a few comments: > > On 05/18/2016 01:50 PM, Todor Tomov wrote: >> The ov5645 sensor from Omnivision supports up to 2592x1944 >> and CSI2 interface. >> >> The driver add