public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Cc: <linux-kernel@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
	<plagnioj@jcrosoft.com>
Subject: Re: [PATCH v5] video: add OpenCores VGA/LCD framebuffer driver
Date: Mon, 13 Jan 2014 12:43:58 +0200	[thread overview]
Message-ID: <52D3C36E.9020107@ti.com> (raw)
In-Reply-To: <20140113102006.GA30877@chokladfabriken.org>

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

On 2014-01-13 12:20, Stefan Kristiansson wrote:

> The VGA/LCD in the subject comes from the name of the core,
> the core itself presents a "vga-type" interface, but it can basically
> be hooked up to any type of display (with a bit of glue-logic in some cases).
> 
> That said - the reason why I went for the mode_options solution in the
> first place, is that when I initially wrote this driver
> (>2 years ago, time flies...) the display-timing device-tree bindings weren't
> invented yet, so it seemed like the most viable option without coming up
> with custom device-tree bindings.
> 
> It's completely possible that this design choice should be revised now,
> and I wouldn't mind converting this driver to make use of the display-timing
> dt properties if you think that's a good idea?

I don't have a strong opinion on this. It looks to me that even if the
current driver is merged, it would be easy to add device tree
display-timing later, and still keep full backward compatibility.

Then again, you already have DT support in the driver, and if it's clear
that the DT based videomode selection is better, then I'd just go
straight to that one without intermediate steps.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-01-13 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 20:13 [PATCH v5] video: add OpenCores VGA/LCD framebuffer driver Stefan Kristiansson
2014-01-13  1:24 ` Jingoo Han
2014-01-13  6:19   ` Stefan Kristiansson
2014-01-13  8:21 ` Tomi Valkeinen
2014-01-13 10:20   ` Stefan Kristiansson
2014-01-13 10:43     ` Tomi Valkeinen [this message]
2014-01-13 10:54       ` Geert Uytterhoeven
2014-01-13 11:15         ` Stefan Kristiansson
2014-02-21 13:54 ` Uwe Kleine-König

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=52D3C36E.9020107@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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