From: Joerg Roedel <joro@8bytes.org>
To: Tomasz Figa <tfiga@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Shunqian Zheng <zhengsq@rock-chips.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64
Date: Tue, 21 Jun 2016 14:54:35 +0200 [thread overview]
Message-ID: <20160621125435.GE11432@8bytes.org> (raw)
In-Reply-To: <CAAFQd5B8sxbZ6MymwDKL4vZkfQ-ej_bNh7tS1OhRC=X7-eie+Q@mail.gmail.com>
Hi Tomasz,
On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> In simple words, DRM patches depend on IOMMU patches.
>
> More precisely: The IOMMU patches alone are supposed to not break
> anything. Same goes for the first DRM patch (7/8). Only second DRM
> patch (8/8) depends on changes introduced by its predecessors.
The first DRM patch is 6/7, so it is 7/8 with the iommu dependency,
right? Anyway, I think the best is I take the iommu patches when Heiko
is ok with them and then the DRM tree can merge that branch in to apply
the DRM patches.
But first Heiko should have a look at the patches.
Thanks,
Joerg
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64
Date: Tue, 21 Jun 2016 14:54:35 +0200 [thread overview]
Message-ID: <20160621125435.GE11432@8bytes.org> (raw)
In-Reply-To: <CAAFQd5B8sxbZ6MymwDKL4vZkfQ-ej_bNh7tS1OhRC=X7-eie+Q@mail.gmail.com>
Hi Tomasz,
On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> In simple words, DRM patches depend on IOMMU patches.
>
> More precisely: The IOMMU patches alone are supposed to not break
> anything. Same goes for the first DRM patch (7/8). Only second DRM
> patch (8/8) depends on changes introduced by its predecessors.
The first DRM patch is 6/7, so it is 7/8 with the iommu dependency,
right? Anyway, I think the best is I take the iommu patches when Heiko
is ok with them and then the DRM tree can merge that branch in to apply
the DRM patches.
But first Heiko should have a look at the patches.
Thanks,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Tomasz Figa <tfiga@chromium.org>
Cc: "open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
Mark Yao <mark.yao@rock-chips.com>,
Shunqian Zheng <zhengsq@rock-chips.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64
Date: Tue, 21 Jun 2016 14:54:35 +0200 [thread overview]
Message-ID: <20160621125435.GE11432@8bytes.org> (raw)
In-Reply-To: <CAAFQd5B8sxbZ6MymwDKL4vZkfQ-ej_bNh7tS1OhRC=X7-eie+Q@mail.gmail.com>
Hi Tomasz,
On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> In simple words, DRM patches depend on IOMMU patches.
>
> More precisely: The IOMMU patches alone are supposed to not break
> anything. Same goes for the first DRM patch (7/8). Only second DRM
> patch (8/8) depends on changes introduced by its predecessors.
The first DRM patch is 6/7, so it is 7/8 with the iommu dependency,
right? Anyway, I think the best is I take the iommu patches when Heiko
is ok with them and then the DRM tree can merge that branch in to apply
the DRM patches.
But first Heiko should have a look at the patches.
Thanks,
Joerg
next prev parent reply other threads:[~2016-06-21 12:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 4:34 [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64 Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
[not found] ` <1466483681-36110-1-git-send-email-tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-06-21 4:34 ` [PATCH v4 1/8] iommu/rockchip: Fix devm_{request,free}_irq parameter Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 2/8] iommu/rockchip: Add map_sg callback for rk_iommu_ops Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 3/8] iommu/rockchip: Fix allocation of bases array in driver probe Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
[not found] ` <1466483681-36110-4-git-send-email-tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-06-21 17:19 ` Doug Anderson
2016-06-21 17:19 ` Doug Anderson
2016-06-21 17:19 ` Doug Anderson
2016-06-21 4:34 ` [PATCH v4 4/8] iommu/rockchip: Use DMA API to manage coherency Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 5/8] iommu/rockchip: Prepare to support generic DMA mapping Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 6/8] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 7/8] drm/rockchip: Use common IOMMU API to attach devices Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` [PATCH v4 8/8] iommu/rockchip: Enable Rockchip IOMMU on ARM64 Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 4:34 ` Tomasz Figa
2016-06-21 9:17 ` [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable " Joerg Roedel
2016-06-21 9:17 ` Joerg Roedel
2016-06-21 9:17 ` Joerg Roedel
2016-06-21 12:42 ` Tomasz Figa
2016-06-21 12:42 ` Tomasz Figa
2016-06-21 12:42 ` Tomasz Figa
2016-06-21 12:54 ` Joerg Roedel [this message]
2016-06-21 12:54 ` Joerg Roedel
2016-06-21 12:54 ` Joerg Roedel
[not found] ` <20160621125435.GE11432-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-06-21 13:18 ` Heiko Stübner
2016-06-21 13:18 ` Heiko Stübner
2016-06-21 13:18 ` Heiko Stübner
2016-06-21 13:18 ` Heiko Stübner
2016-06-21 13:52 ` Joerg Roedel
2016-06-21 13:52 ` Joerg Roedel
2016-06-21 13:52 ` Joerg Roedel
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=20160621125435.GE11432@8bytes.org \
--to=joro@8bytes.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=m.szyprowski@samsung.com \
--cc=tfiga@chromium.org \
--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 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.