From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] video: ARM CLCD: add support of an optional GPIO to enable panel
Date: Mon, 02 Jan 2017 14:22:28 +0000 [thread overview]
Message-ID: <20170102142228.GI14217@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkdZE6VgJA27+Wh=Gxd7yOXpLMyT7yCB2PYA36y0gvosHFQ@mail.gmail.com>
On Fri, Dec 30, 2016 at 09:23:59AM +0100, Linus Walleij wrote:
> On Wed, Dec 21, 2016 at 4:27 AM, Vladimir Zapolskiy <vz@mleia.com> wrote:
>
> > The changeset contains a number of cleanups, changed semantics of
> > init_panel() callback, which allows to simplify getting of panel
> > properties from panel device tree node, and a handling of optional
> > "enable-gpios" panel property, the latter is described in
> > display/panel/panel-dpi.txt device tree binding documentation, but
> > it has been unsupported by the ARM CLCD driver.
> >
> > Vladimir Zapolskiy (4):
> > video: ARM CLCD: sort included headers out alphabetically
> > video: ARM CLCD: use panel device node for panel initialization
> > video: ARM CLCD: use panel device node for getting backlight and mode
> > video: ARM CLCD: add support of an optional GPIO to enable panel
>
> As you may have seen Tomi has stepped down as FBDEV maintainer and
> this subsystem is now orphaned.
>
> I guess Andrew Morton merges patches for it in this case, he usually does.
>
> But what we should actually do is create a new DRM driver for CLCD
> in drivers/gpu/drm/arm/clcd*
>
> It's maybe not a small undertaking :(
>
> But in case you're interested in the job, I will pitch in and test the result
> on all ARM reference designs plus Nomadik.
A DRM driver for it would probably be a good idea, but dealing with all
the weird and wonderful connection arrangements may not be that easy...
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-01-02 14:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 3:27 [PATCH 0/4] video: ARM CLCD: add support of an optional GPIO to enable panel Vladimir Zapolskiy
2016-12-21 3:27 ` [PATCH 1/4] video: ARM CLCD: sort included headers out alphabetically Vladimir Zapolskiy
2016-12-21 3:27 ` [PATCH 2/4] video: ARM CLCD: use panel device node for panel initialization Vladimir Zapolskiy
2016-12-21 3:27 ` [PATCH 3/4] video: ARM CLCD: use panel device node for getting backlight and mode Vladimir Zapolskiy
2016-12-21 3:27 ` [PATCH 4/4] video: ARM CLCD: add support of an optional GPIO to enable panel Vladimir Zapolskiy
2016-12-30 8:20 ` Linus Walleij
2016-12-30 9:24 ` Vladimir Zapolskiy
2016-12-30 8:23 ` [PATCH 0/4] " Linus Walleij
2017-01-01 20:50 ` Vladimir Zapolskiy
2017-01-02 14:22 ` Russell King - ARM Linux [this message]
2017-01-07 23:32 ` Vladimir Zapolskiy
2017-01-10 4:06 ` Vladimir Zapolskiy
2017-01-10 13:47 ` Vladimir Murzin
2017-01-11 15:16 ` Linus Walleij
2017-01-12 0:05 ` Vladimir Zapolskiy
2017-01-12 8:27 ` Linus Walleij
2017-01-12 21:26 ` Vladimir Zapolskiy
2017-01-13 11:08 ` Bartlomiej Zolnierkiewicz
2017-01-17 1:57 ` Vladimir Zapolskiy
2017-01-18 12:22 ` Linus Walleij
[not found] ` <CGME20170130152340epcas5p3f68349ef89c5ec902186ae71011c0c4b@epcas5p3.samsung.com>
2017-01-30 15:23 ` Bartlomiej Zolnierkiewicz
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=20170102142228.GI14217@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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).