From: "Víctor M. Jáquez L." <vjaquez@igalia.com>
To: "Gomez Castellanos, Ivan" <ivan.gomez@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Ameya Palande <ameya.palande@nokia.com>,
"Menon, Nishanth" <nm@ti.com>
Subject: Re: [PATCH 03/13] DSPBRIDGE: Moving functions from mem.c to drv.c
Date: Fri, 16 Apr 2010 12:36:58 +0200 [thread overview]
Message-ID: <20100416103658.GA18995@lit.local.igalia.com> (raw)
In-Reply-To: <818EF96F5A7CC84789DD014773DB09548F6481CF@dlee01.ent.ti.com>
On Thu, Apr 08, 2010 at 06:47:13PM -0500, Gomez Castellanos, Ivan wrote:
> +/*
> + * ======== mem_flush_cache ========
> + * Purpose:
> + * Flush cache
> + */
> +void mem_flush_cache(void *pMemBuf, u32 byte_size, s32 FlushType)
> +{
> + if (!pMemBuf)
> + return;
> +
> + switch (FlushType) {
> + /* invalidate only */
> + case PROC_INVALIDATE_MEM:
> + dmac_inv_range(pMemBuf, pMemBuf + byte_size);
> + outer_inv_range(__pa((u32) pMemBuf), __pa((u32) pMemBuf +
> + byte_size));
> + break;
> + /* writeback only */
> + case PROC_WRITEBACK_MEM:
> + dmac_clean_range(pMemBuf, pMemBuf + byte_size);
> + outer_clean_range(__pa((u32) pMemBuf), __pa((u32) pMemBuf +
> + byte_size));
> + break;
> + /* writeback and invalidate */
> + case PROC_WRITEBACK_INVALIDATE_MEM:
> + dmac_flush_range(pMemBuf, pMemBuf + byte_size);
> + outer_flush_range(__pa((u32) pMemBuf), __pa((u32) pMemBuf +
> + byte_size));
> + break;
> + }
In the commit 702b94bff3c50542a6e4ab9a4f4cef093262fe65 (2.6.34) the functions
dmac_inv_range and dmac_clean_range were removed.
I'm wondering how to fix this in order to rebase to 2.6.34.
Thanks
vmjl
next prev parent reply other threads:[~2010-04-16 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 23:47 [PATCH 03/13] DSPBRIDGE: Moving functions from mem.c to drv.c Gomez Castellanos, Ivan
2010-04-16 10:36 ` Víctor M. Jáquez L. [this message]
2010-04-16 11:46 ` Kanigeri, Hari
2010-04-21 23:57 ` Nishanth Menon
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=20100416103658.GA18995@lit.local.igalia.com \
--to=vjaquez@igalia.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=ivan.gomez@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox