From: Ginny Chen <ginny.chen@mediatek.com>
To: dri-devel@lists.freedesktop.org
Cc: christie.yu@mediatek.com
Subject: DRM: how to support live source
Date: Wed, 21 Sep 2016 15:18:29 +0800 [thread overview]
Message-ID: <1474442309.4646.41.camel@mtksdaap41> (raw)
Dear All:
I am Ginny Chen from Mediatek company.I start to work with DRM for a
while and now I am evaluating our display architecture for our new SoC.
I would like to adopt DRM to develop our display driver.
However, in our new SoC, the input source of display engine could be
memory or direct-linked with other hardwares (ex:camera sensor) which
means the input source of each plane should be able to configure during
plane updating.
As my understanding,with currently DRM framework, the input source of
plane could only be framebuffer that implies we still need to allocate
framebuffer for planes which are direct-linked with other hardware
engines if I want to control planes without modifying DRM framework.
It will waste memory and doesn't make sense for user to notice/manage
the framebuffers for direct-linked DRM planes.
Do you have any ideas for such use case?
Any suggestion will be very appreciated.
Regards,
Ginny Chen
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2016-09-21 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1474442309.4646.41.camel@mtksdaap41 \
--to=ginny.chen@mediatek.com \
--cc=christie.yu@mediatek.com \
--cc=dri-devel@lists.freedesktop.org \
/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