From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Yao <mark.yao@rock-chips.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu
Date: Thu, 09 Feb 2017 00:36:28 +0100 [thread overview]
Message-ID: <4892535.e058iD2sG7@diego> (raw)
In-Reply-To: <1486456542-18675-1-git-send-email-mark.yao@rock-chips.com>
Am Dienstag, 7. Februar 2017, 16:35:35 CET schrieb Mark Yao:
> Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and
> enable on ARM64" already landed, So drm/rockchip related patches [1] and [2]
> ready to landed, this series just rebase them to lastest drm-next.
>
> And fix some bugs for drm/rockchip drm_mm
>
> [0]: http://www.spinics.net/lists/arm-kernel/msg513781.html
> [1]: https://patchwork.kernel.org/patch/9196367
> [2]: https://patchwork.kernel.org/patch/9196369
I've managed to get some output on my rk3399-gru with this series ;-)
and rk3288 also kept on working, so
On rk3288 and rk3399
Tested-by: Heiko Stuebner <heiko@sntech.de>
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu
Date: Thu, 09 Feb 2017 00:36:28 +0100 [thread overview]
Message-ID: <4892535.e058iD2sG7@diego> (raw)
In-Reply-To: <1486456542-18675-1-git-send-email-mark.yao@rock-chips.com>
Am Dienstag, 7. Februar 2017, 16:35:35 CET schrieb Mark Yao:
> Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and
> enable on ARM64" already landed, So drm/rockchip related patches [1] and [2]
> ready to landed, this series just rebase them to lastest drm-next.
>
> And fix some bugs for drm/rockchip drm_mm
>
> [0]: http://www.spinics.net/lists/arm-kernel/msg513781.html
> [1]: https://patchwork.kernel.org/patch/9196367
> [2]: https://patchwork.kernel.org/patch/9196369
I've managed to get some output on my rk3399-gru with this series ;-)
and rk3288 also kept on working, so
On rk3288 and rk3399
Tested-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2017-02-08 23:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 8:35 [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` [PATCH v2 1/7] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` [PATCH v2 2/7] drm/rockchip: Use common IOMMU API to attach devices Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` [PATCH v2 3/7] drm/rockchip: gem: add mutex lock for drm mm Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 12:19 ` Thierry Reding
2017-02-07 12:19 ` Thierry Reding
2017-02-07 12:19 ` Thierry Reding
2017-02-08 0:28 ` Mark yao
2017-02-08 0:28 ` Mark yao
2017-02-08 0:28 ` Mark yao
2017-02-07 8:35 ` [PATCH v2 4/7] drm/rockchip: gem: fixup iommu_map_sg error path Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:35 ` Mark Yao
2017-02-07 8:39 ` [PATCH v2 6/7] drm/rockchip: Respect page offset in IOMMU mmap Mark Yao
2017-02-07 8:39 ` Mark Yao
2017-02-07 8:39 ` Mark Yao
2017-02-07 12:33 ` Thierry Reding
2017-02-07 12:33 ` Thierry Reding
2017-02-07 12:33 ` Thierry Reding
2017-02-07 8:39 ` [PATCH v2 7/7] drm/rockchip: Call drm_gem_object_release() to destroy GEM base Mark Yao
2017-02-07 8:39 ` Mark Yao
2017-02-07 8:39 ` Mark Yao
2017-02-07 12:37 ` Thierry Reding
2017-02-07 12:37 ` Thierry Reding
2017-02-07 12:37 ` Thierry Reding
2017-02-07 13:05 ` Tomasz Figa
2017-02-07 13:05 ` Tomasz Figa
2017-02-07 13:05 ` Tomasz Figa
2017-02-07 12:38 ` [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu Thierry Reding
2017-02-07 12:38 ` Thierry Reding
2017-02-07 12:38 ` Thierry Reding
2017-02-08 1:15 ` Mark yao
2017-02-08 1:15 ` Mark yao
2017-02-08 1:15 ` Mark yao
2017-02-08 23:36 ` Heiko Stübner [this message]
2017-02-08 23:36 ` Heiko Stübner
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=4892535.e058iD2sG7@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.