From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Philippe Cornu <philippe.cornu@st.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Yannick Fertre <yannick.fertre@st.com>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [RFC 1/1] drm: allow to use mmuless SoC
Date: Wed, 30 Nov 2016 17:36:46 +0200 [thread overview]
Message-ID: <2627720.fAh4h1brPx@avalon> (raw)
In-Reply-To: <CA+M3ks6VAbyi-qeMJLCdrwNJfAAJHu1QrhkJ-NqJTPvzY-486w@mail.gmail.com>
Hi Benjamin,
On Wednesday 30 Nov 2016 16:34:37 Benjamin Gaignard wrote:
> 2016-11-30 16:19 GMT+01:00 Laurent Pinchart:
> > On Wednesday 30 Nov 2016 16:08:23 Benjamin Gaignard wrote:
> >> 2016-11-30 14:52 GMT+01:00 Daniel Vetter <daniel@ffwll.ch>:
> >>> On Wed, Nov 30, 2016 at 12:21:24PM +0100, Benjamin Gaignard wrote:
> >>>> Some platforms without MMU have display drivers where a drm/kms driver
> >>>> could be implemented.
> >>>> Before doing such kind of thing drm/kms must allow to use mmuless
> >>>> devices.
> >>>> This patch proposes to remove MMU configuration flag and add some
> >>>> cma helpers functions to help implementing mmuless display driver
> >>>>
> >>>> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
> >>>> ---
> >>>>
> >>>> drivers/gpu/drm/Kconfig | 4 +--
> >>>> drivers/gpu/drm/drm_fb_cma_helper.c | 20 ++++++++++++
> >>>> drivers/gpu/drm/drm_gem_cma_helper.c | 62 +++++++++++++++++++++++++++
> >
> > [snip]
> >
> >>> drm_vm.c is a legacy horror show. Instead of hacking even more garbage
> >>> into this, can't we just not compile this for MMU-less platforms? A
> >>> bunch of stubs in drm_internal.h is all that should be needed for this,
> >>> since on MMU-less you should never be able to enable one of the legacy
> >>> drivers which need the exported symbols from this file.
> >>
> >> Following your advice I have removed drm_vm.c from the build if
> >> CONFIG_MMU is not set
> >
> > How about only including it if !DRM_LEGACY && !DRM_NOUVEAU ?
>
> I don't understand the link between !DRM_LEGACY && !DRM_NOUVEAU and MMU...
>
> By chance would you mean including only if DRM_LEGACY && DRM_NOUVEAU ?
I meant excluding it if !DRM_LEGACY && !DRM_NOUVEAU, sorry, so including it if
DRM_LEGACY || DRM_NOUVEAU.
(Probably out of scope for this patch series, but why do we need it in nouveau
?)
> >> I only had to stub drm_legacy_vma_flush() to compile.
> >> I will include that in v3
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-30 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 11:21 [RFC 0/1] DRM: allow to use mmuless devices Benjamin Gaignard
2016-11-30 11:21 ` [RFC 1/1] drm: allow to use mmuless SoC Benjamin Gaignard
2016-11-30 11:35 ` Laurent Pinchart
2016-11-30 12:35 ` Benjamin Gaignard
2016-11-30 13:52 ` Daniel Vetter
2016-11-30 15:08 ` Benjamin Gaignard
2016-11-30 15:19 ` Laurent Pinchart
2016-11-30 15:34 ` Benjamin Gaignard
2016-11-30 15:36 ` Laurent Pinchart [this message]
2016-11-30 15:56 ` Daniel Vetter
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=2627720.fAh4h1brPx@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@redhat.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=philippe.cornu@st.com \
--cc=yannick.fertre@st.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 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.