From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hideki EIRAKU <hdk@igel.co.jp>
Cc: FlorianSchandinat@gmx.de, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, m.szyprowski@samsung.com,
matsu@igel.co.jp, dhobsong@igel.co.jp
Subject: Re: [PATCH v4] fbdev: sh_mobile_lcdc: use dma_mmap_coherent
Date: Mon, 10 Dec 2012 22:54:45 +0000 [thread overview]
Message-ID: <1441080.TGoVcIhooK@avalon> (raw)
In-Reply-To: <20121210.193125.442743545.hdk@igel.co.jp>
Hi Eiraku-san,
On Monday 10 December 2012 19:31:25 Hideki EIRAKU wrote:
> On Thu, 16 Aug 2012 14:16:32 +0200 Laurent Pinchart wrote:
> > On Thursday 16 August 2012 19:13:20 Hideki EIRAKU wrote:
> >> fb_mmap() implemented in fbmem.c uses smem_start as the physical
> >> address of the frame buffer. In the sh_mobile_lcdc driver, the
> >> smem_start is a dma_addr_t that is not a physical address when IOMMU is
> >> enabled. dma_mmap_coherent() maps the address correctly.
> >>
> >> Signed-off-by: Hideki EIRAKU <hdk@igel.co.jp>
> >
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >
> > I will push the patch to v3.7 through my tree.
>
> I'd like to use this patch to test IOMMU implementation of Renesas
> IPMMU. But I could not find it in v3.7-rc8. Could you please tell me if
> this has already been merged somewhere or not?
I'm afraid the patch got delayed to v3.8, sorry about that. I've sent a pull
request for v3.8, the patch is currently in linux-next
(bf10a53765b4435a5349a92a5a51753902ed86f1) and will be merged during the next
merge window (which should open in the very near future).
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2012-12-10 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:13 [PATCH v4] fbdev: sh_mobile_lcdc: use dma_mmap_coherent Hideki EIRAKU
2012-08-16 12:16 ` Laurent Pinchart
2012-12-10 10:31 ` Hideki EIRAKU
2012-12-10 22:54 ` Laurent Pinchart [this message]
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=1441080.TGoVcIhooK@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=FlorianSchandinat@gmx.de \
--cc=dhobsong@igel.co.jp \
--cc=hdk@igel.co.jp \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=matsu@igel.co.jp \
/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).