From: Linus Walleij <linus.walleij@linaro.org>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Liviu Dudau <Liviu.Dudau@arm.com>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Fabian Vogt <fabian@ritter-vogt.de>,
Daniel Tang <dt.tangr@gmail.com>, Sam Ravnborg <sam@ravnborg.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] RFT: PL111 DRM conversion of nspire
Date: Wed, 24 Jul 2019 14:53:48 +0200 [thread overview]
Message-ID: <CACRpkdYYcco-4+vOfNFTVvJ5Yb6t5HNdBZjT8T87J7G9egV=4Q@mail.gmail.com> (raw)
In-Reply-To: <4d576e9cc749fc47b57f9bc64a082aa791e9780c.camel@arm.com>
On Wed, Jul 24, 2019 at 2:47 PM Pawel Moll <pawel.moll@arm.com> wrote:
> On Wed, 2019-07-24 at 13:28 +0100, Linus Walleij wrote:
> > On Tue, Jul 23, 2019 at 8:10 PM Sam Ravnborg <sam@ravnborg.org> wrote:
> > > On Tue, Jul 23, 2019 at 03:37:52PM +0200, Linus Walleij wrote:
> > > Do we need to support arm,pl11x,tft-r0g0b0-pads before
> > > we can obsolete fbdev stuff?
> >
> > No I don't think so, the only in-tree platform that was using it was
> > the Nomadik and all it did was to switch RGB to BGR and
> > I already handle that in the driver using the hardware
> > feature to switch RGB and BGR around instead.
> >
> > Right now I just check that the pads are there, I might just
> > remove the check.
> >
> > However Pawel added this binding and might be able to tell
> > something about if there are platforms out there that really
> > needs this. Possibly Liviu knows more.
>
> It was only there so the fbdev driver could figure out the output mode.
> I take that DRM "pipeline" now takes care of it, so I'd say that the
> moment the fbdev driver dies, the binding can go along :-)
OK I'll get rid of it. :)
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-24 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 13:37 [PATCH 0/3] RFT: PL111 DRM conversion of nspire Linus Walleij
2019-07-23 13:37 ` [PATCH 1/3] RFT: drm/pl111: Support grayscale Linus Walleij
2019-07-23 15:19 ` Fabian Vogt
2019-07-24 12:33 ` Linus Walleij
2019-07-25 19:26 ` Fabian Vogt
2019-08-03 9:51 ` Linus Walleij
2019-08-04 20:13 ` Fabian Vogt
2019-07-23 16:22 ` [1/3] " David Lechner
2019-07-23 17:25 ` [PATCH 1/3] " Adam Jackson
2019-07-23 21:06 ` Daniel Vetter
2019-07-24 12:52 ` Linus Walleij
2019-07-24 14:06 ` Daniel Vetter
2019-07-23 13:37 ` [PATCH 2/3] RTF: drm/panel: simple: Add TI nspire panels Linus Walleij
2019-07-23 17:54 ` Sam Ravnborg
2019-07-24 13:58 ` Linus Walleij
2019-07-24 18:53 ` Sam Ravnborg
2019-07-23 13:37 ` [PATCH 3/3] RFT: ARM: nspire: Move CLCD set-up to device tree Linus Walleij
2019-07-23 18:10 ` [PATCH 0/3] RFT: PL111 DRM conversion of nspire Sam Ravnborg
2019-07-24 12:28 ` Linus Walleij
2019-07-24 12:47 ` Pawel Moll
2019-07-24 12:53 ` Linus Walleij [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='CACRpkdYYcco-4+vOfNFTVvJ5Yb6t5HNdBZjT8T87J7G9egV=4Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dt.tangr@gmail.com \
--cc=fabian@ritter-vogt.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pawel.moll@arm.com \
--cc=sam@ravnborg.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).