From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] DRM: add Freescale i.MX LCDC driver
Date: Wed, 23 May 2012 10:37:58 +0200 [thread overview]
Message-ID: <4FBCA1E6.9050604@metafoo.de> (raw)
In-Reply-To: <20120523074710.GP30400@pengutronix.de>
[...]
>>> +
>>> +static int imx_drm_gem_mmap_buffer(struct file *filp,
>>> + struct vm_area_struct *vma)
>>> +{
>>> + struct drm_gem_object *obj = filp->private_data;
>>> + struct imx_drm_gem_obj *imx_drm_gem_obj = to_imx_drm_gem_obj(obj);
>>> + struct imx_drm_buf_entry *entry;
>>> + unsigned long pfn, vm_size;
>>> +
>>> + vma->vm_flags |= VM_IO | VM_RESERVED;
>>> +
>>> + vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
>>
>> pgprot_writecombine()?
>
> copied from the exynos driver. The exynos driver recently gained support
> for different cache attribute flags and I could do the same. I would
> prefer not to even have to think about it by using some generic code
> here instead of duplicating other peoples bugs.
>
> Do you think it's possible to share this code as suggested by Lars?
> Every SoC not having a IOMMU could share the same code here, it's just
> not clear to me how we can put this in a form that is acceptable
> upstream.
I may have missed this in the previous discussion. But why can't we put the
gem handling code in the toplevel drm folder, give it a config symbol and
let drivers which want to use the code select the config symbol? I think the
main concern was about introducing a new intermediate layer, but the
"simple" gem support would really just a set of helper functions.
Thanks,
- Lars
next prev parent reply other threads:[~2012-05-23 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 12:27 No subject Sascha Hauer
2012-05-18 12:27 ` [PATCH 1/2] DRM: add Freescale i.MX LCDC driver Sascha Hauer
2012-05-22 21:28 ` Rob Clark
2012-05-23 7:47 ` Sascha Hauer
2012-05-23 8:37 ` Lars-Peter Clausen [this message]
2012-05-23 9:09 ` Daniel Vetter
2012-05-18 12:27 ` [PATCH 2/2] pcm038 lcdc support Sascha Hauer
2012-05-18 14:03 ` Adam Jackson
2012-05-18 15:13 ` Sascha Hauer
2012-05-22 10:02 ` Dave Airlie
2012-05-22 14:06 ` Lars-Peter Clausen
2012-05-23 8:12 ` Sascha Hauer
2012-05-24 6:31 ` Sascha Hauer
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=4FBCA1E6.9050604@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).