From: Shunqian Zheng <zhengsq@rock-chips.com>
To: joro@8bytes.org, heiko@sntech.de, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk,
mark.yao@rock-chips.com, airlied@linux.ie, tfiga@google.com,
xxm@rock-chips.com
Cc: linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Shunqian Zheng <zhengsq@rock-chips.com>
Subject: [PATCH v3 0/6] fix bugs; enable iommu for ARM64
Date: Wed, 15 Jun 2016 20:04:39 +0800 [thread overview]
Message-ID: <1465992285-16187-1-git-send-email-zhengsq@rock-chips.com> (raw)
This series patches mainly for ARM64 supporting.
To do this, it first add virtual iommu slave device which DRM can attach to,
convert DRM driver to use common iommu API instead of the ARM32
functions, and then use DMA API in iommu driver to map, to flush cache.
Mainly changes of V3:
- Instead of registering virtual iommu in DTS, V3
creates a iommu when attaching.
- Fix some bugs according to Tomasz's comments,
most of them are offline, locally.
Shunqian Zheng (3):
iommu/rockchip: support virtual iommu slave device
drm: rockchip: use common iommu api to attach iommu
iommu/rockchip: use DMA API to map, to flush cache
Simon Xue (3):
iommu/rockchip: fix devm_{request,free}_irq parameter
iommu/rockchip: add map_sg callback for rk_iommu_ops
iommu/rockchip: enable rockchip iommu on ARM64 platform
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 112 ++++++++-----
drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 1 +
drivers/iommu/Kconfig | 2 +-
drivers/iommu/rockchip-iommu.c | 251 ++++++++++++++++++++++------
4 files changed, 273 insertions(+), 93 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-15 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:04 Shunqian Zheng [this message]
2016-06-15 12:04 ` [PATCH v3 4/6] drm: rockchip: use common iommu api to attach iommu Shunqian Zheng
[not found] ` <1465992285-16187-5-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-15 14:24 ` Tomasz Figa via iommu
[not found] ` <1465992285-16187-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-15 12:04 ` [PATCH v3 1/6] iommu/rockchip: fix devm_{request,free}_irq parameter Shunqian Zheng
2016-06-15 12:04 ` [PATCH v3 2/6] iommu/rockchip: add map_sg callback for rk_iommu_ops Shunqian Zheng
2016-06-15 12:04 ` [PATCH v3 3/6] iommu/rockchip: support virtual iommu slave device Shunqian Zheng
2016-06-15 14:21 ` Tomasz Figa
2016-06-15 12:04 ` [PATCH v3 5/6] iommu/rockchip: use DMA API to map, to flush cache Shunqian Zheng
[not found] ` <1465992285-16187-6-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-15 14:31 ` Tomasz Figa via iommu
2016-06-15 12:04 ` [PATCH v3 6/6] iommu/rockchip: enable rockchip iommu on ARM64 platform Shunqian Zheng
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=1465992285-16187-1-git-send-email-zhengsq@rock-chips.com \
--to=zhengsq@rock-chips.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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=mark.yao@rock-chips.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@google.com \
--cc=xxm@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).