linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] DRM i.MX: Add parallel display support
Date: Thu, 21 Jun 2012 09:06:00 +0200	[thread overview]
Message-ID: <20120621070600.GY28394@pengutronix.de> (raw)
In-Reply-To: <20120621060730.GA23285@S2101-09.ap.freescale.net>

On Thu, Jun 21, 2012 at 02:07:32PM +0800, Shawn Guo wrote:
> On Thu, Jun 21, 2012 at 01:35:56PM +0800, Shawn Guo wrote:
> > On Thu, Jun 14, 2012 at 03:43:24PM +0200, Sascha Hauer wrote:
> > > +static const struct of_device_id imx_pd_dt_ids[] = {
> > > +	{ .compatible = "fsl,imx-parallel-display", .data = NULL, },
> > 
> > Can we use particular soc name to define the compatible string?
> 
> Just realized that it's actually not representing any hardware block.
> If that's the case, I feel we should try to get it away from device
> tree.

It actually represents a hardware block, or what else should a display
be? You are right in the way that it does not correspond to some
register block, but still it's hardware.
The information about the connected display must definitely live in the
devicetree, I can't think off any other place.

(We could argue that the displays should be subnodes of the IPU. I have
chosen not to do so because other display connections such as the LVDS
unit are outside of the IPU, but still need a display description.)

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2012-06-21  7:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 13:43 [PATCH, RFC] i.MX DRM support Sascha Hauer
2012-06-14 13:43 ` [PATCH 1/5] DRM: Add i.MX drm core support Sascha Hauer
2012-06-21  5:30   ` Shawn Guo
2012-06-21  6:52     ` Sascha Hauer
2012-06-14 13:43 ` [PATCH 2/5] DRM i.MX: Add parallel display support Sascha Hauer
2012-06-21  5:35   ` Shawn Guo
2012-06-21  6:07     ` Shawn Guo
2012-06-21  7:06       ` Sascha Hauer [this message]
2012-06-22  5:29   ` Shawn Guo
2012-06-14 13:43 ` [PATCH 3/5] DRM i.MX: Add LCDC support Sascha Hauer
2012-06-21  6:12   ` Shawn Guo
2012-06-21  7:10     ` Sascha Hauer
2012-06-14 13:43 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Sascha Hauer
2012-06-22  6:04   ` Shawn Guo
2012-06-14 13:43 ` [PATCH 5/5] DRM: Add i.MX IPUv3 crtc support Sascha Hauer
2012-06-19 18:20 ` [PATCH, RFC] i.MX DRM support Fabio Estevam
2012-07-02 10:05 ` Sascha Hauer
2012-07-02 11:12   ` Dirk Behme
2012-07-06 22:58   ` Greg Kroah-Hartman
2012-07-08  7:35     ` Dave Airlie
2012-07-09  8:42       ` Sascha Hauer

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=20120621070600.GY28394@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).