From: Eric Anholt <eric@anholt.net>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: dri-devel@lists.freedesktop.org, tom.cooksey@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111
Date: Fri, 17 Mar 2017 17:45:34 -0700 [thread overview]
Message-ID: <87pohfv2dt.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170317230949.GK21222@n2100.armlinux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
Russell King - ARM Linux <linux@armlinux.org.uk> writes:
> On Fri, Mar 17, 2017 at 03:47:42PM -0700, Eric Anholt wrote:
>> This is a modesetting driver for the pl111 CLCD display controller
>> found on various ARM platforms such as the Versatile Express. The
>> driver has only been tested on the bcm911360_entphn platform so far,
>> with PRIME-based buffer sharing between vc4 and clcd.
>>
>> It reuses the existing devicetree binding, while not using quite as
>> many of its properties as the fbdev driver does (those are left for
>> future work).
>
> As we're multiplatform on ARM, and this is using the PL11x AMBA IDs,
> we must ensure that it's compatible with everything that the fbdev
> driver is compatible with... however, I suspect that's not worth the
> effort (unless Linus W wants it?)
>
> If we make it PL111 specific, then we don't need to handle Integrator
> CP, or the Versatile PB/AB weirdness. The only thing left is the
> power etc enable bits on Realview which uses the PL111. See the
> code for Realview in drivers/video/fbdev/amba-clcd-versatile.c.
Restricting to PL111 for now sounds good to me.
Those Realview bits look like they're turning on a power domain --
shouldn't we represent those as a regulator or a power domain? If we
did, then plugging that into a panel driver sounds straightforward.
(that's assuming that they're powering panel. not the controller -- I
can't quite tell from the code I've browsed so far)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-03-18 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 22:47 [PATCH 0/2] ARM CLCD DRM driver Eric Anholt
2017-03-17 22:47 ` [PATCH 1/2] video: ARM CLCD: Move registers to a separate header Eric Anholt
2017-03-17 22:47 ` [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111 Eric Anholt
2017-03-17 23:09 ` Russell King - ARM Linux
2017-03-18 0:45 ` Eric Anholt [this message]
2017-03-23 21:54 ` Linus Walleij
2017-03-23 23:31 ` Russell King - ARM Linux
2017-03-24 8:08 ` Linus Walleij
2017-03-20 8:34 ` Daniel Vetter
2017-03-20 18:23 ` Eric Anholt
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=87pohfv2dt.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tom.cooksey@arm.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
all inboxes | Powered by JetHome®