mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v6] omap4-fb: add driver
Date: Tue, 18 Jun 2013 10:09:55 +0200	[thread overview]
Message-ID: <1371542995.4055.12.camel@mars> (raw)
In-Reply-To: <51C00F29.1060601@ti.com>

Hi Tomi

On Tue, 2013-06-18 at 10:41 +0300, Tomi Valkeinen wrote:
> On 17/06/13 19:18, Christoph Fritz wrote:
> > This patch adds omap4 display controller support.
> 
> I haven't been following the discussions about this patch, so maybe
> these have been covered:
> 
> OMAP2/3/4/5 all have very similar DSS. Why did you go for omap_4_-fb
> driver, not omap-fb driver?

I'm currently only having an omap4 board here. But I could rename the
driver to the more generic name "omap-fb" and explain in the KCONFIG
that it currently only covers omap4 devices.

So we could go from there up to all other OMAP devices. Okay?

> > +config DRIVER_VIDEO_OMAP4
> > +	bool "OMAP4 framebuffer driver"
> > +	depends on ARCH_OMAP4
> > +	help
> > +	  Add support for the OMAP4 Display Controller.
> > +	  DSI is unsupported, only DISPC parallel mode on LCD2
> > +	  is supported.
> > +
> 
> Also HDMI, RFBI and VENC seem to be unsupported. The DISPC parallel mode
> you mention is MIPI DPI.
> 
> Supporting only the DPI output is "easy", do you have plans to support
> the other outputs and external encoders used in many boards?

No, at present I have no intention to do so.

>  That may
> require a more generic approach, with multiple display "entities" in the
> pipeline. Not that the first version should support that, but I just
> wanted to mention it so that you don't design the driver in too
> non-generic manner.

 Thanks
  -- Christoph



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-06-18  8:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  6:42 [PATCH] " Christoph Fritz
2013-04-05  8:59 ` Sascha Hauer
2013-04-07 22:15   ` [PATCH v2] " Christoph Fritz
2013-04-08  7:17     ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-09  7:16       ` Sascha Hauer
2013-04-09 13:29         ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 19:01           ` Christoph Fritz
2013-06-02 21:07             ` Christoph Fritz
2013-06-12 20:45               ` [PATCH v3] " Christoph Fritz
2013-06-13 10:10                 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-13 22:40                   ` [PATCH v4] " Christoph Fritz
2013-06-14  6:29                     ` Alexander Aring
2013-06-14  7:23                       ` Jan Weitzel
2013-06-14  8:15                         ` [PATCH v5] " Christoph Fritz
2013-06-14 11:43                           ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-14 15:11                             ` [PATCH v6] " Christoph Fritz
2013-06-17  7:36                               ` Sascha Hauer
2013-06-17 16:17                                 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-18  8:47                                 ` [PATCH v7] " Christoph Fritz
2013-06-17 18:45                               ` [PATCH v6] " Alexander Aring
2013-06-17 16:18                             ` Christoph Fritz
2013-06-18  7:41                               ` Tomi Valkeinen
2013-06-18  8:09                                 ` Christoph Fritz [this message]
2013-06-18  9:59                                   ` Tomi Valkeinen

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=1371542995.4055.12.camel@mars \
    --to=chf.fritz@googlemail.com \
    --cc=barebox@lists.infradead.org \
    --cc=tomi.valkeinen@ti.com \
    /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