From: pullip.cho@samsung.com (KyongHo Cho)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: iommu flush page table entries from L1 and L2 cache
Date: Fri, 15 Apr 2011 11:24:16 +0900 [thread overview]
Message-ID: <BANLkTikfXbtsqaw5ZuP_BbDCtsxXOHZs_w@mail.gmail.com> (raw)
In-Reply-To: <20110414223036.GA7335@n2100.arm.linux.org.uk>
Hi, Russell.
I think we need cache maintenance operations that effect on inner and
outer caches at the same time.
Even though the DMA APIs are not for cache maintenance but for IO mapping,
they are useful for cache maint'
because they operate on inner and outer caches.
As you know, inner cache of Cortex-A is logical cache and outer cache
is physical cache in the programmer's point of view.
We need logical address and physical address at the same time to clean
or invalidate inner and outer cache.
That means we need to translate logical to physical address and it is
sometimes not trivial.
Finally, the kernel will contain many similar routines that do same thing.
On Fri, Apr 15, 2011 at 7:30 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Thu, Apr 14, 2011 at 04:52:48PM -0500, Fernando Guzman Lugo wrote:
>> From: Ramesh Gupta <grgupta@ti.com>
>>
>> This patch is to flush the iommu page table entries from L1 and L2
>> caches using dma_map_single. This also simplifies the implementation
>> by removing the functions ?flush_iopgd_range/flush_iopte_range.
>
> No. ?This usage is just wrong. ?If you're going to use the DMA API then
> unmap it, otherwise the DMA API debugging will go awol.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at ?http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2011-04-15 2:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 21:52 [PATCH] OMAP: iommu flush page table entries from L1 and L2 cache Fernando Guzman Lugo
2011-04-14 22:30 ` Russell King - ARM Linux
2011-04-15 2:24 ` KyongHo Cho [this message]
2011-04-15 8:12 ` Russell King - ARM Linux
2011-04-15 11:26 ` Gupta, Ramesh
2011-04-28 13:40 ` Russell King - ARM Linux
2011-04-28 16:48 ` Gupta, Ramesh
2011-08-11 19:28 ` Gupta, Ramesh
2011-08-11 22:29 ` Russell King - ARM Linux
2011-08-12 16:05 ` Gupta, Ramesh
2011-10-16 18:32 ` C.A, Subramaniam
2012-05-29 15:53 ` Gupta, Ramesh
2011-04-18 7:29 ` Arnd Bergmann
2011-04-18 11:05 ` Tony Lindgren
2011-04-18 11:42 ` Hiroshi DOYU
2011-04-18 13:25 ` Arnd Bergmann
2011-04-18 11:58 ` Arnd Bergmann
2011-04-18 12:55 ` Kyungmin Park
2011-04-18 14:13 ` Arnd Bergmann
2011-04-19 9:11 ` Kyungmin Park
2011-04-19 12:01 ` Arnd Bergmann
2011-04-19 12:35 ` Kyungmin Park
2011-04-19 13:02 ` Russell King - ARM Linux
2011-04-19 13:11 ` Arnd Bergmann
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=BANLkTikfXbtsqaw5ZuP_BbDCtsxXOHZs_w@mail.gmail.com \
--to=pullip.cho@samsung.com \
--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).