All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Maxime Ripard <maxime.ripard@bootlin.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Sean Paul <seanpaul@chromium.org>Maxime Ripard
	<maxime.ripard@bootlin.com>
Cc: eben@raspberrypi.org, dri-devel@lists.freedesktop.org,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] drm/panel: panel-simple: Support panel-dpi
Date: Thu, 07 Mar 2019 10:12:47 -0800	[thread overview]
Message-ID: <87pnr2tuxs.fsf@anholt.net> (raw)
In-Reply-To: <20190307101030.3822-1-maxime.ripard@bootlin.com>


[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]

Maxime Ripard <maxime.ripard@bootlin.com> writes:

> The kernel has a device tree binding for panel-dpi which allows for the
> panel timings to be described in the device-tree, however it wasn't
> supported so far except in a (small) number of KMS drivers that had an
> ad-hoc solution for this (omapdrm for example).

I'm really in favor of this idea.  panel-simple.c is a clear testament
to how much could have been done with a small amount of DT describing
the hardware.

Hoever I don't see how panel-dpi provides the bus flags or bus format,
so I don't think this is quite enough.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-03-07 18:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 10:10 [PATCH] drm/panel: panel-simple: Support panel-dpi Maxime Ripard
2019-03-07 18:12 ` Eric Anholt [this message]
2019-03-08  9:44 ` Thierry Reding
2019-03-08 11:14   ` Laurent Pinchart
2019-03-08 14:11     ` Thierry Reding
2019-03-11  9:56       ` Maxime Ripard
2019-03-08 13:01   ` Sam Ravnborg
2019-03-08 13:39     ` Thierry Reding
2019-03-08 17:12       ` Sam Ravnborg
2019-03-08 20:11         ` Rob Herring
2019-03-08 19:59   ` Rob Herring
2019-03-08 23:05     ` Eric Anholt
2019-03-09  0:21       ` Rob Herring

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=87pnr2tuxs.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eben@raspberrypi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=seanpaul@chromium.org \
    --cc=thierry.reding@gmail.com \
    --cc=thomas.petazzoni@bootlin.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 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.