From mboxrd@z Thu Jan 1 00:00:00 1970 From: daniel@ffwll.ch (Daniel Vetter) Date: Tue, 11 Jun 2013 00:01:59 +0200 Subject: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver In-Reply-To: References: <20130609190612.GM18614@n2100.arm.linux.org.uk> <20130610170648.GX18614@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Jun 10, 2013 at 9:59 PM, Rob Clark wrote: > On Mon, Jun 10, 2013 at 1:06 PM, Russell King - ARM Linux > wrote: >> On Mon, Jun 10, 2013 at 11:57:32AM -0400, Rob Clark wrote: >>> On Sun, Jun 9, 2013 at 3:29 PM, Russell King >>> wrote: >>> > This patch adds support for the pair of LCD controllers on the Marvell >>> > Armada 510 SoCs. This driver supports: >>> > - multiple contiguous scanout buffers for video and graphics >>> > - shm backed cacheable buffer objects for X pixmaps for Vivante GPU >>> > acceleration >>> > - dual lcd0 and lcd1 crt operation >>> > - video overlay on each LCD crt >>> >>> Any particular reason for not exposing the overlays as drm_plane's? >>> That is probably something that should change before merging the >>> driver. >> >> Only through not understanding much of DRM when I started this. >> Provided DRM planes can do everything that I'm already doing with >> the overlay support, then yes. Otherwise, I want to stick with this >> which is modelled after the i915 overlay interface. Oh i915 overlays aren't a good reason ;-) I've done those way back when drm didn't have any plane infrastructure and pretty much as my very contribution. So totally lacked any clue. If I can scrap together a bit of time I want to port the legacy overlay code over to drm planes (and remap the current ioctl interface to the drm plane interface for backwards compat). But atm that's crushed under a giant pile of other todo items. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver Date: Tue, 11 Jun 2013 00:01:59 +0200 Message-ID: References: <20130609190612.GM18614@n2100.arm.linux.org.uk> <20130610170648.GX18614@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) by gabe.freedesktop.org (Postfix) with ESMTP id E42FAE5F61 for ; Mon, 10 Jun 2013 15:01:59 -0700 (PDT) Received: by mail-ie0-f177.google.com with SMTP id aq17so284000iec.36 for ; Mon, 10 Jun 2013 15:01:59 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Rob Clark Cc: "linux-arm-kernel@lists.infradead.org" , Russell King - ARM Linux , Jason Cooper , dri-devel , Sebastian Hesselbarth List-Id: dri-devel@lists.freedesktop.org On Mon, Jun 10, 2013 at 9:59 PM, Rob Clark wrote: > On Mon, Jun 10, 2013 at 1:06 PM, Russell King - ARM Linux > wrote: >> On Mon, Jun 10, 2013 at 11:57:32AM -0400, Rob Clark wrote: >>> On Sun, Jun 9, 2013 at 3:29 PM, Russell King >>> wrote: >>> > This patch adds support for the pair of LCD controllers on the Marvell >>> > Armada 510 SoCs. This driver supports: >>> > - multiple contiguous scanout buffers for video and graphics >>> > - shm backed cacheable buffer objects for X pixmaps for Vivante GPU >>> > acceleration >>> > - dual lcd0 and lcd1 crt operation >>> > - video overlay on each LCD crt >>> >>> Any particular reason for not exposing the overlays as drm_plane's? >>> That is probably something that should change before merging the >>> driver. >> >> Only through not understanding much of DRM when I started this. >> Provided DRM planes can do everything that I'm already doing with >> the overlay support, then yes. Otherwise, I want to stick with this >> which is modelled after the i915 overlay interface. Oh i915 overlays aren't a good reason ;-) I've done those way back when drm didn't have any plane infrastructure and pretty much as my very contribution. So totally lacked any clue. If I can scrap together a bit of time I want to port the legacy overlay code over to drm planes (and remap the current ioctl interface to the drm plane interface for backwards compat). But atm that's crushed under a giant pile of other todo items. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch