From: Mark yao <mark.yao@rock-chips.com>
To: Steven Newbury <steve@snewbury.org.uk>,
Andrzej Hajda <a.hajda@samsung.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
heiko@sntech.de, linux-doc@vger.kernel.org,
kever.yang@rock-chips.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, xjq@rock-chips.com,
zyw@rock-chips.com, linux-api@vger.kernel.org,
cym@rock-chips.com, linux-rockchip@lists.infradead.org,
kfx@rock-chips.com, Grant Likely <grant.likely@linaro.org>,
wxt@rock-chips.com, huangtao@rock-chips.com,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
yxj@rock-chips.com, cf@rock-chips.com,
Rob Herring <robh+dt@kernel.org>,
marcheu@chromium.org, xxm@rock-chips.com, xw@rock-chips.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
dianders@chromium.org, Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v9 1/3] drm: rockchip: Add basic drm driver
Date: Wed, 08 Oct 2014 09:17:28 +0800 [thread overview]
Message-ID: <543490A8.7030807@rock-chips.com> (raw)
In-Reply-To: <1412720776.2797.8.camel@snewbury.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
Hi Steven
I'm glad to see you to discuss about rk29xx.
On 2014年10月08日 06:26, Steven Newbury wrote:
> I've just been discussing how this relates to rk29xx on #etnaviv. I
> looked through the patch and it's good to see it's not limited to
> supporting Mali GPUs. I see no reason this wouldn't be compatible
> with etna_viv for rk29xx (or future Rockchip designs with alternative
> GPUs) as long as the rest of the infrastructure to support rk29 is in
> place iommu (ARM SMMU?) driver, for example.
Now the drm driver only test on rk3288, and future when we add
compatible for rk29xx, we
would consider to add a non-iommu path for it.
> IMHO it's vital to keep a logical separation between the video display
> hardware and the graphics processor on SoCs.
Sure, the graphics processor maybe change in different solutions,
logical separation is that we
try to keep.
Regards
-Ｍark
[-- Attachment #1.2: Type: text/html, Size: 2083 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-08 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 12:57 [PATCH v9 0/3] Add drm driver for Rockchip Socs Mark Yao
2014-09-30 13:03 ` [PATCH v9 1/3] drm: rockchip: Add basic drm driver Mark Yao
2014-09-30 13:31 ` Andrzej Hajda
2014-10-07 3:56 ` Mark yao
2014-10-07 6:13 ` Andrzej Hajda
[not found] ` <54338484.5070809-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-10-07 22:26 ` Steven Newbury
2014-10-08 1:17 ` Mark yao [this message]
[not found] ` <543490A8.7030807-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-10-08 13:31 ` Steven Newbury
[not found] ` <1412081870-27535-1-git-send-email-mark.yao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-30 13:04 ` [PATCH v9 2/3] dt-bindings: video: Add for rockchip display subsytem Mark Yao
2014-09-30 13:06 ` [PATCH v9 3/3] dt-bindings: video: Add documentation for rockchip vop Mark Yao
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=543490A8.7030807@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=a.hajda@samsung.com \
--cc=cf@rock-chips.com \
--cc=cym@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kever.yang@rock-chips.com \
--cc=kfx@rock-chips.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcheu@chromium.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=steve@snewbury.org.uk \
--cc=wxt@rock-chips.com \
--cc=xjq@rock-chips.com \
--cc=xw@rock-chips.com \
--cc=xxm@rock-chips.com \
--cc=yxj@rock-chips.com \
--cc=zyw@rock-chips.com \
/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).