From: Vineet Gupta <vgupta@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer
Date: Thu, 28 Apr 2016 19:26:35 +0530 [thread overview]
Message-ID: <57221693.50401@synopsys.com> (raw)
In-Reply-To: <1461851171.3673.30.camel@synopsys.com>
On Thursday 28 April 2016 07:16 PM, Alexey Brodkin wrote:
>> > Note that the IOC start alignment needs to follow
>> > max(4k, size). What will be maximum size of frame buffer - 16M always !
> What do you mean by that?
For HS38, we intend to bypass the frame buffer traffic from IOC port. So the frame
buffer start needs to be inside the IOC aperture base address. That value can't be
arbitrary - it is atleast 4K aligned value and further also needs to be aligned to
the size of aperture. So if the size is 16M it needs to be 16M aligned etc...
-Vineet
next prev parent reply other threads:[~2016-04-28 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 14:34 [PATCH 0/2] drm/arcpgu: Get use of dedicated memory area for frame buffer Alexey Brodkin
2016-04-27 14:35 ` [PATCH 1/2] drm/arcpgu: use " Alexey Brodkin
2016-04-27 14:35 ` [PATCH 2/2] ARC: [axs10x] Specify reserved memory " Alexey Brodkin
2016-04-28 4:26 ` Vineet Gupta
2016-04-28 13:46 ` Alexey Brodkin
2016-04-28 13:56 ` Vineet Gupta [this message]
2016-04-28 14:38 ` Alexey Brodkin
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=57221693.50401@synopsys.com \
--to=vgupta@synopsys.com \
--cc=Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=devicetree@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).