From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: dri-devel@lists.freedesktop.org, airlied@redhat.com,
daniel@ffwll.ch, robdclark@gmail.com,
laurent.pinchart@ideasonboard.com
Cc: yannick.fertre@st.com, linaro-kernel@lists.linaro.org,
philippe.cornu@st.com
Subject: [RFC 0/1] DRM: allow to use mmuless devices
Date: Wed, 30 Nov 2016 12:21:23 +0100 [thread overview]
Message-ID: <1480504884-22638-1-git-send-email-benjamin.gaignard@linaro.org> (raw)
Hello,
The purpose of this RFC is to understand what is needed to allow to
write drm/kms drivers for devices without MMU.
There are some MCU platforms, like stm32f4, which don't have MMU
but have hardware display IP where is it possible to implement a
drm/kms driver.
Obviously that start by removing MMU configuration flag from Kconfig.
But while coding the driver for stm32f4 (on discovery board to have enough memory)
we have already identify few other pieces of code that need to be change.
We have been inspired by what already exist in v4l2 where using mmuless devices
is possible.
Since we have only use cma helpers we only have partial view of what could be
needed for other part of drm/kms framework.
Benjamin Gaignard (1):
drm: allow to use mmuless SoC
drivers/gpu/drm/Kconfig | 4 +--
drivers/gpu/drm/drm_fb_cma_helper.c | 20 ++++++++++++
drivers/gpu/drm/drm_gem_cma_helper.c | 62 ++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/drm_vm.c | 4 +++
drivers/video/fbdev/core/fbmem.c | 8 +++++
include/drm/drm_gem_cma_helper.h | 6 ++++
6 files changed, 102 insertions(+), 2 deletions(-)
--
1.9.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-30 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 11:21 Benjamin Gaignard [this message]
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
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=1480504884-22638-1-git-send-email-benjamin.gaignard@linaro.org \
--to=benjamin.gaignard@linaro.org \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=philippe.cornu@st.com \
--cc=robdclark@gmail.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 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).