From: Tomi Valkeinen <tomi.valkeinen@ti.com> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>, Stephen Warren <swarren@wwwdotorg.org>, Steffen Trumtrar <s.trumtrar@pengutronix.de>, linux-fbdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org Subject: Re: [PATCH 1/2 v6] of: add helper to parse display timings Date: Mon, 08 Oct 2012 15:20:16 +0300 [thread overview] Message-ID: <1349698816.9437.5.camel@deskari> (raw) In-Reply-To: <1479122.2xVsV4MZ4o@avalon> [-- Attachment #1: Type: text/plain, Size: 2558 bytes --] On Mon, 2012-10-08 at 14:04 +0200, Laurent Pinchart wrote: > Hi Tomi, > > On Monday 08 October 2012 12:01:18 Tomi Valkeinen wrote: > > On Mon, 2012-10-08 at 10:25 +0200, Guennadi Liakhovetski wrote: > > > In general, I might be misunderstanding something, but don't we have to > > > distinguish between 2 types of information about display timings: (1) is > > > defined by the display controller requirements, is known to the display > > > driver and doesn't need to be present in timings DT. We did have some of > > > these parameters in board data previously, because we didn't have proper > > > display controller drivers... (2) is board specific configuration, and is > > > such it has to be present in DT. > > > > > > In that way, doesn't "interlaced" belong to type (1) and thus doesn't need > > > to be present in DT? > > > > As I see it, this DT data is about the display (most commonly LCD > > panel), i.e. what video mode(s) the panel supports. If things were done > > my way, the panel's supported timings would be defined in the driver for > > the panel, and DT would be left to describe board specific data, but > > this approach has its benefits. > > What about dumb DPI panels ? They will all be supported by a single driver, > would you have the driver contain information about all known DPI panels ? DT > seems a good solution to me in this case. Yes, I would have a table in the driver for all the devices it supports, which would describe the device specific parameters. But I don't have a problem with DT solution. Both methods have their pros and cons, and perhaps DT based solution is more practical. > For complex panels where the driver will support a single (or very few) model > I agree that specifying the timings in DT isn't needed. > > > Thus, if you connect an interlaced panel to your board, you need to tell > > the display controller that this panel requires interlace signal. Also, > > pixel clock source doesn't make sense in this context, as this doesn't > > describe the actual used configuration, but only what the panel > > supports. > > > > Of course, if this is about describing the hardware, the default-mode > > property doesn't really fit in... > > Maybe we should rename it to native-mode then ? Hmm, right, if it means native mode, then it is describing the hardware. But would it make sense to require that the native mode is the first mode in the list, then? This would make the separate default-mode/native-mode property not needed. Tomi [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>, Stephen Warren <swarren@wwwdotorg.org>, Steffen Trumtrar <s.trumtrar@pengutronix.de>, linux-fbdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org Subject: Re: [PATCH 1/2 v6] of: add helper to parse display timings Date: Mon, 08 Oct 2012 12:20:16 +0000 [thread overview] Message-ID: <1349698816.9437.5.camel@deskari> (raw) In-Reply-To: <1479122.2xVsV4MZ4o@avalon> [-- Attachment #1: Type: text/plain, Size: 2558 bytes --] On Mon, 2012-10-08 at 14:04 +0200, Laurent Pinchart wrote: > Hi Tomi, > > On Monday 08 October 2012 12:01:18 Tomi Valkeinen wrote: > > On Mon, 2012-10-08 at 10:25 +0200, Guennadi Liakhovetski wrote: > > > In general, I might be misunderstanding something, but don't we have to > > > distinguish between 2 types of information about display timings: (1) is > > > defined by the display controller requirements, is known to the display > > > driver and doesn't need to be present in timings DT. We did have some of > > > these parameters in board data previously, because we didn't have proper > > > display controller drivers... (2) is board specific configuration, and is > > > such it has to be present in DT. > > > > > > In that way, doesn't "interlaced" belong to type (1) and thus doesn't need > > > to be present in DT? > > > > As I see it, this DT data is about the display (most commonly LCD > > panel), i.e. what video mode(s) the panel supports. If things were done > > my way, the panel's supported timings would be defined in the driver for > > the panel, and DT would be left to describe board specific data, but > > this approach has its benefits. > > What about dumb DPI panels ? They will all be supported by a single driver, > would you have the driver contain information about all known DPI panels ? DT > seems a good solution to me in this case. Yes, I would have a table in the driver for all the devices it supports, which would describe the device specific parameters. But I don't have a problem with DT solution. Both methods have their pros and cons, and perhaps DT based solution is more practical. > For complex panels where the driver will support a single (or very few) model > I agree that specifying the timings in DT isn't needed. > > > Thus, if you connect an interlaced panel to your board, you need to tell > > the display controller that this panel requires interlace signal. Also, > > pixel clock source doesn't make sense in this context, as this doesn't > > describe the actual used configuration, but only what the panel > > supports. > > > > Of course, if this is about describing the hardware, the default-mode > > property doesn't really fit in... > > Maybe we should rename it to native-mode then ? Hmm, right, if it means native mode, then it is describing the hardware. But would it make sense to require that the native mode is the first mode in the list, then? This would make the separate default-mode/native-mode property not needed. Tomi [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-08 12:20 UTC|newest] Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-04 17:59 [PATCH 0/2 v6] of: add display helper Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 17:59 ` [PATCH 1/2 v6] of: add helper to parse display timings Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 18:47 ` Stephen Warren 2012-10-04 18:47 ` Stephen Warren [not found] ` <506DD9B4.40409-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 2012-10-05 16:16 ` Steffen Trumtrar 2012-10-05 16:16 ` Steffen Trumtrar 2012-10-05 16:16 ` Steffen Trumtrar 2012-10-05 16:21 ` Stephen Warren 2012-10-05 16:21 ` Stephen Warren 2012-10-05 16:38 ` Steffen Trumtrar 2012-10-05 16:38 ` Steffen Trumtrar 2012-10-07 13:38 ` Laurent Pinchart 2012-10-07 13:38 ` Laurent Pinchart 2012-10-08 7:34 ` Steffen Trumtrar 2012-10-08 7:34 ` Steffen Trumtrar [not found] ` <1349373560-11128-2-git-send-email-s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2012-10-04 21:35 ` Guennadi Liakhovetski 2012-10-04 21:35 ` Guennadi Liakhovetski 2012-10-04 21:35 ` Guennadi Liakhovetski 2012-10-05 7:17 ` Robert Schwebel 2012-10-05 7:17 ` Robert Schwebel 2012-10-05 16:17 ` Stephen Warren 2012-10-05 16:17 ` Stephen Warren 2012-10-08 8:25 ` Guennadi Liakhovetski 2012-10-08 8:25 ` Guennadi Liakhovetski 2012-10-08 9:01 ` Tomi Valkeinen 2012-10-08 9:01 ` Tomi Valkeinen 2012-10-08 12:04 ` Laurent Pinchart 2012-10-08 12:04 ` Laurent Pinchart 2012-10-08 12:20 ` Tomi Valkeinen [this message] 2012-10-08 12:20 ` Tomi Valkeinen 2012-10-08 16:12 ` Stephen Warren 2012-10-08 16:12 ` Stephen Warren 2012-10-08 16:12 ` Stephen Warren 2012-10-08 16:34 ` Mitch Bradley 2012-10-08 16:34 ` Mitch Bradley 2012-10-08 16:34 ` Mitch Bradley 2012-10-08 16:10 ` Stephen Warren 2012-10-08 16:10 ` Stephen Warren 2012-10-08 17:33 ` Laurent Pinchart 2012-10-08 17:33 ` Laurent Pinchart [not found] ` <Pine.LNX.4.64.1210042307300.3744-0199iw4Nj15frtckUFj5Ag@public.gmane.org> 2012-10-05 16:28 ` Steffen Trumtrar 2012-10-05 16:28 ` Steffen Trumtrar 2012-10-05 16:28 ` Steffen Trumtrar 2012-10-08 7:07 ` Tomi Valkeinen 2012-10-08 7:07 ` Tomi Valkeinen 2012-10-08 7:12 ` Tomi Valkeinen 2012-10-08 7:12 ` Tomi Valkeinen 2012-10-08 7:49 ` Steffen Trumtrar 2012-10-08 7:49 ` Steffen Trumtrar [not found] ` <20121008074921.GB20800-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2012-10-11 19:31 ` Thierry Reding 2012-10-11 19:31 ` Thierry Reding 2012-10-11 19:31 ` Thierry Reding 2012-10-12 7:21 ` Steffen Trumtrar 2012-10-12 7:21 ` Steffen Trumtrar 2012-10-20 10:58 ` Thierry Reding 2012-10-20 10:58 ` Thierry Reding 2012-10-20 19:59 ` Thierry Reding 2012-10-20 19:59 ` Thierry Reding 2012-10-22 7:40 ` Steffen Trumtrar 2012-10-22 7:40 ` Steffen Trumtrar 2012-10-04 17:59 ` [PATCH 2/2 v6] of: add generic videomode description Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 17:59 ` Steffen Trumtrar 2012-10-04 18:51 ` Stephen Warren 2012-10-04 18:51 ` Stephen Warren 2012-10-05 15:51 ` Steffen Trumtrar 2012-10-05 15:51 ` Steffen Trumtrar 2012-10-07 13:38 ` Laurent Pinchart 2012-10-07 13:38 ` Laurent Pinchart 2012-10-20 10:45 ` Thierry Reding 2012-10-20 10:45 ` Thierry Reding 2012-10-08 7:21 ` Tomi Valkeinen 2012-10-08 7:21 ` Tomi Valkeinen 2012-10-08 7:57 ` Steffen Trumtrar 2012-10-08 7:57 ` Steffen Trumtrar 2012-10-08 12:19 ` Laurent Pinchart 2012-10-08 12:19 ` Laurent Pinchart 2012-10-08 12:13 ` Laurent Pinchart 2012-10-08 12:13 ` Laurent Pinchart 2012-10-08 12:48 ` Steffen Trumtrar 2012-10-08 12:48 ` Steffen Trumtrar 2012-10-08 20:52 ` Laurent Pinchart 2012-10-08 20:52 ` Laurent Pinchart 2012-10-09 7:26 ` Steffen Trumtrar 2012-10-09 7:26 ` Steffen Trumtrar [not found] ` <20121009072608.GA2519-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2012-10-20 10:54 ` Thierry Reding 2012-10-20 10:54 ` Thierry Reding 2012-10-20 10:54 ` Thierry Reding 2012-10-20 11:04 ` Thierry Reding 2012-10-20 11:04 ` Thierry Reding 2012-10-22 7:35 ` Steffen Trumtrar 2012-10-22 7:35 ` Steffen Trumtrar [not found] ` <1349373560-11128-1-git-send-email-s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2012-10-15 10:54 ` [PATCH 0/2 v6] of: add display helper Leela Krishna Amudala 2012-10-15 10:55 ` Leela Krishna Amudala 2012-10-15 10:54 ` Leela Krishna Amudala 2012-10-15 14:17 ` Steffen Trumtrar 2012-10-15 14:17 ` Steffen Trumtrar 2012-10-20 11:35 ` Thierry Reding 2012-10-20 11:35 ` Thierry Reding
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1349698816.9437.5.camel@deskari \ --to=tomi.valkeinen@ti.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=g.liakhovetski@gmx.de \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=s.trumtrar@pengutronix.de \ --cc=swarren@wwwdotorg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.