From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: rodrigosiqueiramelo@gmail.com, hamoahmmed.sa@gmail.com
Subject: [RFC 0/3] Add infrastructure for CRC support
Date: Thu, 28 Jun 2018 00:21:24 +0300 [thread overview]
Message-ID: <cover.1530133610.git.hamohammed.sa@gmail.com> (raw)
This patchset add the necessary infrastructure required to enable to
compute and add CRCs entries.
1. add functions to map buffers to kernel address space.
2. map/unmap buffers in the prepare/cleanup_fb hooks.
3. compute crc using crc32 on the visible portion of the buffer.
Note:
This patchset was built on top of the following patch:
subject: "drm/vkms: Add vblank events simulated by hrtimers"
link: https://lists.freedesktop.org/archives/dri-devel/2018-June/181060.html
Haneen Mohammed (3):
drm/vkms: Add functions to map GEM backing storage
drm/vkms: map/unmap buffers in [prepare/cleanup]_fb hooks
drm/vkms: Implement CRC debugfs API
drivers/gpu/drm/vkms/vkms_crtc.c | 76 +++++++++++++++++++++++++++++++
drivers/gpu/drm/vkms/vkms_drv.c | 1 +
drivers/gpu/drm/vkms/vkms_drv.h | 22 +++++++++
drivers/gpu/drm/vkms/vkms_gem.c | 50 ++++++++++++++++++++
drivers/gpu/drm/vkms/vkms_plane.c | 50 ++++++++++++++++++++
5 files changed, 199 insertions(+)
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-06-27 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 21:21 Haneen Mohammed [this message]
2018-06-27 21:22 ` [RFC 1/3] drm/vkms: Add functions to map GEM backing storage Haneen Mohammed
2018-06-27 21:23 ` [RFC 2/3] drm/vkms: map/unmap buffers in [prepare/cleanup]_fb hooks Haneen Mohammed
2018-06-27 21:24 ` [RFC 3/3] drm/vkms: Implement CRC debugfs API Haneen Mohammed
2018-06-28 8:07 ` Daniel Vetter
2018-06-28 8:08 ` Daniel Vetter
2018-06-28 11:40 ` Daniel Vetter
2018-06-28 11:56 ` Haneen Mohammed
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=cover.1530133610.git.hamohammed.sa@gmail.com \
--to=hamohammed.sa@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamoahmmed.sa@gmail.com \
--cc=rodrigosiqueiramelo@gmail.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.