From: Joerg Roedel <joro@8bytes.org>
To: Shunqian Zheng <zhengsq@rock-chips.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux@armlinux.org.uk,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
tfiga@google.com, iommu@lists.linux-foundation.org,
robh+dt@kernel.org, xxm@rock-chips.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: iommu/rockchip: Fix bugs and enable on ARM64
Date: Mon, 27 Jun 2016 14:57:51 +0200 [thread overview]
Message-ID: <20160627125751.GN11432@8bytes.org> (raw)
In-Reply-To: <1466734413-7453-1-git-send-email-zhengsq@rock-chips.com>
On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote:
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++++++------
> drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 +
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221 ++++++++++++++++++++++++++--
> drivers/gpu/drm/rockchip/rockchip_drm_gem.h | 9 ++
> drivers/iommu/Kconfig | 2 +-
> drivers/iommu/rockchip-iommu.c | 181 +++++++++++++++++------
> 6 files changed, 413 insertions(+), 103 deletions(-)
Applied the IOMMU patches, thanks.
Joerg
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-27 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 2:13 iommu/rockchip: Fix bugs and enable on ARM64 Shunqian Zheng
[not found] ` <1466734413-7453-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-24 2:13 ` [PATCH v5 1/8] iommu/rockchip: Fix devm_{request,free}_irq parameter Shunqian Zheng
2016-06-24 2:13 ` [PATCH v5 2/8] iommu/rockchip: Add map_sg callback for rk_iommu_ops Shunqian Zheng
2016-06-24 2:13 ` [PATCH v5 3/8] iommu/rockchip: Fix allocation of bases array in driver probe Shunqian Zheng
2016-06-24 2:13 ` [PATCH v5 4/8] iommu/rockchip: Use DMA API to manage coherency Shunqian Zheng
2016-06-24 2:13 ` [PATCH v5 5/8] iommu/rockchip: Prepare to support generic DMA mapping Shunqian Zheng
2016-06-24 2:13 ` [PATCH v5 6/8] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain Shunqian Zheng
2016-07-08 0:54 ` Mark yao
2016-06-24 2:13 ` [PATCH v5 7/8] drm/rockchip: Use common IOMMU API to attach devices Shunqian Zheng
2016-07-08 0:54 ` Mark yao
2016-06-24 2:13 ` [PATCH v5 8/8] iommu/rockchip: Enable Rockchip IOMMU on ARM64 Shunqian Zheng
[not found] ` <1466734413-7453-9-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-11-29 0:42 ` Brian Norris
[not found] ` <20161129004225.GA109697-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-11-29 9:22 ` Heiko Stübner
2016-06-27 12:57 ` Joerg Roedel [this message]
2016-07-08 1:01 ` iommu/rockchip: Fix bugs and enable " Mark yao
[not found] ` <577EFB86.1060502-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-07-15 15:32 ` Matthias Brugger
2016-07-15 16:16 ` Joerg Roedel
2017-03-08 5:50 ` Caesar Wang
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=20160627125751.GN11432@8bytes.org \
--to=joro@8bytes.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@google.com \
--cc=xxm@rock-chips.com \
--cc=zhengsq@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).