From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 0/2 v2] drm/arcpgu: Get use of dedicated memory area for frame buffer
Date: Thu, 28 Apr 2016 17:19:54 +0300 [thread overview]
Message-ID: <1461853196-15599-1-git-send-email-abrodkin@synopsys.com> (raw)
This mini-series allows to allocate frame buffer memory in desired
location. Allocation of a frame buffer memory in a special memory region
allows bypassing of so-called IO Coherency aperture which is typically set
as a range 0x8z-0xAz.
I.e. all data traffic to PGU bypasses IO Coherency block
and saves its bandwidth for other peripherals.
Cc: Dave Airlie <airlied at gmail.com>
Cc: Daniel Vetter <daniel at ffwll.ch>
Cc: devicetree at vger.kernel.org
Changes v1 -> v2:
* Reserved memory size bumped from 16Mb to 32Mb.
* Reserved area in AXS103 boards moved to the very end of available DDR.
Alexey Brodkin (2):
drm/arcpgu: use dedicated memory area for frame buffer
ARC: [axs10x] Specify reserved memory for frame buffer
arch/arc/boot/dts/axc001.dtsi | 22 ++++++++++++++++++++--
arch/arc/boot/dts/axc003.dtsi | 14 ++++++++++++++
arch/arc/boot/dts/axc003_idu.dtsi | 14 ++++++++++++++
arch/arc/boot/dts/axs10x_mb.dtsi | 2 +-
drivers/gpu/drm/arc/arcpgu_drv.c | 6 ++++++
5 files changed, 55 insertions(+), 3 deletions(-)
--
2.5.5
next reply other threads:[~2016-04-28 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 14:19 Alexey Brodkin [this message]
2016-04-28 14:19 ` [PATCH 1/2 v2] drm/arcpgu: use dedicated memory area for frame buffer Alexey Brodkin
2016-04-28 14:19 ` [PATCH 2/2 v2] ARC: [axs10x] Specify reserved memory " Alexey Brodkin
2016-04-29 10:49 ` Vineet Gupta
[not found] ` <57468A6C.9080505@synopsys.com>
[not found] ` <1464253672.4578.8.camel@synopsys.com>
[not found] ` <C2D7FE5348E1B147BCA15975FBA23075F4EAE493@us01wembx1.internal.synopsys.com>
[not found] ` <1464694143.6538.18.camel@synopsys.com>
2016-06-02 7:35 ` Fwd: " Vineet Gupta
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=1461853196-15599-1-git-send-email-abrodkin@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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