[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-08-04 Thread Laurent Pinchart
On Monday 04 August 2014 09:30:04 Daniel Vetter wrote: > On Fri, Aug 01, 2014 at 02:58:21PM +0200, Laurent Pinchart wrote: > > On Thursday 31 July 2014 15:16:21 Randy Dunlap wrote: > >> On 05/12/14 11:04, Randy Dunlap wrote: > >>> On 05/12/2014 08:54 AM, Daniel Vetter wrote: > On Mon, May 12,

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-08-04 Thread Daniel Vetter
On Fri, Aug 01, 2014 at 02:58:21PM +0200, Laurent Pinchart wrote: > Hi Randy, > > On Thursday 31 July 2014 15:16:21 Randy Dunlap wrote: > > On 05/12/14 11:04, Randy Dunlap wrote: > > > On 05/12/2014 08:54 AM, Daniel Vetter wrote: > > >> On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote:

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-08-01 Thread Randy Dunlap
On 08/01/14 05:58, Laurent Pinchart wrote: > Hi Randy, > > On Thursday 31 July 2014 15:16:21 Randy Dunlap wrote: >> On 05/12/14 11:04, Randy Dunlap wrote: >>> On 05/12/2014 08:54 AM, Daniel Vetter wrote: On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote: > On 05/12/2014 01:58 A

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-08-01 Thread Laurent Pinchart
Hi Randy, On Thursday 31 July 2014 15:16:21 Randy Dunlap wrote: > On 05/12/14 11:04, Randy Dunlap wrote: > > On 05/12/2014 08:54 AM, Daniel Vetter wrote: > >> On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote: > >>> On 05/12/2014 01:58 AM, Daniel Vetter wrote: > On Mon, May 12, 201

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-07-31 Thread Randy Dunlap
On 05/12/14 11:04, Randy Dunlap wrote: > On 05/12/2014 08:54 AM, Daniel Vetter wrote: >> On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote: >>> On 05/12/2014 01:58 AM, Daniel Vetter wrote: On Mon, May 12, 2014 at 06:24:57PM +1000, Dave Airlie wrote: >>> >>> If we decide to g

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-13 Thread Daniel Vetter
On Tue, May 13, 2014 at 1:02 PM, Laurent Pinchart wrote: >> Also eventually I want to pull these tables directly out of source >> code comments - everything else tends to never get updated when the >> code changes. > > On the subject of moving documentation from docbook to source code, do your > k

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-13 Thread Laurent Pinchart
Hi Daniel, On Tuesday 13 May 2014 09:34:45 Daniel Vetter wrote: > On Tue, May 13, 2014 at 9:17 AM, Thierry Reding wrote: > > On Mon, May 12, 2014 at 10:03:55AM +0200, Daniel Vetter wrote: > >> On Mon, May 12, 2014 at 11:37:53AM +0530, Sagar Arun Kamble wrote: > >> > I support approach using docboo

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-13 Thread Thierry Reding
On Tue, May 13, 2014 at 09:34:45AM +0200, Daniel Vetter wrote: > On Tue, May 13, 2014 at 9:17 AM, Thierry Reding > wrote: > > On Mon, May 12, 2014 at 10:03:55AM +0200, Daniel Vetter wrote: > >> On Mon, May 12, 2014 at 11:37:53AM +0530, Sagar Arun Kamble wrote: > >> > I support approach using docbo

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-13 Thread Daniel Vetter
On Tue, May 13, 2014 at 9:17 AM, Thierry Reding wrote: > On Mon, May 12, 2014 at 10:03:55AM +0200, Daniel Vetter wrote: >> On Mon, May 12, 2014 at 11:37:53AM +0530, Sagar Arun Kamble wrote: >> > I support approach using docbook to start since there are not lot of >> > properties. Laurent has ack'e

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-13 Thread Thierry Reding
On Mon, May 12, 2014 at 10:03:55AM +0200, Daniel Vetter wrote: > On Mon, May 12, 2014 at 11:37:53AM +0530, Sagar Arun Kamble wrote: > > I support approach using docbook to start since there are not lot of > > properties. Laurent has ack'ed this one. Can we go ahead with this? > > http://lists.freed

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Dave Airlie
>> >> If we decide to go for property documentation inside the source code then I >> believe we'll have to create our own format, as creating a properties table >> from kerneldoc information extracted from comments is probably not possible. > > Can comeone pick up the ball here and figure out what

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Daniel Vetter
On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote: > On 05/12/2014 01:58 AM, Daniel Vetter wrote: > > On Mon, May 12, 2014 at 06:24:57PM +1000, Dave Airlie wrote: > > If we decide to go for property documentation inside the source code > then I > believe we'll have t

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Sagar Arun Kamble
I support approach using docbook to start since there are not lot of properties. Laurent has ack'ed this one. Can we go ahead with this? http://lists.freedesktop.org/archives/intel-gfx/2014-March/041527.html Adding description of new property is not very complex (assuming table format is understoo

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Randy Dunlap
On 05/12/2014 08:54 AM, Daniel Vetter wrote: > On Mon, May 12, 2014 at 08:23:45AM -0700, Randy Dunlap wrote: >> On 05/12/2014 01:58 AM, Daniel Vetter wrote: >>> On Mon, May 12, 2014 at 06:24:57PM +1000, Dave Airlie wrote: >> >> If we decide to go for property documentation inside the source

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Daniel Vetter
On Mon, May 12, 2014 at 06:24:57PM +1000, Dave Airlie wrote: > >> > >> If we decide to go for property documentation inside the source code then I > >> believe we'll have to create our own format, as creating a properties table > >> from kerneldoc information extracted from comments is probably not

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Daniel Vetter
On Mon, May 12, 2014 at 11:37:53AM +0530, Sagar Arun Kamble wrote: > I support approach using docbook to start since there are not lot of > properties. Laurent has ack'ed this one. Can we go ahead with this? > http://lists.freedesktop.org/archives/intel-gfx/2014-March/041527.html > > Adding descri

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-12 Thread Randy Dunlap
On 05/12/2014 01:58 AM, Daniel Vetter wrote: > On Mon, May 12, 2014 at 06:24:57PM +1000, Dave Airlie wrote: If we decide to go for property documentation inside the source code then I believe we'll have to create our own format, as creating a properties table from kerneldoc info

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-10 Thread Ville Syrjälä
On Wed, Mar 12, 2014 at 12:25:06PM +0100, Laurent Pinchart wrote: > Hi Sagar, > > On Wednesday 12 March 2014 16:46:05 Sagar Arun Kamble wrote: > > On Mon, 2014-03-10 at 15:36 +0100, Laurent Pinchart wrote: > > > On Monday 10 March 2014 06:21:49 Daniel Vetter wrote: > > > > On Wed, Mar 5, 2014 at 1

[PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers

2014-05-10 Thread Rob Clark
On Sat, May 10, 2014 at 6:39 AM, Ville Syrj?l? wrote: > On Wed, Mar 12, 2014 at 12:25:06PM +0100, Laurent Pinchart wrote: >> Hi Sagar, >> >> On Wednesday 12 March 2014 16:46:05 Sagar Arun Kamble wrote: >> > On Mon, 2014-03-10 at 15:36 +0100, Laurent Pinchart wrote: >> > > On Monday 10 March 2014 0