linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/2] video: ARM CLCD: Add DT support
Date: Thu, 06 Mar 2014 15:23:51 +0000	[thread overview]
Message-ID: <1394119431.4160.84.camel@hornet> (raw)
In-Reply-To: <53184C2E.3000807@ti.com>

On Thu, 2014-03-06 at 10:21 +0000, Tomi Valkeinen wrote:
> Is this an old HW, and presumably there won't be new users for it? If
> yes, this is probably fine. 

There is a DRM driver in the works, actually...

> If not, you might want to look at the video
> ports and endpoints, which is used by at least three not-yet-merged series:
> 
> [PATCHv3 00/41] OMAPDSS: DT support v3
> [PATCH v5 00/11] imx-drm dt bindings
> [RFC PATCH v2 00/21] Add DSI display support for Exynos based boards
> 
> Using bindings like that would be more future proof, even if the current
> driver doesn't use them.

... and this makes me try to get out of its way. In other words, I fully
agree with you, but I don't think this applies to this particular patch,
as I'm not even trying to represent the display pipeline. The (optional)
"display-timings" sub-node has been "borrowed" from other older drivers
and can be easily deprecated in the future, replaced by standard ones
(whatever final shape they will take :-). All other extra properties are
CLCD-specific and orthogonal.

Pawel


  reply	other threads:[~2014-03-06 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 16:23 [PATCH v5 1/2] video: ARM CLCD: Add DT support Pawel Moll
2014-03-05 16:23 ` [PATCH v5 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2014-03-06 10:21 ` [PATCH v5 1/2] video: ARM CLCD: Add DT support Tomi Valkeinen
2014-03-06 15:23   ` Pawel Moll [this message]
2014-03-07 11:35     ` Tomi Valkeinen
2014-03-10 12:09       ` Pawel Moll
2014-03-10 12:23         ` Tomi Valkeinen
2014-03-13 12:01           ` Russell King - ARM Linux
2014-03-13 13:12           ` Pawel Moll
2014-03-13  9:30   ` Linus Walleij
2014-03-13 11:43     ` Pawel Moll

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=1394119431.4160.84.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).