All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PULL] SH Mobile DRM driver for v3.7
Date: Sun, 16 Sep 2012 17:38:41 +0200	[thread overview]
Message-ID: <1379357.9O94Nb1bxd@avalon> (raw)
In-Reply-To: <50547D45.4010309@metafoo.de>

On Saturday 15 September 2012 15:06:13 Lars-Peter Clausen wrote:
> On 09/15/2012 01:28 AM, Dave Airlie wrote:
> > On Fri, Sep 14, 2012 at 10:38 PM, Laurent Pinchart wrote:
> >> Hi Dave,
> >> 
> >> The SH Mobile DRM driver is now (in my opinion) ready for mainline. It
> >> requires GEM and KMS/FB helpers that have been reviewed on the list and
> >> tested. Sascha is waiting for them to reach your tree to send a pull
> >> request for another new driver.
> > 
> > Just a quick review before I pull,
> > 
> > Why does include/drm/shmob_drm.h exist? this file is meant to define
> > the userspace API to the driver, if you don't have any userspace API
> > or driver specific ioctls, this file shouldn't be required. You might
> > want to create include/drm/shmob_internal.h maybe, if this is used as
> > an interface to other places in the kernel. I probably need to check
> > other have been doing the right thing here as well. (driver_drm.h
> > should be user facing only)
> > 
> > Uggh drm_fb_cma_helper.c is pure midlayer mistake, are you 100% sure
> > no driver is ever going to want to tweak the drm_fbdev_cma_ops?
> 
> Obviously we can't, for the same reasons we can't know whether there will
> ever be a driver which needs to use custom fb_ops. It works fine as it is
> now for three different drivers. And other drivers making use of the cma
> buffer helpers are likely to have similar requirements, but if we ever get
> to a point where a driver needs custom fb_ops it is fairly easy to change
> it then.

Dave, are you fine with that ? If so I'll submit a new pull request with 
include/drm/shmob_drm.h moved to include/linux/platform_data/shmob_drm.h.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2012-09-16 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 12:38 [PULL] SH Mobile DRM driver for v3.7 Laurent Pinchart
2012-09-14 12:47 ` Alan Cox
2012-09-14 13:05   ` Laurent Pinchart
2012-09-14 22:57     ` Alan Cox
2012-09-14 23:15       ` Laurent Pinchart
2012-09-14 23:28 ` Dave Airlie
2012-09-14 23:36   ` Laurent Pinchart
2012-09-15 13:06   ` Lars-Peter Clausen
2012-09-16 15:38     ` Laurent Pinchart [this message]
2012-09-17  3:33       ` Dave Airlie
2012-09-18 10:31         ` [PULL v2] " Laurent Pinchart

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=1379357.9O94Nb1bxd@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lars@metafoo.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.