From: Thierry Reding <thierry.reding@gmail.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Riccardo Bortolato <bortolato@navaltechitalia.it>,
David Airlie <airlied@linux.ie>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Daniel Vetter <daniel@ffwll.ch>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] drm/panel: simple: Add support for Innolux AT070TN92
Date: Sat, 23 Apr 2016 00:30:49 +0200 [thread overview]
Message-ID: <20160422223047.GA22161@mithrandir.ba.sec> (raw)
In-Reply-To: <877ffrp3fc.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Thu, Apr 21, 2016 at 02:11:19PM +0200, Holger Schurig wrote:
> Thierry Reding <thierry.reding@gmail.com> writes:
> > Applied, thanks.
>
> I once read that this is the recommended way to go, instead of
> specifying the timings in the device tree. Why is this so? Any new
> display just increases the .text size of the kernel unnessary.
It's actually only the .rodata section that's increased every time we
add a new display panel.
> Did this idea stem from the era where bootloaders like Barebox couldn't
> modify the DT ad-hoc before handing it over to the kernel?
No, not really. But since this has come up every now and again I finally
wrote down my recollection and thoughts on the matter, hopefully that
will be satisfactory as an answer:
http://sietch-tagr.blogspot.com/2016/04/display-panels-are-not-special.html
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-22 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:37 [PATCH v2] drm/panel: simple: Add support for Innolux AT070TN92 Boris Brezillon
2016-04-20 13:40 ` Thierry Reding
2016-04-21 12:11 ` Holger Schurig
2016-04-22 22:30 ` Thierry Reding [this message]
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=20160422223047.GA22161@mithrandir.ba.sec \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=bortolato@navaltechitalia.it \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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).