From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Cc: "daniel@ffwll.ch" <daniel@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Allocation of frame buffer at a specific memory range or address
Date: Fri, 15 Apr 2016 15:48:59 +0000 [thread overview]
Message-ID: <1460735338.3248.21.camel@synopsys.com> (raw)
Hello,
I'm wondering if there's a way to force kernel to allocate backing
memory for frame buffer in a special location?
A little bit of background below.
I continue to work on DRM driver for ARC PGU, latest
is v5 and available here - https://lkml.org/lkml/2016/3/28/170
In current state everything more or less works but I'd like to
implement one improvement - I'd like to have an ability to specify
where in memory will be allocated frame-buffer's backing storage area.
I.e. buffer which will be read by PGU hardware.
Currently we use whatever DRM susbsystem put in "gem->paddr".
That's a snippet of the code which tells PGU hardware
which memory location to scan for data:
--------------------->8--------------------
arcpgu = crtc_to_arcpgu_priv(plane->state->crtc);
gem = drm_fb_cma_get_gem_obj(plane->state->fb, 0);
/* Telling PGU hardware where is data to read */
arc_pgu_write(arcpgu, ARCPGU_REG_BUF0_ADDR, gem->paddr);
--------------------->8--------------------
But we may use a special memory area which works better
for that case, i.e. for example could be accessed faster by both
CPU and PGU hardware (like on-chip SRAM as opposed to external DDR).
And now the question is how to force DRM subsystem or just that driver
to use whatever predefined (say via device tree) location in memory
for data buffer allocation.
All thoughts on this are more than welcome.
-Alexey
next reply other threads:[~2016-04-15 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 15:48 Alexey Brodkin [this message]
2016-04-15 16:42 ` Allocation of frame buffer at a specific memory range or address Daniel Vetter
2016-04-16 6:07 ` Vineet Gupta
2016-04-16 21:48 ` Rob Clark
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=1460735338.3248.21.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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