From: Mark yao <mark.yao@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: dri-devel@lists.freedesktop.org,
"Ørjan Eide" <orjan.eide@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] drm: rockchip: Don't pass DRM fake offset to dma-api
Date: Mon, 20 Apr 2015 13:34:57 +0800 [thread overview]
Message-ID: <55349001.80304@rock-chips.com> (raw)
In-Reply-To: <1743547.3D2D8THGkI@diego>
On 2015年04月19日 00:55, Heiko Stübner wrote:
> Am Donnerstag, 16. April 2015, 16:41:51 schrieb Ørjan Eide:
>> Set vm_pgoff to 0 after using it to look up the GEM node, before passing
>> it on rockchip_gem_mmap_buf() where the offset must be from the start of
>> the buffer.
>>
>> Passing in the fake offset currently works because the
>> dma_mmap_attrs implementation that is used for this device,
>> arm_iommu_mmap_attrs, ignores the offset completely.
>>
>> Signed-off-by: Ørjan Eide <orjan.eide@arm.com>
> both patches on a rk3288-veyron-pinky
>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
>
> Through which tree do you want to take these patches? I guess the rockchip-drm
> related patch should go through the tree that will take the dma-mapping patch,
> so you'll probably need an "Ack" from Mark Yao (Cc'ed).
>
>
> Heiko
>
>> ---
>> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c index 7ca8799e..69f01c3
>> 100644
>> --- a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> @@ -94,6 +94,11 @@ int rockchip_gem_mmap(struct file *filp, struct
>> vm_area_struct *vma) return -EACCES;
>> }
>>
>> + /* Set vm_pgoff (used as a fake buffer offset by DRM) to 0 and map the
>> + * whole buffer from the start.
>> + */
>> + vma->vm_pgoff = 0;
>> +
>> obj = container_of(node, struct drm_gem_object, vma_node);
>> ret = rockchip_gem_mmap_buf(obj, vma);
>
>
>
Thanks for this fix,
Acked-by: Mark Yao <mark.yao@rock-chips.com>
--
Mark
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] drm: rockchip: Don't pass DRM fake offset to dma-api
Date: Mon, 20 Apr 2015 13:34:57 +0800 [thread overview]
Message-ID: <55349001.80304@rock-chips.com> (raw)
In-Reply-To: <1743547.3D2D8THGkI@diego>
On 2015?04?19? 00:55, Heiko St?bner wrote:
> Am Donnerstag, 16. April 2015, 16:41:51 schrieb ?rjan Eide:
>> Set vm_pgoff to 0 after using it to look up the GEM node, before passing
>> it on rockchip_gem_mmap_buf() where the offset must be from the start of
>> the buffer.
>>
>> Passing in the fake offset currently works because the
>> dma_mmap_attrs implementation that is used for this device,
>> arm_iommu_mmap_attrs, ignores the offset completely.
>>
>> Signed-off-by: ?rjan Eide <orjan.eide@arm.com>
> both patches on a rk3288-veyron-pinky
>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
>
> Through which tree do you want to take these patches? I guess the rockchip-drm
> related patch should go through the tree that will take the dma-mapping patch,
> so you'll probably need an "Ack" from Mark Yao (Cc'ed).
>
>
> Heiko
>
>> ---
>> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c index 7ca8799e..69f01c3
>> 100644
>> --- a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> @@ -94,6 +94,11 @@ int rockchip_gem_mmap(struct file *filp, struct
>> vm_area_struct *vma) return -EACCES;
>> }
>>
>> + /* Set vm_pgoff (used as a fake buffer offset by DRM) to 0 and map the
>> + * whole buffer from the start.
>> + */
>> + vma->vm_pgoff = 0;
>> +
>> obj = container_of(node, struct drm_gem_object, vma_node);
>> ret = rockchip_gem_mmap_buf(obj, vma);
>
>
>
Thanks for this fix,
Acked-by: Mark Yao <mark.yao@rock-chips.com>
--
?ark
WARNING: multiple messages have this Message-ID (diff)
From: Mark yao <mark.yao@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: "Ørjan Eide" <orjan.eide@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
djkurtz@chromium.org
Subject: Re: [PATCH 1/2] drm: rockchip: Don't pass DRM fake offset to dma-api
Date: Mon, 20 Apr 2015 13:34:57 +0800 [thread overview]
Message-ID: <55349001.80304@rock-chips.com> (raw)
In-Reply-To: <1743547.3D2D8THGkI@diego>
On 2015年04月19日 00:55, Heiko Stübner wrote:
> Am Donnerstag, 16. April 2015, 16:41:51 schrieb Ørjan Eide:
>> Set vm_pgoff to 0 after using it to look up the GEM node, before passing
>> it on rockchip_gem_mmap_buf() where the offset must be from the start of
>> the buffer.
>>
>> Passing in the fake offset currently works because the
>> dma_mmap_attrs implementation that is used for this device,
>> arm_iommu_mmap_attrs, ignores the offset completely.
>>
>> Signed-off-by: Ørjan Eide <orjan.eide@arm.com>
> both patches on a rk3288-veyron-pinky
>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
>
> Through which tree do you want to take these patches? I guess the rockchip-drm
> related patch should go through the tree that will take the dma-mapping patch,
> so you'll probably need an "Ack" from Mark Yao (Cc'ed).
>
>
> Heiko
>
>> ---
>> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c index 7ca8799e..69f01c3
>> 100644
>> --- a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
>> @@ -94,6 +94,11 @@ int rockchip_gem_mmap(struct file *filp, struct
>> vm_area_struct *vma) return -EACCES;
>> }
>>
>> + /* Set vm_pgoff (used as a fake buffer offset by DRM) to 0 and map the
>> + * whole buffer from the start.
>> + */
>> + vma->vm_pgoff = 0;
>> +
>> obj = container_of(node, struct drm_gem_object, vma_node);
>> ret = rockchip_gem_mmap_buf(obj, vma);
>
>
>
Thanks for this fix,
Acked-by: Mark Yao <mark.yao@rock-chips.com>
--
Mark
next prev parent reply other threads:[~2015-04-20 5:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:41 [PATCH 1/2] drm: rockchip: Don't pass DRM fake offset to dma-api Ørjan Eide
2015-04-16 14:41 ` Ørjan Eide
2015-04-16 14:41 ` [PATCH 2/2] ARM: DMA: Use vm_pgoff for IOMMU mmap Ørjan Eide
2015-04-16 14:41 ` Ørjan Eide
2015-04-20 4:13 ` Daniel Kurtz
2015-04-20 4:13 ` Daniel Kurtz
2015-04-20 4:13 ` Daniel Kurtz
2015-04-18 16:55 ` [PATCH 1/2] drm: rockchip: Don't pass DRM fake offset to dma-api Heiko Stübner
2015-04-18 16:55 ` Heiko Stübner
2015-04-18 16:55 ` Heiko Stübner
2015-04-20 5:34 ` Mark yao [this message]
2015-04-20 5:34 ` Mark yao
2015-04-20 5:34 ` Mark yao
2015-04-20 5:44 ` Mark yao
2015-04-20 5:44 ` Mark yao
2015-04-20 5:44 ` Mark yao
2015-07-07 7:02 ` Daniel Kurtz
2015-07-07 7:02 ` Daniel Kurtz
2015-07-07 7:02 ` Daniel Kurtz
2015-04-20 4:13 ` Daniel Kurtz
2015-04-20 4:13 ` Daniel Kurtz
2015-04-20 4:13 ` Daniel Kurtz
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=55349001.80304@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=orjan.eide@arm.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.