From: Sam Ravnborg <sam@ravnborg.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, eben@raspberrypi.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel@lists.freedesktop.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] drm/panel: panel-simple: Support panel-dpi
Date: Fri, 8 Mar 2019 14:01:48 +0100 [thread overview]
Message-ID: <20190308130148.GA21068@ravnborg.org> (raw)
In-Reply-To: <20190308094457.GA22655@ulmo>
> One thing that's not clear to me is whether or not we want to allow
> video timings to be specified in DT. I used to think that we didn't,
> because the video timings are implied by the specific compatible string
> (which we already determined is mandatory anyway),
We often have two users of the timings for a simple panel.
First we have the bootloader that may present something on the
panel - next step it then the kernel.
Bootloaders such as U-boot and barebox supports devicetree.
So with the timings specified in the devicetree there are three
users that can use the timings, and it is simple to share the
timing specifications.
As it is now one has to patch the kernel to add a panel to panel-simple,
and add timing to device tree to let barebox use it.
So it would be good once and for all to have the rules specified.
And the preferred solution is to have timing in the devicetree
so we can use it both in the kernel and in the bootloaders.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-08 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190307101030.3822-1-maxime.ripard@bootlin.com>
2019-03-08 9:44 ` [PATCH] drm/panel: panel-simple: Support panel-dpi 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 [this message]
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=20190308130148.GA21068@ravnborg.org \
--to=sam@ravnborg.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eben@raspberrypi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maxime.ripard@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--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 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).