Re: [PATCH v5] media: platform: Renesas IMR driver

2017-06-24 Thread Sergei Shtylyov
Hello! On 03/17/2017 05:24 PM, Hans Verkuil wrote: Sorry for the long wait before I got around to reviewing this, but here are (finally!) my review comments. Addressing your comments took significant time too, and I wasn't able to address all of them yet... On 03/09/17 21:08, Sergei Sh

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-06-07 Thread Sergei Shtylyov
Hello! On 06/07/2017 10:26 AM, Hans Verkuil wrote: Any progress on this? Yes. :-) There where a bunch of comments, I think I've addresses most of those (except those I didn't quite understand). but I haven't seen anything since. I'm still busy documenting the driver. :-( R

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-06-07 Thread Hans Verkuil
Any progress on this? There where a bunch of comments, but I haven't seen anything since. Regards, Hans

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-05-07 Thread Kuninori Morimoto
Hi Laurent > > >> Laurent: what do you think about the need for SoC-specific compatible > > >> values for the various IM* blocks? > > > > > > There's no documented IP core version register, but when dumping all > > > configuration registers on H3 and M3-W I noticed that register 0x002c, not > >

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-05-03 Thread Laurent Pinchart
Hi Geert, On Wednesday 03 May 2017 09:22:00 Geert Uytterhoeven wrote: > On Tue, May 2, 2017 at 11:17 PM, Laurent Pinchart wrote: > > On Wednesday 22 Mar 2017 10:34:16 Geert Uytterhoeven wrote: > >> On Thu, Mar 9, 2017 at 9:08 PM, Sergei Shtylyov wrote: > >>> --- /dev/null > >>> +++ media_tree/Docu

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-05-03 Thread Geert Uytterhoeven
Hi Laurent, On Tue, May 2, 2017 at 11:17 PM, Laurent Pinchart wrote: > On Wednesday 22 Mar 2017 10:34:16 Geert Uytterhoeven wrote: >> On Thu, Mar 9, 2017 at 9:08 PM, Sergei Shtylyov wrote: >> > --- /dev/null >> > +++ media_tree/Documentation/devicetree/bindings/media/rcar_imr.txt >> > @@ -0,0 +1,

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-05-02 Thread Laurent Pinchart
Hi Geert, On Wednesday 22 Mar 2017 10:34:16 Geert Uytterhoeven wrote: > On Thu, Mar 9, 2017 at 9:08 PM, Sergei Shtylyov wrote: > > --- /dev/null > > +++ media_tree/Documentation/devicetree/bindings/media/rcar_imr.txt > > @@ -0,0 +1,27 @@ > > +Renesas R-Car Image Renderer (Distortion Correction Eng

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-03-22 Thread Geert Uytterhoeven
On Thu, Mar 9, 2017 at 9:08 PM, Sergei Shtylyov wrote: > --- /dev/null > +++ media_tree/Documentation/devicetree/bindings/media/rcar_imr.txt > @@ -0,0 +1,27 @@ > +Renesas R-Car Image Renderer (Distortion Correction Engine) > +--- > + > +The i

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-03-17 Thread Hans Verkuil
Hi Sergei, Sorry for the long wait before I got around to reviewing this, but here are (finally!) my review comments. On 03/09/17 21:08, Sergei Shtylyov wrote: > From: Konstantin Kozhevnikov > > The image renderer, or the distortion correction engine, is a drawing > processor with a simple inst

Re: [PATCH v5] media: platform: Renesas IMR driver

2017-03-16 Thread Rob Herring
On Thu, Mar 09, 2017 at 11:08:03PM +0300, Sergei Shtylyov wrote: > From: Konstantin Kozhevnikov > > The image renderer, or the distortion correction engine, is a drawing > processor with a simple instruction system capable of referencing video > capture data or data in an external memory as the 2

[PATCH v5] media: platform: Renesas IMR driver

2017-03-09 Thread Sergei Shtylyov
From: Konstantin Kozhevnikov The image renderer, or the distortion correction engine, is a drawing processor with a simple instruction system capable of referencing video capture data or data in an external memory as the 2D texture data and performing texture mapping and drawing with respect to a