From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "airlied@redhat.com" <airlied@redhat.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"airlied@linux.ie" <airlied@linux.ie>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [GIT PULL] drm/arcpgu: use dedicated memory area for frame buffer
Date: Tue, 10 May 2016 09:51:31 +0000 [thread overview]
Message-ID: <1462873872.3135.0.camel@synopsys.com> (raw)
In-Reply-To: <1461929790.3020.8.camel@synopsys.com>
Hi Dave,
On Fri, 2016-04-29 at 11:36 +0000, Alexey Brodkin wrote:
> Hi Dave,
>
> Please pull this mini-series that allows ARC PGU to use
> dedicated memory location as framebuffer backing storage.
>
> v2 of that series was reviewed here
> https://lists.freedesktop.org/archives/dri-devel/2016-April/106279.html
>
> It is based on top of today's drm-next branch.
>
> Best regards,
> Alexey
>
> The following changes since commit b89359bdf0f1e95a4c5f92300594ba9dde323fc4:
>
> Merge branch 'for-next' of http://git.agner.ch/git/linux-drm-fsl-dcu into drm-next (2016-04-29 14:57:51 +1000)
>
> are available in the git repository at:
>
> https://github.com/foss-for-synopsys-dwc-arc-processors/linux.git topic-arcpgu-updates
>
> for you to fetch changes up to cb2ad5e5339c5122166265cea579cc6a356d46de:
>
> ARC: [axs10x] Specify reserved memory for frame buffer (2016-04-29 14:34:13 +0300)
>
> ----------------------------------------------------------------
> 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(-)
Could you please take a look at this pull request?
-Alexey
next prev parent reply other threads:[~2016-05-10 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:19 [PATCH 0/4 v6] drm: Add support of ARC PGU display controller Alexey Brodkin
2016-04-19 13:19 ` [PATCH 1/4 " Alexey Brodkin
2016-04-19 13:19 ` [PATCH 2/4 v6] drm: Add DT bindings documentation for " Alexey Brodkin
2016-04-19 13:19 ` [PATCH 3/4 v6] MAINTAINERS: Add maintainer " Alexey Brodkin
2016-04-19 13:19 ` [PATCH 4/4 v6] arc: axs10x - add support of ARC PGU Alexey Brodkin
2016-04-22 14:53 ` [PATCH 0/4 v6] drm: Add support of ARC PGU display controller Alexey Brodkin
2016-04-26 15:28 ` [GIT PULL] " Alexey Brodkin
2016-04-26 23:40 ` Dave Airlie
2016-04-29 11:36 ` [GIT PULL] drm/arcpgu: use dedicated memory area for frame buffer Alexey Brodkin
2016-05-10 9:51 ` Alexey Brodkin [this message]
2016-05-16 8:22 ` Alexey Brodkin
2016-05-23 10:31 ` Alexey Brodkin
2016-05-23 19:23 ` David Airlie
2016-05-23 20:02 ` 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=1462873872.3135.0.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).